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.