Hi @AKG11 * KPI which uses host as entity, * KPI is "service Up" which basically check service is up and in this case entity is "process name". * KPI for Garbage collection which also has diffe...
See more...
Hi @AKG11 * KPI which uses host as entity, * KPI is "service Up" which basically check service is up and in this case entity is "process name". * KPI for Garbage collection which also has different entity. You could have multiple different strategies for this. All does however sound like they host specific. "process name" will be related to a host, so does the Garbage collection right? I would make the KPI searches for "service Up" and "Garbage collection" exposes the host for every result. Use the filter to entities in service by host, and use the split by on a pseudo-entites for example process_name or garbage_collection_name. Then the result will be that all KPIs are filtered to the entity (host) of the service and split by different entites per KPI. Note this will be a bit wonky if you have multiple hosts by service, for example host1, host2, host3. In that case, to be able to distinguish a process from one host to another, you would need to create a combination of host and process, etc to split the data by. I.e. | eval my_process_entity = process_name."-".host Filter kpi by hosy Split kpi by my_process_entity If this widely used use-case also consider creating real entities and entity types for this use-cases to be able to create entity dashboards. Hope this gives some ideas! Kind Regards, Seb