2024 Customer Success Honoree Award Winners
Any community whether online or in person is a place to share and learn. As leader of Customer Advocacy, my role too encompasses sharing the voice of our customer in many formats in order for our peers to thrive from this knowledge. In case you missed it, we recently launched our ScienceLogic 2024 Customer Success Honorees - an awards program recognizing those who have made significant progress in a specific area, and have been an integral champion for SL1 success. I wanted to share with you these wonderful advocates, our finalists, in the hopes it inspires you to share your stories of success with our new Nexus community! Stay tuned for our upcoming 2024 Innovators Awards, an application-based awards program celebrating and recognizing customers and partners who are leading the charge in digital transformation, operational excellence, innovation, and business impact utilizing SL1 in innovative ways. Applications are opening early June! Read more in our CS HonoreeeBook. Congratulations to each of our 2024 Honorees! 👏💣 If you're interested in telling your SL1 story, please reach out to me, and join our Pathfinders customer advocate program.
Azure monitoring and integration with CMDB
When gathering information from cloud stuff, or actually doing whatever with cloud staff you most often need the object's ID, that long hexastring. That same ID is also most used identifier and required information when trying to sync those cloud "devices" into ServiceNow CMDB. The issue is that SL1 Azure PP does not gather that information too much, one device class that we have so far found it is those actual VMs in cloud. But one could say that those are the only "devices" where it is easily found. So my question is, how you have planned, or done, the CMDB integration of Azure cloud stuff. Or have you done any automation from SL1 to Azure, because also there one always(?) need that object ID. I could have written also an Idea for this, but at least for me, Nexus does not support my ideas.
