New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stackdriver-prometheus vs prometheus-to-sd #15

Closed
geekflyer opened this Issue Aug 22, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@geekflyer

geekflyer commented Aug 22, 2018

Hi,

I'm a bit confused as to how stackdriver-prometheus relates to prometheus-to-sd and what are the pros / cons of using each? What is the recommended option way of sending prometheus-like metrics to stackdriver?

Both projects are maintained by Google which doesn't make the choice easier :)
I hope someone can clarify, perhaps adding a note to the README would be useful for others.

@jkohen jkohen self-assigned this Aug 22, 2018

@jkohen

This comment has been minimized.

Contributor

jkohen commented Aug 22, 2018

@geekflyer thanks for bringing that up. My recommendation is to go with stackdriver-prometheus because it's developed and supported for Stackdriver users, but you can help yourself to either tool.

Google develops stackdriver-prometheus primarily for Stackdriver users and gives support to Stackdriver users. We designed the user experience to meet the expectations of Prometheus users and to make it easy to run with Prometheus server (we are working on a Prometheus server sidecar version). stackdriver-prometheus is intended to monitor all your applications, Kubernetes and beyond.

Google develops prometheus-to-sd primarily for Google Kubernetes Engine to collect metrics from system services in order to support Kubernetes users. We designed the tool to be lean when deployed as a sidecar in your pod. It's intended to support only the metrics the Kubernetes team at Google needs; you can use it to monitor your applications, but the user experience could be rough.

/cc @piosz

@geekflyer

This comment has been minimized.

geekflyer commented Sep 17, 2018

Hi @jkohen thanks for your prompt answer. Unfortunately I'm still not 100% clear what I should use in our scenario. I should have probably clarified this before, but here's a bit more context:

  • we run GKE
  • we aim to monitor k8s state metrics like "replicas_available" for our own k8s apps that run on gke
  • we would run stackdriver-prometheus or prometheus-to-sd both in gke / k8s
  • we don't aim to use prometheus directly (i.e. no query), but rather make use of one those packages only to be able to scrape metrics which are only exported in prometheus format (e.g. kube-state-metrics).
@jkohen

This comment has been minimized.

Contributor

jkohen commented Sep 25, 2018

@geekflyer I believe stackdriver-prometheus will meet your needs, and it's what I would recommend. If that's not the case, I'd like to hear more about your needs.

@jkohen jkohen closed this Oct 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment