question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Stackdriver metrics not ending up in Stackdriver

See original GitHub issue

Micrometer 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:

  1. 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. missing-global
  2. When debugging, the StackdriverMeterRegistry#publish call is just done once. With the LoggingMeterRegistry, the publish-method is called every interval.
  3. Any way of using Spring integration with actuator?
  4. Feature request: Can we use the prefix for the custom metric, so instead of custom/jvm/buffer/etc something like custom/{prefix}/jvm/buffer/etc? This makes it much easier to distinguish between services running in the same project.
  5. 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:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:22 (7 by maintainers)

github_iconTop GitHub Comments

5reactions
itzgcommented, Jan 10, 2019

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

3reactions
amohabircommented, Jan 9, 2019

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

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found