Custom metrics issues
See original GitHub issueI’m using stagemonitor (lastest) + elastic + grafana through the docker-compose.yml
provided in wiki. However, there are two problems:
-
Custom metrics are not being gathered at all (I just checked on Kibana, there are no entries for
name: timer
andname: gauge*
). The code has tons of@Timed
methods being called, though. -
The custom metrics dashboard is broken. The query filters for
signature
(which I don’t know what it is) and breaks the graph:
Failed to parse query [name: timer AND application: app AND host: ("host1" OR "host2" OR "host3") AND instance: ("myapp") AND signature: ()]
There are no erros on logs, so I’m not attaching them. Please let me know if you need futher information.
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Issues · kubernetes-sigs/custom-metrics-apiserver - GitHub
Framework for implementing custom metrics support for Kubernetes - Issues · kubernetes-sigs/custom-metrics-apiserver.
Read more >Track server errors with custom metrics and alerts
For example, while built-in metrics show you issues with HTTP responses and requests, a custom metric can identify 500-level server errors. These types...
Read more >Collect custom metrics (APM, browser, mobile)
For an overview of custom metrics, including examples, best practices, and a quick reference by New ... For more information, see Metric grouping...
Read more >Custom Metrics - Datadog Docs
Naming custom metrics · Metric names must start with a letter. · Metric names must only contain ASCII alphanumerics, underscores, and periods. Other...
Read more >Problems with custom metrics - SonarQube - Sonar Community
I am trying to create a custom metric and trying to add it in each project's configuration. Its showing pending status.
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
Thanks a lot felix. It worked 👍
Ha, thats a cheesy “problem”: Your package name is
org.stagemonitor.mytest.task
but in order to exclude stagemonitor from transforming itself, the packageorg.stagemonitor
is excluded implicitly. So please choose a different packaging structure.