When using a default setup of Spring Boot + Actuator + Micrometer, the auto emitted logback.events and log4j2.events metrics can be high volume and start slowing down the application. Other Metrics may also be dropped due to one (or more) high volume metrics.
This is a flaw in how Sentry Java SDK currently buffers metrics by simply taking each increment as a separate entry. This means a high volume metrics can cause other metrics to no longer make it to Sentry.
As a first step and workaround we want to offer a Sentry.metrics().ignoredMetrics() option that allows customers to easily configure which metrics (by name) should not be sent to Sentry.
In the future we should revisit this. One solution could be to start accumulating metrics, see #6151
When using a default setup of Spring Boot + Actuator + Micrometer, the auto emitted
logback.eventsandlog4j2.eventsmetrics can be high volume and start slowing down the application. Other Metrics may also be dropped due to one (or more) high volume metrics.This is a flaw in how Sentry Java SDK currently buffers metrics by simply taking each increment as a separate entry. This means a high volume metrics can cause other metrics to no longer make it to Sentry.
As a first step and workaround we want to offer a
Sentry.metrics().ignoredMetrics()option that allows customers to easily configure which metrics (by name) should not be sent to Sentry.In the future we should revisit this. One solution could be to start accumulating metrics, see #6151