About kbocchino

kbocchino · ‎02-08-2017

Ideally you should be sending data from the HTTP Event Collector for F5 Devices to a specific index example: f5-default. If you have all of the BIG-IPs going to F5 only indexes you would then update the f5_index macro to index name and that will prevent all hosts from being listed.

kbocchino · ‎11-23-2016

What version were you running, we just released 1.0.0rc1 with major changes to the majority of dashboards. There are cases where searches may report errors but still run cleanly this has to do with underlying subsearches not having specific data. In these cases those exceptions are dealt with using case statements but there is no way to remove the ! next to the panel.

kbocchino · ‎10-24-2016

You will need to map to some tenant, this can be done within the default tenant section if the tenant should be the same for all apps hosted by the F5 or within the Application mapping section. This will clear up the issue as all the apps likely have a tenant of null and it is conflicting with the predefined null value within the tenant dropdown.

Posts	3
Solutions	1
Karma Given	0
Karma Received	2
Member Since	‎02-04-2014

Online Status	Offline
Date Last Visited	‎06-05-2020 02:03 AM

Re: Non-Repoonding hosts lists non F5

Re: Getting these random errors on some panels

Re: F5 Networks - Analytics (New): Why am I receiv...