-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Monitoring] Added ability to possibly distinguish between Agent type metrics in APM #95129
Conversation
Pinging @elastic/stack-monitoring (Team:Monitoring) |
x-pack/plugins/monitoring/public/components/apm/apm_metrics.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/monitoring/public/components/apm/apm_metrics.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't actually run it yet, but LGTM apart from the version check comment I left.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wasn't able to run it, but changes LGTM
I talked to @igoristic and I am not sure we fully understand this change yet, so I'm going to reach out to some folks out of band and get clarification. If we still need to land this for 7.13, I'm comfortable with talking about landing it as a text/visual bug fix, or we can push it to 7.13.1/7.14 if that's okay also. |
Can you please share your concerns? We are actually relying on this change. The |
@igoristic could you please re-request a review once this is finalized? |
Will do 👍 Though, nothing has changed since the last approval. Just some test fix and conflict resolves |
💚 Build SucceededMetrics [docs]Module Count
Async chunks
History
To update your PR or re-run it, just comment with: cc @igoristic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
… metrics in APM (elastic#95129) * Added version and cloud check * Fixed tests * Code review feedback * Fixed tests * added versions * added version * ... * Removed default version * .. * Fixed test * fixed tests # Conflicts: # x-pack/plugins/monitoring/server/lib/apm/_apm_stats.js # x-pack/test/api_integration/apis/monitoring/apm/fixtures/cluster.json
…nt type metrics in APM (#95129) (#98388) * [Monitoring] Added ability to possibly distinguish between Agent type metrics in APM (#95129) * Added version and cloud check * Fixed tests * Code review feedback * Fixed tests * added versions * added version * ... * Removed default version * .. * Fixed test * fixed tests # Conflicts: # x-pack/plugins/monitoring/server/lib/apm/_apm_stats.js # x-pack/test/api_integration/apis/monitoring/apm/fixtures/cluster.json * Update cluster.json * Update _apm_stats.js
…t type metrics in APM (#95129) (#98387) * [Monitoring] Added ability to possibly distinguish between Agent type metrics in APM (#95129) * Added version and cloud check * Fixed tests * Code review feedback * Fixed tests * added versions * added version * ... * Removed default version * .. * Fixed test * fixed tests # Conflicts: # x-pack/plugins/monitoring/server/lib/apm/_apm_stats.js # x-pack/test/api_integration/apis/monitoring/apm/fixtures/cluster.json * Update cluster.json * Update _apm_stats.js
@igoristic I wanted to test this on cloud QA but I see |
Resolves #97879
In this PR we're changing some headers from "APM Server" to "APM and Fleet Server" to help users understand that data from other Agent subprocesses might also be included if the monitoring cluster is in cloud and has (at least one) node with version 7.13 (or greater). More information in #97879