-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splunk HEC Exporter Integration for Grafana Alloy #1226
Comments
This issue has not had any activity in the past 30 days, so the |
Hi, @PatMis16! Thank you for opening this issue. We could certainly add a new To gauge how much maintenance a component requires, I usually check a few things:
Based on this, I'd say it's completely doable to have an May I ask a few more questions please:
It is ok if you're not able to submit the initial PR or to assume ownership of the community component, but it'd mean that the work gets prioritised a little later. We will need to check further regarding prioritisation, because I'm not sure what the priority of this request vs other ones is. In the long term, I hope we can automate most of this maintenance work. WIP features such as OTel config schema could autogenerate code and documentation. This could significantly reduce the need for community component ownership. |
This would be nice. |
@ptodev |
@ptodev |
Created Pull Request #1645 |
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 functionality would be achieved by integrating the Splunk HEC exporter from the OpenTelemetry Collector Contrib Repository into Grafana Alloy.
Use case
Many organizations, including ours, leverage Splunk as their primary log management solution. Currently, Grafana Alloy lacks a native way to send collected logs directly to Splunk. This necessitates workarounds, such as deploying a separate log forwarder. These workarounds introduce additional complexity, potential points of failure, and hinder a streamlined observability experience.
The proposed integration with the Splunk HEC exporter would address these challenges by providing the following benefits:
Technical Considerations
Future Considerations
Conclusion
Integrating the Splunk HEC exporter into Grafana Alloy would significantly improve the platform's log forwarding capabilities. This feature would streamline data flow, enhance user experience, and improve overall observability within the Grafana ecosystem. We believe this integration aligns with Grafana's commitment to providing a comprehensive and user-friendly observability platform.
The text was updated successfully, but these errors were encountered: