jaegertracing / jaeger

CNCF Jaeger, a Distributed Tracing Platform
https://www.jaegertracing.io/
Apache License 2.0
20.4k stars 2.43k forks source link

Recommended collector topolgy in jaeger #1650

Closed prana24 closed 2 years ago

prana24 commented 5 years ago

Requirement - what kind of business use case are you trying to solve?

Problem - what in Jaeger blocks you from solving the requirement?

Proposal - what do you suggest to solve the problem or improve the existing situation?

Any open questions to address

Experts, Do we have any recommended topology of collectors ?
We want to go with multiple collector being deployed in different kubernetes clusters rather than multiple jaeger collector in one Cluster.
By doing this we want to avoid single point of failure . Is there any issue in this topology ? Would like to hear views.

jpkrohling commented 5 years ago

As far as the collector is concerned, it doesn't matter whether all instances are part of the same pod or are deployed in different clusters. If anything, I'd place one pod with a couple replicas close to where your agents are. If you have your application deployed in several clusters, I'd then have one Jaeger instance per cluster, sharing the same backing storage but I wouldn't create additional clusters just to host a highly-available collector setup.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

stale[bot] commented 2 years ago

This issue has been automatically closed due to inactivity.