Skip to content

Commit ab7a08b

Browse files
atoulmeDougManton
authored andcommitted
[chore] remove mention of Splunk Cloud observability behavior for logs (open-telemetry#31650)
**Description:** Remove mention of Splunk Cloud observability behavior related to logs as this functionality is now end of life.
1 parent 3692c24 commit ab7a08b

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

exporter/splunkhecexporter/README.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,8 +39,7 @@ The following configuration options can also be configured:
3939
- `key_file` (no default) Path to the TLS key to use for TLS required connections.
4040
- `max_content_length_logs` (default: 2097152): Maximum log payload size in bytes. Log batches of bigger size will be
4141
broken down into several requests. Default value is 2097152 bytes (2 MiB). Maximum allowed value is 838860800
42-
(~ 800 MB). Keep in mind that Splunk Observability backend doesn't accept requests bigger than 2 MiB. This
43-
configuration value can be raised only if used with Splunk Core/Cloud. When set to 0, it will treat as infinite length and it will create only 1 request per batch.
42+
(~ 800 MB). When set to 0, it will treat as infinite length and it will create only 1 request per batch.
4443
- `max_content_length_metrics` (default: 2097152): Maximum metric payload size in bytes. Metric batches of bigger size
4544
will be broken down into several requests. Default value is 2097152 bytes (2 MiB). Maximum allowed value is 838860800
4645
(~ 800 MB). When set to 0, it will treat as infinite length and it will create only one request per batch.

0 commit comments

Comments
 (0)