Stop 2 seconds, and think about this… The Cisco ACI API is just another API, we could be using Firepower API, AWS API, Microsoft Teams, WhatsApp, and so on. This is awesome because you are avoiding the need of a server to run the script, and we can say that the APIC is sending the message directly to you and without the need for any intermediary monitoring system. Now, this script is running on a server, and the Cisco ACI APIC, allows you to deploy the script inside a small Docker container directly in the APIC. (I’m using the Cisco ACI WebEx the code at GitHub. You can see the EPGs creation events, and at the end, a fault because one of the interfaces does not exist. Check my other posts about WebEx the next one, I will upload a full tenant config to the APIC. Later if you add some chatBots you could easily take some action on these messages, forward them to support, start a voice call on the same chat, or even have them searchable for a future reference. Here in the first example, you can see how a fault will be seen on your PC, Cell Phone, or tablet, which means … anywhere anytime! We could also be doing any other kind of action with that information. Then when ACI has a new message it will send it back to the script, and the script will send that message to a collaboration platform like Slack or WebEx Teams. With a Python script, we are going to subscribe to the ACI faults and events channel.
Webex teams rss bot how to#
In this post, I will show you how to send Cisco ACI faults and events to messages straight to Slack and WebEx Teams. Even if you don’t fully understand what is an API, it is really easy to leverage their power to have some useful information directly sent to a collaboration platform and receive it on your mobile or PC in real-time.Īll the tools in use are Free: Python, Slack, and WebEx Teams.
0 kommentar(er)
