-
## Bug Report
**Describe the bug**
We are attempting to add a splunk output to our fluent-bit pods that run as part of an EKS Amazon Cloudwatch addon. We are running into an issue where we are abl…
-
### Community component name
### Request
This document proposes the addition of a feature that enables Grafana Alloy to forward logs directly to a Splunk instance using the Splunk HTTP Event Collect…
-
### Component(s)
receiver/splunkhec
### What happened?
## Description
We are still seeing an issue with the collector memory after upgrading to 0.109.0 with the fix. The behavior changed and we ar…
-
### Request
This document proposes the addition of a feature that enables Grafana Alloy to forward logs directly to a Splunk instance using the Splunk HTTP Event Collector (HEC) protocol. This functi…
-
### Component(s)
exporter/splunkhec
### Is your feature request related to a problem? Please describe.
I want to propagate the logger name through to Splunk via the OTEL collector. The otel log4j a…
-
`curl -k https://:443/services/collector/event -H "Authorization: Splunk " -d '{"event": "Hello, world!", "sourcetype": "test-sourcetype", "host": "test-host", "source": "test-source", "fields":{"app_…
-
## Bug Report
**Describe the bug**
`time` key is missing from the sent data when using the `splunk` output with `Splunk_Send_Raw On`
**To Reproduce**
1. Spin up a Splunk mockup server on p…
-
### Expected behavior
Events continuously published to Splunk HTTP event collector
### Actual behavior
After some good operating time, omHttp is not able to publish anymore events to Splunk HTTP …
ziouf updated
9 months ago
-
### A note for the community
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to …
-
## Describe the bug
Cortex Data > Splunk HEC event line breaks missing
## Expected behavior
JSON events from Cortex are extracted correctly, broken by line breaks when using the `pan:firewall…