[Feature Request] GHES: Log Forwarding - Filter at source

[olivia-mativi]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Body

GHES has a log forwarding feature that allows for transmission of system and application logs via syslog-ng. This is a useful and desirable feature from a security monitoring standpoint. That being said, it has zero configurability beyond setting a destination ip/port, and the vast majority of events hold little to no security value. While it's possible to filter events out either in an observability pipeline or at a SIEM, it's common (if not standard) for dropped events to still count against licensing for those - and the all-or-nothing nature of the current log forwarding setting means that there's a genuine struggle between deciding to ingest it all for the few useful logs and accept the licensing hit, or to leave the OS/services unmonitored and collect GitHub logs via API.

It would be extremely helpful to be able to configure a filter to specify which log files to include/exclude. This could be as simple as a syslog-ng configuration file upload in the admin setup page that gets applied to the underlying service, but would represent a tremendous benefit in terms of increasing the value per log emitted by the appliance.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐