NeophyteNeophyteHi 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.
