diff --git a/docs/send-data/hosted-collectors/http-source/generate-new-url-with-auth-header.md b/docs/send-data/hosted-collectors/http-source/generate-new-url-with-auth-header.md new file mode 100644 index 0000000000..96ef66f8a2 --- /dev/null +++ b/docs/send-data/hosted-collectors/http-source/generate-new-url-with-auth-header.md @@ -0,0 +1,202 @@ +--- +id: generate-new-url-with-auth-header +title: Generate a New URL for an HTTP Source with an Auth Header +sidebar_label: Regenerate URL +--- + +import useBaseUrl from '@docusaurus/useBaseUrl'; + + + + + +

Beta

+ +Sumo Logic offers secure token-based authentication for the HTTPS Logs and Metrics Source. This capability allows you to authenticate using a unique token in the request header, maintaining the existing HTTPS endpoint behavior while adding token validation per source. Obtain the token to use in an auth header when you configure an HTTP source or regenerate the URL. + +## Generate a new URL for an HTTP source + +You can generate a new URL for an HTTP Source at any time. Generating a new URL completely invalidates the old URL. + +To generate a new URL: + +1. [**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic main menu select **Data Management**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**.  
[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. +1. On the **Manage Collection** page, click **Regenerate URL** next to the HTTP source.
Regenerate URL link +1. In the **HTTP Source Address** dialog box, select one of the following to regenerate the URL where the source data will be stored: + * **Presigned URL**. Select to copy a presigned URL with embedded authentication.
Generate New URL + * **Auth Header**. Select to copy the URL, as well as a separate authorization header that contains an authentication token. This option provides greater security than a presigned URL because placing the authentication token in the authorization header of a request prevents the token from being exposed in the URL.
Generate New URL and token +1. Click **Generate**. +1. When asked to confirm the generation, click **OK**. +1. In the resulting dialog box, the newly-generated URL is displayed, as well as the authorization header if you selected **Auth Header**. Copy the URL (and header if applicable) and keep in a safe place. +1. Use the copied URL (and header if appropriate) when you [upload data to your HTTP Logs and Metrics source](/docs/send-data/hosted-collectors/http-source/logs-metrics/#upload-data-to-the-httplogs-and-metrics-source). + +:::note +If you see a 401 (failed to authenticate) error message right after generating a new URL, wait a few minutes, then try the new URL again. +::: + +## Upload logs to an HTTP source + + + +### Upload log data with a POST request + +When you [upload log with a POST request](/docs/send-data/hosted-collectors/http-source/logs-metrics/upload-logs/#upload-log-data-with-a-post-request), keep in mind the following. + +To upload log data with a POST request, include the complete data payload as the request body. Any query parameters will be ignored. + +:::important +We recommend that the POST data payload have a size, before compression, of 100KB to 1MB. See [data payload considerations](/docs/send-data/hosted-collectors/http-source/logs-metrics/#data-payload-considerations) for details. +::: + +* Data payload: + * Data line 1 + * Data line 2 + * Data line 3 +* Method: POST +* URL:
Enter the URL obtained when you configure the HTTP Logs and Metrics Source or when you regenerate the URL. Enter either a presigned URL or a URL to be used with an auth header: + * Presigned URL: `https://[SumoEndpoint]/receiver/v1/http/[UniqueHTTPCollectorCode]`
where + * [SumoEndpoint] is your Sumo collection endpoint + * [UniqueHTTPCollectorCode] is the string that follows the last forward slash (`/`) in the upload URL for the HTTP source + * URL used with auth header: `https://[SumoEndpoint]/receiver/v1/http`
where [SumoEndpoint] is your Sumo collection endpoint +* Body + * Data line 1 + * Data line 2 + * Data line 3 + +### Supported HTTP Headers + +The following parameters can be specified via headers when sending data to an HTTP Source. The settings will apply to all messages in the request. For Source Name, Host, and Category, the header value will override any default value already specified for the source and/or collector. + +You can configure your Source to process HTTP Headers into metadata fields. See [HTTP Source fields](/docs/manage/fields) for details. + +:::note +Overridden metadata field values are not returned with [Search Autocomplete](/docs/search/get-started-with-search/search-basics/search-autocomplete). +::: + +| Setting | Header Name | Header Value | +|:--|:--|:--| +| Compressed data | `Content-Encoding` | Values can be `zstd`, `gzip`, or `deflate`.
Required if you are uploading compressed data. | +| Custom Source Name | `X-Sumo-Name` | Desired source name.
Useful if you want to override the source name configured for the source. | +| Custom Source Host | `X-Sumo-Host` | Desired host name.
Useful if you want to override the source host configured for the source. | +| Custom Source Category | `X-Sumo-Category` | Desired source category.
Useful if you want to override the source category configured for the source. | +| Fields as custom metadata | `X-Sumo-Fields` | [Fields](/docs/manage/fields) need to be in a comma separated list of key-value pairs. | +| Token authentication | `x-sumo-token` | Token to be used for authentication in an authorization header. Obtain the token when you select **Auth Header** when you [configure the HTTP Logs and Metrics Source](/docs/send-data/hosted-collectors/http-source/logs-metrics/#configure-an-httplogs-and-metrics-source), or when you [regenerate the URL](/docs/send-data/hosted-collectors/http-source/generate-new-url/). | + +### Command line examples + +:::note +Data is ingested according to the configured [processing rules](/docs/send-data/collection/processing-rules). Messages blocked by filters will not be ingested. +::: + +#### cURL + +When using cURL to POST data from a file:  + +* Make sure to use the -T parameter to specify the file path, not -d. The -d parameter causes new lines to be removed from the content, which will interfere with message boundary detection. +* Make sure that each line in the file follows the format specified by the Content-Type header for the HTTP request. +* Enter the URL (and auth header if applicable) obtained when you [configured the HTTP Logs and Metrics Source](/docs/send-data/hosted-collectors/http-source/logs-metrics/#configure-an-httplogs-and-metrics-source) or when you [regenerate the URL](/docs/send-data/hosted-collectors/http-source/generate-new-url/). If you use an auth header, enter it in this format:
`-H "x-sumo-token: [TokenString]"` + +**POST upload** + +Presigned URL: +```bash +curl -v -X POST -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` +URL with auth header: +```bash +curl -v -X POST -H "x-sumo-token: [TokenString]" -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http +``` + +**POST upload (gzip compressed data)**  + +Presigned URL: +```bash +curl -v -X POST -H 'Content-Encoding:gzip' -T [local_file_name.gz] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` + +URL with auth header: +```bash +curl -v -X POST -H 'Content-Encoding:gzip' -H "x-sumo-token: [TokenString]" -T [local_file_name.gz] https://collectors.sumologic.com/receiver/v1/http +``` + +**POST upload with custom Source Category** + +Presigned URL: +```bash +curl -v -X POST -H 'X-Sumo-Category:myNewCategory' -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` + +URL with auth header: +```bash +curl -v -X POST -H 'X-Sumo-Category:myNewCategory' -H "x-sumo-token: [TokenString]" -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http +``` + +**POST upload with custom Fields** + +Presigned URL: +```bash +curl -v -X POST -H 'X-Sumo-Fields:environment=dev,cluster=k8s' -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` +URL with auth header: +```bash +curl -v -X POST -H 'X-Sumo-Fields:environment=dev,cluster=k8s' -H "x-sumo-token: [TokenString]" -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http +``` + +#### PowerShell + +**POST upload** + +In the following examples when a URL is used with an auth header, `$headers` is defined as follows: + +```bash +$headers = @{ + Authorization="x-sumo-token: [TokenString]" + Content='application/json' +} +``` + +Presigned URL: +```bash +Invoke-WebRequest -Method POST -InFile [local_file_name] 'https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode]' +``` + +URL with auth header: +```bash +Invoke-WebRequest -Method POST -InFile [local_file_name] 'https://collectors.sumologic.com/receiver/v1/http' -Headers $headers +``` + +**POST upload (gzip compressed data)**  + +Presigned URL: +```bash +Invoke-WebRequest -Method POST -Headers @{'Content-Encoding' = 'gzip'} -InFile [local_file_name.gz] 'https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode]' +``` + +URL with auth header: +```bash +Invoke-WebRequest -Method POST -Headers @{'Content-Encoding' = 'gzip'} -InFile [local_file_name.gz] 'https://collectors.sumologic.com/receiver/v1/http' -Headers $headers +``` + +**POST upload with custom Source Category** + +Presigned URL: +```bash +Invoke-WebRequest -Method POST -Headers @{'X-Sumo-Category' = 'myCustomCategory'} -InFile [local_file_name] 'https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode]' +``` + +URL with auth header: +```bash +Invoke-WebRequest -Method POST -Headers @{'X-Sumo-Category' = 'myCustomCategory'} -InFile [local_file_name] 'https://collectors.sumologic.com/receiver/v1/http' -Headers $headers +``` + +**POST upload with custom Field** + +Presigned URL: +```bash +Invoke-WebRequest -Method POST -Headers @{'X-Sumo-Fields' = 'environment=dev'} -InFile [local_file_name] 'https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode]' +``` + +URL with auth header: +```bash +Invoke-WebRequest -Method POST -Headers @{'X-Sumo-Fields' = 'environment=dev'} -InFile [local_file_name] 'https://collectors.sumologic.com/receiver/v1/http' -Headers $headers +``` diff --git a/docs/send-data/hosted-collectors/http-source/generate-new-url.md b/docs/send-data/hosted-collectors/http-source/generate-new-url.md index f586de1102..eec02afb0f 100644 --- a/docs/send-data/hosted-collectors/http-source/generate-new-url.md +++ b/docs/send-data/hosted-collectors/http-source/generate-new-url.md @@ -11,11 +11,35 @@ You can generate a new URL for an HTTP Source at any time. Generating a new UR To generate a new URL: 1. [**New UI**](/docs/get-started/sumo-logic-ui). In the Sumo Logic main menu select **Data Management**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**.  
[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. -1. On the **Manage Collection** page, click **Regenerate URL** next to the HTTP source.
HTTPregenURL -1. In the **HTTP Source Address** dialog box, click **Generate**.
http_source_dialog_generate.png +1. On the **Manage Collection** page, click **Regenerate URL** next to the HTTP source.
Regenerate URL link +1. In the **HTTP Source Address** dialog box, click **Generate**.
http_source_dialog_generate.png +1. When asked to confirm the generation, click **OK**. +1. In the **HTTP Source Address** dialog box, the new URL is displayed. Copy and paste the URL, then click **OK**.
http_source_dialog_generate.png + +:::note +If you see a 401 (failed to authenticate) error message right after generating a new URL, wait a few minutes, then try the new URL again. +::: + + \ No newline at end of file diff --git a/docs/send-data/hosted-collectors/http-source/logs-metrics/index.md b/docs/send-data/hosted-collectors/http-source/logs-metrics/index.md index a11f20f7dc..3cf5fe4754 100644 --- a/docs/send-data/hosted-collectors/http-source/logs-metrics/index.md +++ b/docs/send-data/hosted-collectors/http-source/logs-metrics/index.md @@ -55,6 +55,14 @@ To configure an HTTP Logs and Metrics Source: 1. When you are finished configuring the Source, click **Save**. 1. When the URL associated with the source is displayed, copy the URL so you can use it to upload data.
HTTP Source Address dialog + + :::note * Metrics reported with a timestamp older than 24 hours ago or newer than 24 hours in the future from the time they are reported are dropped. Make sure that the Metrics sent to HTTP Endpoint have appropriate timestamps. * Sumo Logic enforces limits on the volume of metrics and associated metadata you ingest. For more information, see [Data Limits for Metrics](/docs/metrics/manage-metric-volume/data-limits-for-metrics). diff --git a/docs/send-data/hosted-collectors/http-source/logs-metrics/upload-logs.md b/docs/send-data/hosted-collectors/http-source/logs-metrics/upload-logs.md index b91e163308..8f0351de58 100644 --- a/docs/send-data/hosted-collectors/http-source/logs-metrics/upload-logs.md +++ b/docs/send-data/hosted-collectors/http-source/logs-metrics/upload-logs.md @@ -31,12 +31,20 @@ We recommend that the POST data payload have a size, before compression, of 100K * Method: POST * URL: `https://[SumoEndpoint]/receiver/v1/http/[UniqueHTTPCollectorCode]` where * [SumoEndpoint] is your Sumo collection endpoint - * [UniqueHTTPCollectorCode] is the string that follows the last forward slash (`/`) in the upload URL for the HTTP source + * [UniqueHTTPCollectorCode] is the string that follows the last forward slash (`/`) in the upload URL for the HTTP source * Body * Data line 1 * Data line 2 * Data line 3 + + ## Supported HTTP Headers The following parameters can be specified via headers when sending data to an HTTP Source. The settings will apply to all messages in the request. For Source Name, Host, and Category, the header value will override any default value already specified for the source and/or collector. @@ -55,7 +63,11 @@ Overridden metadata field values are not returned with [Search Autocomplete](/do | Custom Source Category | `X-Sumo-Category` | Desired source category.
Useful if you want to override the source category configured for the source. | | Fields as custom metadata | `X-Sumo-Fields` | [Fields](/docs/manage/fields) need to be in a comma separated list of key-value pairs. | -## Command Line Examples + + +## Command line examples :::note Data is ingested according to the configured [processing rules](/docs/send-data/collection/processing-rules). Messages blocked by filters will not be ingested. @@ -71,49 +83,166 @@ When using cURL to POST data from a file:  **POST upload** ```bash -curl -v -X POST -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +curl -v -X POST -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` + +**POST upload (gzip compressed data)**  + +```bash +curl -v -X POST -H 'Content-Encoding:gzip' -T [local_file_name.gz] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` + +**POST upload with custom Source Category** + +```bash +curl -v -X POST -H 'X-Sumo-Category:myNewCategory' -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` + +**POST upload with custom Fields** + +```bash +curl -v -X POST -H 'X-Sumo-Fields:environment=dev,cluster=k8s' -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` + +### PowerShell + +**POST upload** + +```bash +Invoke-WebRequest -Method POST -InFile [local_file_name] 'https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode]' +``` + +**POST upload (gzip compressed data)**  + +```bash +Invoke-WebRequest -Method POST -Headers @{'Content-Encoding' = 'gzip'} -InFile [local_file_name.gz] 'https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode]' +``` + +**POST upload with custom Source Category** + +```bash +Invoke-WebRequest -Method POST -Headers @{'X-Sumo-Category' = 'myCustomCategory'} -InFile [local_file_name] 'https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode]' +``` + +**POST upload with custom Field** + +```bash +Invoke-WebRequest -Method POST -Headers @{'X-Sumo-Fields' = 'environment=dev'} -InFile [local_file_name] 'https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode]' +``` + + \ No newline at end of file diff --git a/docs/send-data/hosted-collectors/http-source/logs-metrics/upload-metrics.md b/docs/send-data/hosted-collectors/http-source/logs-metrics/upload-metrics.md index 0114a30f73..5806d97753 100644 --- a/docs/send-data/hosted-collectors/http-source/logs-metrics/upload-metrics.md +++ b/docs/send-data/hosted-collectors/http-source/logs-metrics/upload-metrics.md @@ -94,6 +94,10 @@ Overridden metadata field values are not returned with [Search Autocomplete](/do | Custom Metric Dimensions | `X-Sumo-Dimensions` | Comma-separated key=value list of dimensions to apply to every metric.
For metrics only. Custom dimensions will allow you to query your metrics at a more granular level. | | Custom Metric Metadata | `X-Sumo-Metadata` | Comma-separated, key=value list of metadata to apply to every metric.
For metrics only. Custom metadata will allow you to query your metrics at a more granular level. | + + ## Data volume and metadata limits for metrics For information about the limits Sumo Logic enforces on the metrics you ingest to Sumo Logic, including data volume limits and metadata-related limits, see Data Limits for Metrics. @@ -104,31 +108,116 @@ When using cURL to POST data from a file:  * Make sure to use the `-T` parameter to specify the file path, not `-d`. The `-d` parameter causes new lines to be removed from the content, which will interfere with message boundary detection. * Make sure that each line in the file follows the format specified by the `Content-Type` header for the HTTP request. + * Enter the URL (and auth header if applicable) obtained when you [configured the HTTP Logs and Metrics Source](/docs/send-data/hosted-collectors/http-source/logs-metrics/#configure-an-httplogs-and-metrics-source) or when you [regenerate the URL](/docs/send-data/hosted-collectors/http-source/generate-new-url/). If you use an auth header, enter it in this format:
`-H "x-sumo-token: [TokenString]"` + +**POST upload ([Graphite](http://metrics20.org/implementations/)-formatted metrics)** + +Presigned URL: +```bash +curl -v -X POST -H 'Content-Type:application/vnd.sumologic.graphite' -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` + +URL with auth header: +```bash +curl -v -X POST -H 'Content-Type:application/vnd.sumologic.graphite' -H "x-sumo-token: [TokenString]" -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http +``` + +**POST upload ([Carbon 2.0](http://graphite.readthedocs.io/en/latest/feeding-carbon.html#the-plaintext-protocol)-formatted metrics)** + +Presigned URL: +```bash +curl -v -X POST -H 'Content-Type:application/vnd.sumologic.carbon2' -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` + +URL with auth header: +```bash +curl -v -X POST -H 'Content-Type:application/vnd.sumologic.carbon2' -H "x-sumo-token: [TokenString]" -T [local_file_name] https://collectors.sumologic.com/receiver/v1/http +``` + +**POST upload (gzip compressed [Graphite](http://metrics20.org/implementations/)-formatted metrics)**  + +Presigned URL: +```bash +curl -v -X POST -H 'Content-Encoding:gzip' -H 'Content-Type:application/vnd.sumologic.graphite' -T [local_file_name.gz] https://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` + +URL with auth header: +```bash +curl -v -X POST -H 'Content-Encoding:gzip' -H 'Content-Type:application/vnd.sumologic.graphite' -H "x-sumo-token: [TokenString]" -T [local_file_name.gz] https://collectors.sumologic.com/receiver/v1/http +``` + +**POST upload ([Prometheus](https://github.com/prometheus/docs/blob/master/content/docs/instrumenting/exposition_formats.md)-formatted metrics)** + +Presigned URL: +```bash +curl -v -X POST -H 'Content-Type:application/vnd.sumologic.prometheus' -T [local_file_name] http://collectors.sumologic.com/receiver/v1/http/[UniqueHTTPCollectorCode] +``` + +URL with auth header: +```bash +curl -v -X POST -H 'Content-Type:application/vnd.sumologic.prometheus' -H "x-sumo-token: [TokenString]" -T [local_file_name] http://collectors.sumologic.com/receiver/v1/http +``` + + + ## Prometheus Metrics Not Accepted by Sumo By design, Sumo does not ingest Prometheus comments. Sumo also rejects Prometheus metrics that do not conform to the Prometheus metric format. This page lists the conditions that will cause Sumo to reject Prometheus metrics diff --git a/docs/send-data/hosted-collectors/http-source/otlp.md b/docs/send-data/hosted-collectors/http-source/otlp.md index 651c85855f..4e2a4c315f 100644 --- a/docs/send-data/hosted-collectors/http-source/otlp.md +++ b/docs/send-data/hosted-collectors/http-source/otlp.md @@ -37,6 +37,14 @@ To configure an OTLP/HTTP Source: 1. [Create any Processing Rules](/docs/send-data/collection/processing-rules/create-processing-rule) you'd like for the OTLP/HTTP Source. 
OTLP processing rules 1. When you are finished configuring the Source, click **Save**. + + :::note * Metrics reported with a timestamp older than 24 hours ago or newer than 24 hours in the future from the time they are reported are dropped. Make sure that the Metrics sent to OTLP Endpoint have appropriate timestamps. * Sumo Logic enforces limits on the volume of metrics and associated metadata you ingest. For more information, see [Data Limits for Metrics](/docs/metrics/manage-metric-volume/data-limits-for-metrics). @@ -53,6 +61,7 @@ If you need to access the Source's URL again, click **Show URL**. ### Data differentiation When you set up an OTLP/HTTP Source, a unique URL is assigned to the Source. The exporter automatically appends the specific signal type when sending the data, as described by [OpenTelemetry Protocol Exporter specification](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.10.0/specification/protocol/exporter.md). + The following table shows the URL format based on data types. | Data Type | URL Format | @@ -64,7 +73,12 @@ The following table shows the URL format based on data types. ### OTLP/HTTP Exporter -To use the URL, include the url in otlphttp exporter of OpenTelemetry Collector and refer it in the pipelines, as needed. The exporter will automatically attach the signal type suffix: +To use the URL, include the URL in otlphttp exporter of OpenTelemetry Collector and refer it in the pipelines, as needed. The exporter will automatically attach the signal type suffix: + + ``` exporters: @@ -86,9 +100,20 @@ service: exporters: [otlphttp] ``` + + ### Alternative -It is also possible to optionally configure per-signal URL, e.g. +It is also possible to optionally configure per-signal URL, for example: + + ``` exporters: diff --git a/static/img/send-data/generate-new-url-and-token.png b/static/img/send-data/generate-new-url-and-token.png new file mode 100644 index 0000000000..7befb5aef1 Binary files /dev/null and b/static/img/send-data/generate-new-url-and-token.png differ diff --git a/static/img/send-data/generate-new-url-new.png b/static/img/send-data/generate-new-url-new.png new file mode 100644 index 0000000000..1cb8f49c81 Binary files /dev/null and b/static/img/send-data/generate-new-url-new.png differ diff --git a/static/img/send-data/http-source-address-and-auth-header.png b/static/img/send-data/http-source-address-and-auth-header.png new file mode 100644 index 0000000000..2808305ece Binary files /dev/null and b/static/img/send-data/http-source-address-and-auth-header.png differ diff --git a/static/img/send-data/http-source-address-new.png b/static/img/send-data/http-source-address-new.png new file mode 100644 index 0000000000..f203e457d7 Binary files /dev/null and b/static/img/send-data/http-source-address-new.png differ diff --git a/static/img/send-data/http-source-address-otlp-auth.png b/static/img/send-data/http-source-address-otlp-auth.png new file mode 100644 index 0000000000..83837456e9 Binary files /dev/null and b/static/img/send-data/http-source-address-otlp-auth.png differ diff --git a/static/img/send-data/http-source-address-otlp.png b/static/img/send-data/http-source-address-otlp.png new file mode 100644 index 0000000000..0c050cc26c Binary files /dev/null and b/static/img/send-data/http-source-address-otlp.png differ