Eureka discovery

[drax68]

Hi. Could you please add Eureka to discovery backends?
It has quite straightforward api and existing client in go

[juliusv]

If that is a widely-enough used SD mechanism, then I can imagine it could get added to Prometheus itself. However, SD mechanisms are usually added (via PRs) and maintained by people who actually use a specific type of service discovery, since they are in the best position to test it and know the practical design and implementation considerations. So I guess, feel free to send a PR - and it would help if there was some interest in maintaining it, as well :)

[pparth]

+1

[fabMrc]

+1

[manuelpolacek]

+1

[hakamairi]

+1

[ankurbhakta]

+1

[jtlisi]

+1

[ipalbeniz]

+1

[fedy2]

+1

[olafgeibig]

+1

[chenapan]

+1

[itshanney]

+1

[joaovicente]

+1

[ankurbhakta]

+1

[fabxc]

Friendly reminder that commenting +1 is mostly noise for maintainers and alone does not incentivise us to work on any particular feature. As an open source project, we welcome productive discussion and contributions.
If you just want to express that you agree with the feature request, GitHub has reaction emojis, which do not flood our inboxes.

[yarix]

+1

[fabxc]

Locking this issue now.

[tine2k]

I have written an adapter that you can deploy with your Eureka instance. This adapter provides several HTTP endpoints that return information of the registered services and are compatible with the Prometheus' Consul discovery client (consul_sd_config). It is available as a Spring Boot starter on Github: https://github.com/twinformatics/eureka-consul-adapter

[davidkarlsen]

Very interesting - I looked at it yesterday - and it is just what I need (as I want to avoid the consul full-mesh stuff for agents). Does eureka have a label concept like consul? And are these mapped over?

[tine2k]

No, eureka does not support labels. However, there is something called node metdata that clients can send along with their registration. By overriding InstanceInfoMapper of the adapter you return this metadata as service tags, which you can use as labels in Prometheus.

[simonpasquier]

Closing the issue as unfortunately, we are currently not accepting new integrations. See #1506 (comment) for an alternative.

We can only provide the stability and performance we want to provide if we can properly maintain the codebase. This includes, amongst others, test integrations in an automated and scalable fashion. For this reason, we are suggesting people integrate with the help of our generic interfaces. We have an integrations page on which integrations using our generic interfaces are listed.

Even if existing integrations can not be tested in an automated fashion, we will not remove them for reasons of compatibility. This also means that any additions we take on, or any changes to existing integrations we make or accept, will mean maintaining and testing these until at least the next major version, realistically even beyond that.

Feel free to question this answer on our developer mailing list, but be aware it's unlikely that you will get a different answer.

[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.