Getting Data In

Edge Processor Destination not showing up in Pipeline

Bobert
Observer

I've been writing new pipelines to my Edge Processors when I discovered that no destination values are showing up for me to select. We only have two, our default destination of our cloud instance and an additional cloud instance. When I go to create a new pipeline or modify an old one that already is configured to go to the default destination, it doesn't show up. The ones already created are still working and sending data in.

Any idea what could be causing this to happen? This occurred very recently. Prior to this I was able to create Pipelines and add a destination. Even a work-around would be appreciated.

Thanks!Screenshot 2025-04-17 at 11.37.40 AM.png
Screenshot 2025-04-17 at 11.38.08 AM.pngScreenshot 2025-04-17 at 11.38.02 AM.png

Labels (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...