Getting Data In

Why is my Azure Event Hub not sending data?

omuelle1
Communicator

Good morning,

I am having an issue on-boarding our main Eventhub into the Splunk Add-On for Cloud Services (latest version).

I have setup the inputs just like my other Eventhub but it is not sending data:

Below is the setup:

omuelle1_0-1680618816991.pngomuelle1_0-1680618816991.png

 

This is error I find in the logs:

 

 

logger=azure.eventhub._eventprocessor.event_processor pos=event_processor.py:_load_balancing:286 | EventProcessor instance '#####' of eventhub '#######' consumer group '$Default'. An error occurred while load-balancing and claiming ownership. The exception is AssertionError(). Retrying after 60s

 

 

I have a case open with MS and Splunk but no help so far.

 

Oliver

 

Labels (2)
0 Karma
1 Solution

omuelle1
Communicator

Figured out the issue with Splunk Support - the Splunk Add-On for Cloud Services supports a max of 64 partitions. We had 100, once we reduced to 64 the error message disappeared and the data started coming in.

View solution in original post

omuelle1
Communicator

Figured out the issue with Splunk Support - the Splunk Add-On for Cloud Services supports a max of 64 partitions. We had 100, once we reduced to 64 the error message disappeared and the data started coming in.

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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...