fix: close idle OTLP connections before the collector does (#184)
Unbound Release / Check Preconditions (push) Successful in 27s
Unbound Release / Create Tag (push) Skipped
otelsetup / test (push) Skipped
otelsetup / vulnerabilities (push) Skipped
Unbound Release / Generate Changelog and Handle PR (push) Successful in 39s
Unbound Release / Create Release (push) Successful in 29s
Release / release (push) Successful in 1m14s
pre-commit / pre-commit (push) Successful in 3m27s
Unbound Release / Check Preconditions (push) Successful in 27s
Unbound Release / Create Tag (push) Skipped
otelsetup / test (push) Skipped
otelsetup / vulnerabilities (push) Skipped
Unbound Release / Generate Changelog and Handle PR (push) Successful in 39s
Unbound Release / Create Release (push) Successful in 29s
Release / release (push) Successful in 1m14s
pre-commit / pre-commit (push) Successful in 3m27s
This commit was merged in pull request #184.
This commit is contained in:
1 parent
80d749ab92
commit
8b3d3110fe
3 files changed
+56
-2
No files matched your search
@@ -42,3 +42,4 @@ http.Handle("/", otelsetup.Handler(myHandler))
|
||||
|
||||
- `OTEL_RESOURCE_ATTRIBUTES` - Auto-set if not provided (service.name, service.version, service.environment)
|
||||
- Standard OTLP environment variables for endpoint configuration
|
||||
- The trace and metric exporters use our own HTTP client (idle connections closed after 30s, before the collector's 1m idle timeout), so `OTEL_EXPORTER_OTLP_*TIMEOUT` and the `OTEL_EXPORTER_OTLP_*CERTIFICATE` / `*CLIENT_*` TLS variables are ignored
|
||||
Reference in new issue
Block a user