Rancher support?

[jmreicha]

Rancher has a nice API, would it be possible to add support for it, similar to the other SD configurations currently supported?

It would be cool to be able to configure Prometheus based on Rancher labels for example.

[fabxc]

In general, absolutely.
It mostly needs someone who writes the implementation (with guidance of course) and agrees to maintain it in the future.

[Rucknar]

@jmreicha basic support can be used through the following. It should expose host/service/stack and label metrics so far... it's quite basic at the moment but open to any pull-requests if you have the time.

https://github.com/Rucknar/prometheus-rancher-exporter

[brian-brazil]

That's a rancher exporter (which isn't listed on http://prometheus.io/docs/instrumenting/exporters/ - could you send a PR?), this issue is about service discovery support.

[jmreicha]

@Rucknar Cool, I will check it out. Thanks for the update!

[Rucknar]

@brian-brazil my mistake, will send a PR!

[jmreicha]

@Rucknar Getting around to testing this I am running in to an issue getting the prometheus-rancher-exporter Docker image to play with the Prometheus Rancher stack but it looks like issues are closed for the project? What's the best way report and get help with issues?

Updated. I posted my issue to your (awesome) getting started guide, it probably belongs there anyway.

[brutus333]

@fabxc: I am willing to take this assignment since we are trying to go into production with Rancher & Prometheus and we need a better solution.
I clearly need some guidance - I will try to use consul_sd code as a starting point but I'm not sure if it's enough.
For rancher metadata I am planning to use the go client: https://github.com/rancher/go-rancher-metadata. If additional feature would be needed, I will PR this code also.
Do you have any advice to start working on this feature?

[fabxc]

The Go client unfortunately lacks documentation but AFAICS there is no polling for changes. In that case one would just refresh every x seconds. For that case the DNS SD is more suitable as an example than the Consul one. It's also easier.

The biggest challenge will be providing testing.
After accepting SD integrations without tests in the past, due to recent regressions I decided to no longer accept such PRs.

I would say just start implementing as far as you get and open a pull request to walk through missing steps together.

[burdiyan]

Does anyone have any new about that? I'm thinking about implementing Rancher SD for Prometheus but wonder if there is anybody who already started to do something.

[brutus333]

Hello!
I took a different route, please see: https://github.com/brutus333/prom-rancher-sd
The idea was borrowed from https://github.com/DanielDent/prom-rancher-sd which used json file for Prometheus integration.
I have also a rancher catalog which uses this:
https://github.com/brutus333/rancher-extra-catalog
It is not the most elegant solution, but it was an easy workaround.
A real rancher_sd implementation would be clearly better.

[Rucknar]

@brian-brazil Given rancher 2.0 moving to a kubernetes base, suggest this one is closed off?
DNS service discovery works as-is, kubernetes should be usable once 2.0 is released.

[brian-brazil]

That sounds reasonable to me.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.