Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix default value explanation for SPLUNK_PROFILER_LOGS_ENDPOINT #318

Merged
merged 1 commit into from
Oct 23, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion specification/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -169,7 +169,7 @@ instance using the following environment variables:
| `SPLUNK_ACCESS_TOKEN` | | Access token added to exported data. [1] |
| `SPLUNK_PROFILER_CALL_STACK_INTERVAL` | 10000 | Interval at which call stacks are sampled (in ms) [5] |
| `SPLUNK_PROFILER_ENABLED` | false | Whether CPU profiling is enabled. [2] [5] |
| `SPLUNK_PROFILER_LOGS_ENDPOINT` | * | Where profiling data is sent. Defaults to the value in `OTLP_EXPORTER_OTLP_ENDPOINT` [5] |
| `SPLUNK_PROFILER_LOGS_ENDPOINT` | * | Where profiling data is sent. Defaults to the value in `OTEL_EXPORTER_OTLP_ENDPOINT` [5] |
| `SPLUNK_PROFILER_MEMORY_ENABLED` | false | Whether memory profiling is enabled. [2] [6] |
| `SPLUNK_REALM` | `none` | Which realm to send exported data. [3] |
| `SPLUNK_TRACE_RESPONSE_HEADER_ENABLED` | true | Whether `Server-Timing` header is added to HTTP responses. [4] |
Expand Down