Java Agent creating too many NewRelicMetricsReporter threads when used with Kafka instrumentation #1056
Labels
GTSE
There is an associated support escalation with this issue.
on-roadmap
Issue has been added to our product roadmap and will be worked in the coming quarter
Current agent design/implementation causes an unnecessary number of
NewRelicMetricsReporter
thread to be created when the agent is used with Kafka 3.x instrumentation. Refactoring this implementation would be best - perhaps to leverage a singleton instance, etc.The text was updated successfully, but these errors were encountered: