All Apps and Add-ons

ERROR: No Connection on Hub

GarrettDC
New Member

I'm currently testing out the Azure Monitor Add-on, but I have not been able to establish connectivity. I've followed the steps listed out in the README on github as well as this question (answers//693173//azure-monitor-add-on-for-splunk-why-are-inputs-con), but I have not found out what the issue is. Everything looks like it is configured correctly in Splunk, and I have opened up 5671 & 5672 to communicate. I'm not sure what I'm missing at this point.

================================

  1. 03-05-2019 20:06:27.470 +0000 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/TA-Azure_Monitor/bin/azure_diagnostic_logs.sh" Modular input azure_diagnostic_logs://insights-operational-logs No connection on hub: docs01. Is there a network route to the endpoint?
  2. 03-05-2019 20:06:27.470 +0000 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/TA-Azure_Monitor/bin/azure_diagnostic_logs.sh" Modular input azure_diagnostic_logs://insights-operational-logs No connection on hub: docs02. Is there a network route to the endpoint?
  3. 03-05-2019 20:06:27.470 +0000 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/TA-Azure_Monitor/bin/azure_diagnostic_logs.sh" Modular input azure_diagnostic_logs://insights-operational-logs No connection on hub: docs03. Is there a network route to the endpoint?
  4. 03-05-2019 20:06:27.470 +0000 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/TA-Azure_Monitor/bin/azure_diagnostic_logs.sh" Modular input azure_diagnostic_logs://insights-operational-logs No connection on hub: docs04. Is there a network route to the endpoint?
  5. 03-05-2019 20:06:27.470 +0000 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/TA-Azure_Monitor/bin/azure_diagnostic_logs.sh" Modular input azure_diagnostic_logs://insights-operational-logs No connection on hub: docs05. Is there a network route to the endpoint?

=================================

0 Karma

jesse_corray
Explorer

If you have gotten your secrets checked out you need to open your firewall to the eventhub's URL
Ours ended with servicebus.windows.net and that was blocked as the URL was different from the other asure URL we had opened already.

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...