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
| `splunk.access.token` | Yes | The Splunk [org access token](https://docs.splunk.com/observability/admin/authentication-tokens/org-tokens.html).
42
-
| `splunk.realm` | Yes | The Splunk realm where data will be sent. This is commonly `us0` or `eu0` etc.
43
-
| `otel.*` or `splunk.*` | Optional | All additional credentials starting with these prefixes will be appended to the application's JVM arguments as system properties.
| `splunk.realm` | Yes | Splunk realm where data will be sent. This is commonly `us0`, `eu0`, and so on. See [Available regions or realms](https://docs.splunk.com/observability/en/get-started/service-description.html#available-regions-or-realms) for more information.
45
+
| `otel.*` or `splunk.*` | Optional | All additional credentials starting with these prefixes are appended to the application's JVM arguments as system properties.
44
46
45
47
### Choosing a version
46
48
47
-
Most users should skip this and simply use the latest version of the agent available (the default).
48
-
To override the default and choose a specific version, you can use the `JBP_CONFIG_*` mechanism
49
+
To override the default and choose a specific version, use the `JBP_CONFIG_*` mechanism
49
50
and set the `JBP_CONFIG_SPLUNK_OTEL_JAVA_AGENT` environment variable for your application.
50
51
51
-
For example, to use version 1.16.0 of the Splunk OpenTelemetry Java Instrumentation, you
52
-
could run:
52
+
For example, to use version 1.16.0 of the Splunk OpenTelemetry Java Instrumentation, run:
0 commit comments