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

Can I use consul for service discovery? #3902

Closed
liaol opened this issue Feb 12, 2025 · 3 comments
Closed

Can I use consul for service discovery? #3902

liaol opened this issue Feb 12, 2025 · 3 comments

Comments

@liaol
Copy link

liaol commented Feb 12, 2025

I deploy pyroscope microservices without k8s.
Can I use consul for service discovery?
Can each component register to consul and discovery others from consul on start ?
Like this:

ingester:
    lifecycler:
        ring:
            kvstore:
                store: consul
                prefix: collectors/
                consul:
                    host: consul:8500

distributor:
    ring:
        kvstore:
            store: consul
            prefix: collectors/
            consul:
                host: consul:8500

Thanks all ~

@kolesnikovae
Copy link
Collaborator

Hi @liaol! I'm afraid, only memberlist is fully supported. Consul, however, could provide the DNS SRV record for discovery.

Our CLI and config references might be confusing – I'll create an issue to address it.

@kolesnikovae
Copy link
Collaborator

Created #3918

@liaol
Copy link
Author

liaol commented Feb 14, 2025

@kolesnikovae Thanks for reply.

Memberlist isn't really working for me unless I use DNS SRV, because one node don't know other node's address when starting.
But Pyroscope is working fine with the config above, I'll get back if any problems come up."

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

No branches or pull requests

2 participants