Yen-Cheng Chou

@sahilpalvia I also have same use case which we want to scale up/down based on how fast KCL application consumes. this metric will be helpful.

seems like abseil/abseil-cpp#38 will be tracked under abseil/abseil-cpp#111 now.

Still work in progress - as I haven't provided rationale yet.

@jkohen ready for review. please take a look on the new change. The rationale is updated in [1st comment](https://github.com/Stackdriver/stackdriver-prometheus-sidecar/pull/101#issue-258940788) of the PR.

@jcortejoso - I think the metric descriptor may still show up in other lines of the debug logs - in the log you provided, the message may be truncated. I...

Thanks @Pamir for creating the repo with files. Let me look into your files above and I will get back to you if I have any question.

Can you double check the version of prometheus you use? Why I ask this is because I see the repo you provided use [prometheus-operator v0.26.0](https://github.com/Pamir/stackdriver-prometheus-sidecar-configuration/blob/477c6d3f519f5b3cfa84072d097426bac20cac0e/values.yaml#L605-L606), and it uses prometheus v2.5.0...

Hi @Pamir, we added debug logs with #110, and it is included in release [v0.4.1]( https://github.com/Stackdriver/stackdriver-prometheus-sidecar/releases/tag/v0.4.1) . If there is no data shown up in Stackdriver, you can turn on...

Hi @matthewgoslett, Thanks for the report. I haven't used kube-prometheus yet, so I need to gather some further information. 1. How do you specific where Prometheus write to its storage,...

@roidelapluie PTAL.