On the heels of an exciting GA in March and the April announcement of its regional expansion, we are excited to share the latest updates to Splunk Edge Processor that will make it even easier for customers to have more flexibility and control over just the data you want, nothing more nothing less.
Support Data Ingestion and Export Using HTTP Event Collector (HEC)
Users can now experience increased ingestion support from a wide range of applications and products that can send data to Splunk using HEC, and can take advantage of stream processing for third-party sources like VMWare Tanzu, Kubernetes, Kafka, among others. Plus there’s better support for other Splunk-supported apps like Splunk Nozzle for VMware Tanzu, Splunk Connect for Kafka, Splunk Connect for Kubernetes, etc. that send data over HEC. What’s more, in addition to extended ingest support, Edge Processor now also supports exporting to Splunk using HEC.
Want to see it in action? Check out this short video on setting up Edge Processor to receive data from Kubernetes pods over HEC, and creating a pipeline to filter noisy events.
Assign a Default Destination per Edge Processor
To complement use cases involving data sovereignty, Splunk Admins can now configure a default destination for each Edge Processor node, where previously, only one global destination was available. So, if desired, users can direct unhandled data for each Edge Processor to a destination of their choosing, giving them the control and flexibility to choose how to access data and where to store it. This feature can also support the improvement of your organization's data compliance posture.
Expanded Regional Availability in Four New Markets
Splunk Edge Processor expands its availability to Splunk Cloud stacks in EMEA with the addition of Frankfurt, Germany and London, England; and APAC which now includes Tokyo, Japan and Singapore. To get started using Splunk Edge Processor today, contact your Splunk Account Team to request activation, or send an email directly to EdgeProcessor@splunk.com with your company name, Splunk cloud stack name, and preferred Splunk Cloud region.