add specific config options to config doc

[jackshirazi]

Adding the full set of config options that are additional or have different defaults from the upstream OpenTelemetry agent

[colleenmcginnis]

@jackshirazi what do you think about reorganizing this content in a structure like the content below? (I'm not sure where OTEL_INSTRUMENTATION_RUNTIME-TELEMETRY_EMIT-EXPERIMENTAL-TELEMETRY fits in...)

---

Configuration options

Because the Elastic Distribution of OpenTelemetry Java is an extension of the OpenTelemetry Java agent, it supports:

• General OpenTelemetry configuration options
• Configuration options from OpenTelemetry extensions that are included with EDOT Java
• Configuration options that are only available in EDOT Java

OpenTelemetry configuration options

EDOT Java supports all configuration options listed in the OpenTelemetry General SDK Configuration documentation and OpenTelemetry Java agent documentation.

EDOT Java uses different defaults than the OpenTelemetry Java agent for the following configuration options:

Option	EDOT Java default	OpenTelemetry Java agent default
OTEL_RESOURCE_PROVIDERS_AWS_ENABLED	enabled	disabled (docs)
OTEL_RESOURCE_PROVIDERS_GCP_ENABLED	enabled	disabled (docs)

Configuration options from OpenTelemetry extensions

EDOT Java includes several OpenTelemetry extensions from the OpenTelemetry Java agent contrib repo. These extensions offer the following additional OTEL_ options:

Option(s)	Extension	Description
OTEL_SERVICE_NAME	Resource providers	Can be set as usual, but if not set this will be inferred when the EDOT Java agent is running in various application servers.
OTEL_INFERRED_SPANS_*	Inferred Spans
OTEL_SPAN_STACK_TRACE_MIN_DURATION	Span stacktrace capture	in milliseconds, defaults to 5ms
OTEL_INSTRUMENTATION_RUNTIME-TELEMETRY_EMIT-EXPERIMENTAL-TELEMETRY		Experimental runtime metrics are enabled by default. Set otel.instrumentation.runtime-telemetry.emit-experimental-telemetry to false to disable them.

EDOT Java configuration options

In addition to general OpenTelemetry configuration options, there are two kinds of configuration options that are only available in EDOT Java.

Elastic-authored options that are not yet available upstream

Additional OTEL_ options are configuration options that Elastic plans to contribute upstream to the OpenTelemetry Java agent but are not yet available in the OpenTelemetry Java agent.

Currently there are no additional OTEL_ options that are only available in EDOT Java.

Elastic-specific options

ELASTIC_OTEL_ options that are specific to Elastic and will always live in EDOT Java (in other words, they will not be added upstream) including:

Option(s)	Extension	Description
ELASTIC_OTEL_UNIVERSAL_PROFILING_INTEGRATION_*	Universal profiling integration

[jackshirazi]

Much better thank you! Do you want to apply the changes to the branch or shall I?

[colleenmcginnis]

I'd be happy to apply the change and push a commit after my afternoon meetings (unless you want to go ahead to get it done earlier).