* fix: jq/Dockerfile to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-DEBIAN11-LIBGCRYPT20-523947 - https://snyk.io/vuln/SNYK-DEBIAN11-LIBSEPOL-1315627 - https://snyk.io/vuln/SNYK-DEBIAN11-LIBSEPOL-1315629 - https://snyk.io/vuln/SNYK-DEBIAN11-LIBSEPOL-1315635 - https://snyk.io/vuln/SNYK-DEBIAN11-ZLIB-6008961 * use bookworm-slim --------- Co-authored-by: snyk-bot <snyk-bot@snyk.io> Co-authored-by: Hubert Deng <hubertdeng123@gmail.com> Co-authored-by: Hubert Deng <hubert.deng@sentry.io>
In this PR we fix our usage of jq: 1. Use the container. Before we were accidentally using jq installed in the environment 1. Rewrite generate_breadcrumb_json to read log file all at once 1. Build docker image for jq in unit tests
In this PR, we change the send-event function to write out more information into the envelope we send via sentry-cli, particularly adding breadcrumbs with the end of the log and giving the stack trace in a format Sentry self-hosted can understand. Fixes getsentry/team-ospo#54 and getsentry/team-ospo#53 Example issue with this formatting: https://self-hosted.getsentry.net/organizations/self-hosted/issues/227/?query=is%3Aunresolved