-
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
[Stack Monitoring] Support endpoint counters in APM #44001
Labels
enhancement
New value added to drive a business result
Feature:Stack Monitoring
Team:Monitoring
Stack Monitoring team
Milestone
Comments
cachedout
added
enhancement
New value added to drive a business result
Feature:Stack Monitoring
Team:Monitoring
Stack Monitoring team
labels
Aug 26, 2019
Pinging @elastic/stack-monitoring |
This was referenced Aug 26, 2019
This was referenced May 7, 2020
This was referenced May 11, 2020
2 tasks
10 tasks
8 tasks
This was referenced May 26, 2020
This was referenced May 27, 2020
This was referenced Jun 5, 2020
10 tasks
10 tasks
This was referenced Nov 25, 2020
10 tasks
10 tasks
This was referenced Nov 29, 2020
This was referenced Dec 1, 2020
2 tasks
This was referenced Dec 3, 2020
This was referenced Dec 10, 2020
10 tasks
1 task
10 tasks
1 task
10 tasks
This was referenced Jun 22, 2023
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New value added to drive a business result
Feature:Stack Monitoring
Team:Monitoring
Stack Monitoring team
(Copied out of a document originally created by @simitt )
With #2142 (planned for 7.4) we introduced dedicated monitoring counters per endpoint. The change was made to keep the counters meaningful, e.g. requests to the APM Server's root endpoint made by some agents for figuring out server details should not be shown as part of requests to the Intake API processing actual events.
With more agents using the server's root endpoint, and especially with introducing a new endpoint for agents to fetch the remote configuration, a distinction of requests is introduced, allowing for a better monitoring experience.
The names of the counters used so far have not been changed, to not break anything, but requests that already added up to these counters while belonging to a different endpoint have been removed.
Currently used counters:
apm-server.server.*: These counters will still be present to not introduce any breaking changes, but will only contain information about requests/responses from the Intake API endpoint, responsible for processing uploaded events.
Newly introduced counters are:
apm-server.acm.*: counting requests and responses to the newly introduced agent remote configuration endpoint (beta in 7.3), that agents are using for reloading config options. These counters are interesting, but should be clearly separated from requests sending events.
apm-server.sourcemap.*: counting sourcemap uploads; Uploading sourcemaps is a manual step that probably happens once per deploy for RUM agents. Showing these counters does not seem too important for now.
apm-server.root.*: requests to the server's root endpoint, mainly expected for healthcheck requests or figuring out details about the server's version etc. Not relevant for showing in the monitoring tab at the moment.
Suggested Changes in the UI:
Change visualization: title Response Count -> Response Count Intake API
Change visualization title Response Errors -> Response Errors Intake API.
Change visualization title Requests -> Requests Intake API
Add visualization for Response Count Agent Configuration Management
Following counters should be included:
apm-server.acm.response.count
apm-server.acm.response.errors.count
apm-server.acm.response.valid.ok
apm-server.acm.response.valid.notmodified
Add visualization for Response Errors Agent Configuration Management
Following counters should be included:
apm-server.acm.response.errors.forbidden
apm-server.acm.response.errors.unauthorized
apm-server.acm.response.errors.unavailable
apm-server.acm.response.errors.method
apm-server.acm.response.errors.invalidquery
Add visualization for Requests Agent Configuration Management
Following counters should be included:
apm-server.acm.request.count
The text was updated successfully, but these errors were encountered: