Proposal: Rename http.responseCodes metrics
See original GitHub issueHello,
We currently have the Jenkins UI response code metrics named as follows:
http_responseCodes_<responseType>_total
I would suggest the following convention to keep it consistent with the other metrics, and make it easier to discover:
- Prefix metric name with
jenkins_
- Add response code in metric label instead of in metric name. The response codes have a limited cardinality thus should not be a problem
After the suggested rename, the metrics will look like:
jenkins_http_response_total
And then if you’d like to filter by code
jenkins_http_response_total{code="404"}
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Proposal for adding http_req_errors metric #1311 - GitHub
This is a proposal for adding a new, standard metric to k6 called http_req_errors that records the number of failed HTTP requests.
Read more >What best practices are recommended for naming metrics and ...
What best practices are recommended for naming metrics and tags? Datadog recommends certain best practices for naming metrics, tags, and services.
Read more >Guidance for metric and dimension names
Naming standards for metric and dimensions in Splunk Observability Cloud. ... A metric name that represents the number of HTTP response code 500...
Read more >Create custom metrics with the API - Monitoring - Google Cloud
Learn how to create custom metrics and how to write custom metric data by using the Cloud Monitoring API.
Read more >Use a mapping template to override an API's request and ...
Learn how to override a an API's request and response parameters and status codes.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@markyjackson-taulia why was this issue closed? Has this been fixed in a later release that I missed?
Please also keep best practices in mind and have a look how others expose such common HTTP metrics.