what to be done if nagios log server is almost full

[eloyd]

Yes, I see that. I may not be very clear though:

Let's say I have three hosts, X, Y, and Z. X is very important and I need to keep its logs for 90 days. Y is sort of important and I need to keep its logs for 60 days. Z is not important, and I only want to keep its logs for 30 days. The numbers are just examples, not real world.

Is there a way to prune the data in this fashion, or would it have to be that everything stays for 90 days, which is the time required for the longest retention?

[lgroschen]

Hey Eric,

I do like the idea of this option and the other devs have said they have been tossing this around. So I added it as a feature request: task_id=4898


@hlyeung:
Did my first response to your original post help? Let me know if you need more information

[hlyeung]

hi, thanks for your help.
i have moved the document to another location and then change DATA_DIR. However, after i moved, i cannot login to nagios log server. it said "The username specified does not existed". thanks.

[hlyeung]

after i waited a while, i can login.
thanks!

[hlyeung]

oh, seems after migrate database, it said


Waiting for Database Startup

It looks like your local elasticsearch service is starting.
Why am I getting this error?

Elasticsearch can take a little while to start up because of it's indexing. This may take a few seconds.

The page will refresh automatically after 5 seconds...

does this mean it is re-indexing all again?

thanks.

[scottwilkerson]

It is likely just re-shuffling the shards and verifying all their integrity