Skip to content

Commit 6586f44

Browse files
[chore] Added docs for the edge processor (#1983)
* Added docs for the edge processor
1 parent fe0efa9 commit 6586f44

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

docs/advanced-configuration.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -893,6 +893,22 @@ agent:
893893
storage: null
894894
```
895895

896+
## Using Edge Processor
897+
898+
The [Edge Processor solution](https://help.splunk.com/splunk-cloud-platform/process-data-at-the-edge/use-edge-processors) is a data processing tool that can be used to enrich and filter your logs using SPL2.
899+
900+
Edge processor can be used to send data to various destinations, such as Splunk cloud or an Amazon S3 bucket. You can read more about [destinations here](https://help.splunk.com/en/splunk-cloud-platform/process-data-at-the-edge/use-edge-processors/10.0.2503/send-data-out-from-edge-processors/how-the-destination-for-edge-processor-works).
901+
902+
To configure a HEC Edge processor destination you can use a basic configuration like this:
903+
904+
```yaml
905+
splunkPlatform:
906+
endpoint: "https://x.x.x.x:8088/services/collector"
907+
token: "xxxxxx"
908+
```
909+
910+
Remember that the endpoint will be the instance where you configured the edge processor, and the token will be the token created in Splunk for more information you can check [here](https://docs.splunk.com/Documentation/SplunkCloud/latest/EdgeProcessor/HECSource).
911+
896912
### Support for persistent queue
897913

898914
* `GKE/Autopilot` and `EKS/Fargate` support

0 commit comments

Comments
 (0)