-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Negative Values Reported Deriving from StatsImpl and RepsponseTimeStatsImpl #709
Comments
Bumped from the |
Not able to determine root cause after extensive exploration. Deferring this issue as a potential future roadmap consideration. Moving back to |
Was not able to include in FY23Q1's agent release. Not selected for next quarter's agent roadmap. Will consider for a future agent release. |
Not selected for the agent roadmap. Issue does not appear to be widespread/common. |
Issue appears to have resolved with #1685 |
A pernicious issue that has alluded root cause discovery for some time due to an inability to consistently reproduce it and/or obtain live logging data has finally been reproduced.
Internally, we have information here:
https://newrelic.atlassian.net/browse/GTSE-13353
It looks like in StatsImpl and RepsonseTimeStatsImpl we need to synchronize on a few metric aggregation points.
newrelic-java-agent/newrelic-agent/src/main/java/com/newrelic/agent/stats/ResponseTimeStatsImpl.java
Line 67 in 6be021f
newrelic-java-agent/newrelic-agent/src/main/java/com/newrelic/agent/stats/ResponseTimeStatsImpl.java
Line 128 in 6be021f
newrelic-java-agent/newrelic-agent/src/main/java/com/newrelic/agent/stats/StatsImpl.java
Line 57 in 6be021f
newrelic-java-agent/newrelic-agent/src/main/java/com/newrelic/agent/stats/StatsImpl.java
Line 123 in 6be021f
The links here should not be considered an exhaustive description of where all the problem exists. Addition metric debug information is provided in the logs from the reporting customers application, so we should double check that there aren't other places that show the Supportability metric for negative values. We should check to see if the DefaultTracer had any hits in those logs.
Additional context
[TIP]: # ( Add any other context about the problem here. For example, relevant community posts or support tickets. )
The text was updated successfully, but these errors were encountered: