LogicModules, Exchange, Kubernetes

I don't know much about monitoring Kubernetes specifically, but what I've done in general... If a NEW DataSource has an AppliesTo that does not apply to ANY device, it is safe to just import it. It will not apply to any devices so will not cause new alerts, which is my primary concern with DataSource updates. When I've done rounds of DataSource updates in the past, that was the first thing I did, to get them out of the way before digging into the rest.

I personally just import everything, even if I was not likely to ever use it. I think it was just easier that way and as an MSP I never know if I would need it eventually anyway. But as I think about it, I wonder if that is mostly because I've used the legacy Repository method for years and it shows everything. It was easier to try to get the list down to be as small as possible. But now that New DataSources (Exchange) is separated from existing DataSources (My Toolbox), perhaps that isn't as important anymore. But I'm still likely to continue to do it. 109 DataSources for Kubernetes is quite a lot, might be the largest I've seen. But again I'm not aware of any issues with having too many DataSources that are not being used or anything.

In your situation, where you want to start monitoring Kubernetes but have no devices yet, I personally would first start by adding and updating all the related official LogicModules, all 109 or so. It's a lot easier to update LogicModules when it's not being used, it becomes A LOT harder to update them later. Also it's easier to just let LM auto-add what DataSources it wants (after completing requirements/properties) rather than try to work out what DataSources you will end up needing.