You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requirement - what kind of business use case are you trying to solve?
Exclude/Ignore one or more services from being considered by the jaeger-spark-job-dependencies.
Problem - what in Jaeger blocks you from solving the requirement?
In some cases, you may need to exclude some services from being considered by the job to be shown in the dependency graph. To be precisely specific, If you (for some reasons) enabled/considered your reverse proxy/ingress controller/gateway to add a span during routing the message, you will end up with a graph where you find the gateway is connected to every service and everywhere. Since it makes the graph more complex to understand, you may prefer to exclude it from the dependency graph.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Introduce a new optional environment variable as an input for the job with all the services' names required to be ignored.
Requirement - what kind of business use case are you trying to solve?
Exclude/Ignore one or more services from being considered by the jaeger-spark-job-dependencies.
Problem - what in Jaeger blocks you from solving the requirement?
In some cases, you may need to exclude some services from being considered by the job to be shown in the dependency graph. To be precisely specific, If you (for some reasons) enabled/considered your reverse proxy/ingress controller/gateway to add a span during routing the message, you will end up with a graph where you find the gateway is connected to every service and everywhere. Since it makes the graph more complex to understand, you may prefer to exclude it from the dependency graph.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Introduce a new optional environment variable as an input for the job with all the services' names required to be ignored.
Please check PR #93
The text was updated successfully, but these errors were encountered: