Nagios Support Forum

Hi:
I just updated to the new version today and for some reason I can no longer filter on Event ID. Here is an image with no filtering with event ids shown:
And then here is the same dashboard where I am filtering for a particular event id:
Thanks!

What version was installed previously?

I've tested this on a system and it filters as expected. Try editing the query and make sure there isn't an extra space in there.

Try increasing the memory limit of php.ini as well - https://support.nagios.com/kb/article/n ... e-611.html

Does a query for 'EventId: 4642" return results ?

I upgraded from 2.0.8. The max_memory setting is currently 1024MB. I have tested my other fields and it just seems to be EventID having the issue. I am not even typing it in, I am clicking the magnifying glass beside the eventId field in the dashboard.

Is this a single machine or a cluster? Are there any unassigned shards under Admin > System > Cluster Status?

Also, * is not a valid regex query and can cause this kind of behavior. What is the query type set to?

Hi:

It is a lucene query as defaulted:
It is a single system and is showing green:
After the upgrade there were two unassigned shards but I deleted them and as shown it is now reporting green.

Thanks!

Clear the browser's cache and try a different one if you can and check the dev tools, /var/log/httpd/*, and /var/log/eleasticsearch/* logs to see if anything pops up when you try the query again:

Hi:

Nothing in either log that would be indicative of the issue. It only seems to be that one field for whatever reason.

Thanks!

I rebooted to ensure everything was reset. No change. I have tried the site with IE, Chrome and Firefox, no change. I am not sure what else to try. Thanks!

Please PM me a profile from the system. It can be gathered under Admin > System > System Status > Download System Profile or from the command line with:
This will create /tmp/system-profile.tar.gz.

Note that this file can be very large and may not be able to be uploaded through the PM. This is usually due to the logs in the Logstash and/or Elasticsearch directories found in it. If it is too large, please open the profile, extract these directories/files and send them separately.

Hi:

It has been a killer morning so I hadn't had a chance to respond. After letting it sit over the weekend, I came back today to find that it was working again.

Thank you for taking the time!