Infer service name and set it at startup

[jackshirazi]

Is your feature request related to a problem?

If service name is not explicitly set (using the two options) then there is a generic default unknown_service. This is not useful for auto-instrumentation

Describe the solution you'd like

The service name should be inferred as best as possible, if some property is set to true (eg OTEL_ELASTIC_AUTO_SERVICE_NAME=true).

Describe alternatives you've considered

Suggestions welcome

Additional context

While in most cases you can ask the user to set the service name explicitly - which is best practice - in the case of zero-code configuration this would add additional per deployment configuration which is not the optimal experience

[SylvainJuge]

From the linked issues this is about web applications deployed in a weblogic server

• for now the service.name is a resource attribute and set only once for the whole process.
• there has been a few discussions for a signal level resource attribute, or providing ways to provide dynamic resource attributes, but those haven't been anywhere as far as I know @AlexanderWert do you remember anything like this in semconv ? Given this tends to be a java specific issue, it might be hard to get some shared interest in semconv at least to get reviews. Update: see related otel conversation
• the weblogic server is not supported in contrib resources providers, so there is no single value captured for weblogic, which isn't great and could be contributed

[SylvainJuge]

There is a draft OTEP specification change open-telemetry/opentelemetry-specification#4316 for this, so contributing to it could help unblock having a proper solution for this.

[SylvainJuge]

The previous otep has become stale, but there is another one still active that might help with this: open-telemetry/opentelemetry-specification#4665