Conversation
solnic
force-pushed
the
954-sentry-metrics-for-elixir
branch
3 times, most recently
from
572dc4b to
b65c9d4
Compare
solnic
changed the title
solnic
force-pushed
the
954-sentry-metrics-for-elixir
branch
from
b65c9d4 to
2484046
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
solnic
force-pushed
the
954-sentry-metrics-for-elixir
branch
from
f6f84bb to
681b34a
Compare
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
solnic
force-pushed
the
954-sentry-metrics-for-elixir
branch
from
681b34a to
d33bc2b
Compare
solnic
force-pushed
the
954-sentry-metrics-for-elixir
branch
from
d33bc2b to
2159c74
Compare
solnic
force-pushed
the
954-sentry-metrics-for-elixir
branch
from
2159c74 to
8005347
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
|
|
||
| [] -> | ||
| :ok | ||
| end |
There was a problem hiding this comment.
Missing DSN guard in async metric sending path
Low Severity
The :none non-TelemetryProcessor path calls Transport.Sender.send_async(client, filtered_metric) without checking Config.dsn() first. The :sync path correctly guards with if Config.dsn() do before attempting to send. When DSN is nil and :metric is removed from telemetry_processor_categories, this path will attempt to send to a nil endpoint.
Additional Locations (1)
1 participant
Adds support for Sentry Metrics via
Sentry.Metrics. Uses the newTelemetryProcessorfor batching and sending metrics.Screenshot