Making "Services" usable/scalable
I've been bumping into tasks lately that would be great candidates for using an LM service to combine data into a more usable set pulling from other DSs without having to duplicate effort.
Adding a ServiceSource in the modules would solve for it... the ability to add the 'Source to a group instead of a device could allow it to show up as a device in that group with the service icon.
The primary issue I'm having with the current implementation is that it's a single thing that doesn't scale to "all client environments." As an MSP for a specific industry vertical, many of our clients use same/similar software stacks. Making a service means I repeat the same thing 50 more times to make it for all of those clients. I'd much rather build once, then be able to apply it to a client environment:
/Clients/*
and have it propogate itself, discovering the appropriate resources via some kind of active discovery type of mechanism.
Just a starting point for conversation at this point. This would allow for implementation of application monitoring for third party application multi-tiered enterprise stacks where we don't have access to the source code to add monitoring hooks.
Cole McDonald
OP1 year agoI would love to both learn more and join the beta for this.
Michael Rodrigues
·1 year agoHi Cole_McDonald , as it turns out, we're looking to solve this exact problem this year.
We actually have "Service Auto-Creation Rules" in beta. You can see more about how they work here: https://www.logicmonitor.com/support/service-templates
We've also got some small, but very powerful companion features to help make it easier to create, maintain, and instrument services at scale: https://www.logicmonitor.com/support/using-countif-functionality-and-service-property
Essentially, you set up rules that group resources into services by Property.
Then you create Aggregate-type LogicModules and apply them.
As you deploy (and tag) new resources and instances, everything is automatically managed via your rules.
The current wizard has an unfortunate 1:1 hardcoding between Services and Aggregate-type LogicModules, but with some minor tweaks you can make it much more powerful.
If you're interested in learning more and/or joining the beta, please let me know and I can see about getting time on the calendar and getting the agreement sent to you. We'd love to have you participate and give us feedback if you're able to.