NeophyteHi, we are creating a new datasource that needs data that is already being collected on another datasource. It is possible to use that data already collected instead of polling the device again?
Our need is to re organize collected data on another way to simplify the LM Services creation as it cannot filter instances by any instance property.
Thanks!
ProfessorYou have two options for this as far as I can see. You can query the API via the Datasource to retrieve the data and use it that way, or you can adjust the other datasource to cache its data and use that cache in the other datasource.
NeophyteCan you help me with an example or link to documentation for the API ? I didn´t figure how it can be done in a datasource.
ProfessorLook in the Modules section and look up any of the modules that start with LogicMonitor_Portal. Those all show querying the LogicMonitor API and returning something. In your case you would target fetchdata or another api endpoint.
Product Managersmaidanawe're working on a big effort to simplify LM Service Insight creation this year. Users we've talked to have made it pretty clear that filtering/selecting instances by property. Can you give me specific example of what you're trying to do?
NeophyteHi Mike,
We need to create a lot of services and each of them should get specific network interfaces as individual instances. As there's no filter instance by property we must add them one by one.
As it is possible to filter by name, we are thinking on creating a new datasource(s) that organize or named network interfaces on a way that it can be possible to filter on LM Services. A negative thing of these approach is that we do not want to poll the device again to get the same information we already have on an existant DS. That´s why we thought if there was a way to get information already collected to use in this new DS.
Hope the idea is more clear, also if you think there's a better way to do it, please let us know.
Regards,
Santiago
Product ManagerThe only real sustainable way to create a lot of services is via the API today.
If we allowed filtering by instance property, is there already a property that would allow you to filter by service?
Your use case sounds very similar to lots of others. What we're building will allow you to create a lot of services much more quickly and sustainably, and based on properties.
Unfortunately, between the lack of property filtering and the way that interface instances are named, your approach is probably the best you can do today. We're hoping to release the new capabilities (which are slated to include instance property filtering for service member selection) later this year.
