-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Exposing consul service instance meta data #196
Comments
I would need to dig deeper into this but maybe could you give me a concrete example? |
Service instances in Consul can include both
We use the So exposing this metadata with consul_exporter can be useful, for example, it can expose service versions in one central location without the need to instrument every service individually with info_* metrics. For example, today consul_exporter exposes tags like this:
Would be nice if similarly we could see the meta:
|
I can see how it could potentially lead to high label cardinality. At the very least it should be behind a flag. |
Yep, that would make sense, similar to kv filter. Its been a while since I wrote Go, but I can give it a crack, would a PR be welcome? |
sure go for it :) |
Took me a while to get back to it but just opened a PR for initial attempt. Let me know if I'm in a good direction. Cheers. |
Hi @m1keil , I have the same requirement: using "consul_service_meta" instead of "consul_service_tag". What's the current status ? |
I opened up an initial PR with a POC (#204), waiting to hear feedback from maintainers if this is the way to go. |
I will look at this in the coming days. |
no worries @roidelapluie, cheers! |
Currently, consul_exporter exposes both catalogue KV and service tags via
consul_service_tag
.Registered services in consul can also expose metadata which is a KV structure but without the special meaning of tags during lookups.
I wonder if support for service metadata is something that you would consider adding in a future release?
The text was updated successfully, but these errors were encountered: