Stackdriver metrics not ending up in Stackdriver
See original GitHub issueMicrometer version: 1.1.0 Spring boot version: 5.1.0 JDK version: 11
There seem to be multiple issues with the Stackdriver integration of Micrometer:
- Metrics are created, but are not under the Global resource it seems. (The ones with global were created using our current solution) See also the screenshot below.
- When debugging, the
StackdriverMeterRegistry#publish
call is just done once. With theLoggingMeterRegistry
, the publish-method is called every interval. - Any way of using Spring integration with actuator?
- Feature request: Can we use the prefix for the custom metric, so instead of
custom/jvm/buffer/etc
something likecustom/{prefix}/jvm/buffer/etc
? This makes it much easier to distinguish between services running in the same project. - I’m also missing the documentation right now. 😉
See also the demo zip I have added for my sample code. monitoringdemo.zip
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:22 (7 by maintainers)
Top Results From Across the Web
Troubleshoot the Ops Agent | Operations Suite - Google Cloud
Go to the Agent is installed but not running section first to fix that condition.
Read more >Not all prometheus metrics are showing in google Stackdriver
When I query into the prometheus, I find all the metrics. But in the stackdriver metrics explorer, I can't find all the metrics(...
Read more >Exception sending metrics to Stackdriver EventID 255
I set up a log exclusion in GCP as Igor suggested to ignore the "no error message available" messages I receive in my...
Read more >How to Setup Monitoring Agent in Google Cloud - YouTube
In this video you will learn how to configure stackdriver agent for monitoring GCE instance along with custom application.
Read more >Stackdriver Custom Metrics in Python | by Yuri Grinshteyn
As part of the GCP Live team, I recently delivered this session introducing the basics of the Stackdriver Monitoring API and showed an ......
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 Free
Top 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
I was able to confirm that after filtering down to just a single gauge metric its value properly flowed to Stackdriver. Before that I wasn’t able to confirm where the thread was dying, but stepping through the debugger it was indeed dying somewhere before reaching
https://github.com/micrometer-metrics/micrometer/blob/master/implementations/micrometer-registry-stackdriver/src/main/java/io/micrometer/stackdriver/StackdriverMeterRegistry.java#L154
So the following line throws an
ArrayOutOfBoundsException
, when creating a new distribution it seems. After the exception is thrown, the thread is seemingly killed and never used again. This happens when a time series for a meter needs to be created.https://github.com/micrometer-metrics/micrometer/blob/master/implementations/micrometer-registry-stackdriver/src/main/java/io/micrometer/stackdriver/StackdriverMeterRegistry.java#L391