Nagios Support Forum

The issue you want to look for in the changelog is GL:NLS#881. I can't promise that it'll happen or give you a timeline but it is now on our radar.

I don't have a really good answer for you other than we set it up that way several years ago and it only got looked at when we added support for EL8.. No one ever looked at it for any other distro. I'll file an issue to look at it because I do see the same recommendation to use chrony everywhere. I'...

Would you be willing and able to provide screenshots or a screen capture video of the situations you're experiencing. It would help out a lot if you could.

We don't have an alternative at the moment. However the fix for this is in the pipeline and will be coming soon.

Let me know if its anything that we can work on our end to alleviate going forward, or if its something more specific to your environment.

We have an internal issue for that, which should be fixed in the next couple of releases. Keep an eye on the changelog for issue NLS#864.

They don't need to be set to UTC unless they can't add in a time zone offset to the log that they're sending.

The first question I have is always going to be what version of Nagios Log Server are you on? The second question I have is how doe your disc space look on your system? If the disc gets full beyond a certain threshold, the database can automatically stop accepting writes, so even though your login m...

Which version of Log Server are you using? Your sources should be configured to send logs to NLS with their timestamps set to UTC as this is how they are stored and processed internally, this in particular applies to the @timestamp field, which is take from whatever timestamp your inputs and filters...

Understood. I have written an enhancement request for this. I can't promise any timeline for it, but if it is implemented it will be in the changelog as item number NLS:862