You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2023. It is now read-only.
Describe the bug
TracingInstrumentation#instrumentExecutionResult is being executed twice per query and MetricsInstrumentation#instrumentExecutionResult is never called because it overrides a deprecated method that is no longer called by graphql.execution.instrumentation.ChainedInstrumentation. This results in tracing metrics always being included in the extensions of results even when graphql.servlet.tracing-enabled is set to metrics-only and actuator metrics are never recorded.
To Reproduce
Steps to reproduce the behavior:
In a graphql spring boot project, set graphql.servlet.tracing-enabled to metrics-only and graphql.servlet.actuator-metrics to true.
Run server and submit a query of any complexity/simplicity.
Notice that extensions is populated with tracing information.
Submit a request to the server's JMX metrics endpoint.
Notice that no graphql metrics are found.
Expected behavior
When graphql.servlet.tracing-enabled is set to metrics-only and graphql.servlet.actuator-metrics is set to true. The response should exclude tracing from extensions and graphql metrics should be present in the response of a request to obtain the server's JMX metrics.
Desktop (please complete the following information):
OS: macOS Ventura 13.4 (M1 processor)
Browser N/A
Version 14.1.0
Client: Insomnia 2023.2.2
Additional context
The API seems to have been deprecated and using a different method for some time now. Perhaps I have something wrong with my implementation that is making me see this issue and not others?