feat(core): add configurability and service graph support

[LMarkie]

• Add LOG_LEVEL env var to configure logging level (none, debug, info, warn, error)
• Add JAEGER_USE_DEFAULT_PORT env var to control HTTP port behavior
• Add docker file to expose SSE transport
• Add service graph implementation to extract dependency data

[serkan-ozal]

Hi @LMarkie,

Thanks for your contribution.

But, I am not able to find the API specification for the service dependencies here: https://github.com/jaegertracing/jaeger-idl/

Could you please point me where the service dependency API is specified/defined?

[LMarkie]

Hi @LMarkie,

Thanks for your contribution.

But, I am not able to find the API specification for the service dependencies here: https://github.com/jaegertracing/jaeger-idl/

Could you please point me where the service dependency API is specified/defined?

It's an internal route, so not really recommended to be used externally but would give an easy way to see how services are connected. https://www.jaegertracing.io/docs/2.6/apis/#service-dependencies-graph

The main change I wanted was to be able to configure the mcp server with URLs such as http://example.com/some/path. It currently adds a port. I've included extra changes in case you wanted them.

[serkan-ozal]

Hi @LMarkie,

Sorry for late response.

I couldn't fully understand the motivation behind the newly introduced JAEGER_USE_DEFAULT_PORT env var. As far as I understood, you want to set JAEGER_USE_DEFAULT_PORT env var to false, so you will have Jaeger URL without port.

But instead of introducing and configuring new env var, doesn't setting JAEGER_PORT env var to 80 for plain http or 443 for https work?