Skip to content
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

prometheus support in nats-operator #40

Closed
RyanGordon opened this issue Mar 26, 2018 · 4 comments · Fixed by #84
Closed

prometheus support in nats-operator #40

RyanGordon opened this issue Mar 26, 2018 · 4 comments · Fixed by #84

Comments

@RyanGordon
Copy link

When nats-io/prometheus-nats-exporter#48 is completed, it would be great if the option to add prometheus exporter was added to nats-operator.

@wallyqs
Copy link
Member

wallyqs commented Mar 26, 2018

Yep agree, will take a look at adding support

@ColinSullivan1
Copy link
Member

A note for when we implement this... the Prometheus recommended architecture is to have a prometheus NATS exporter paired with each NATS server.

@wallyqs
Copy link
Member

wallyqs commented Mar 26, 2018

That's right, so I think that the exporter container PodSpec would be running as part of the same PodSpec of the deployed NATS servers. (1 Pod = exporter + nats server)

@wallyqs wallyqs added this to the v0.2.4 milestone Jun 8, 2018
@entone
Copy link

entone commented Jul 25, 2018

Any update on this?

I've added prometheus-nats-exporter, and pointed it at the headless mgmt service created by the operator. It appears to find all the pods in the cluster, but does not enumerate the pods, also some variables don't seem to be aggregated correctly.

@wallyqs wallyqs mentioned this issue Nov 19, 2018
@pires pires removed this from the v0.2.4 milestone Dec 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants