Hi all. When i get the Graylog slow, i restarted it, but every time that i do it something happens, for example : “unassigned shards” , and at this time the alerts stop working too, but i solved already (i think) deleting old indices.
So my question: ¿Is oK to make : sudo reboot or sudo graylog-crt restart ?
welcome to the community - with that little information give about your setup it is impossible to give you an answer that will help you.
You could always restart a service or a server and in most times this might help. But you should find the reason why graylog is becoming slow.
But first, it looks like you are using the OVA in Production, that is not recommend as you are not able to make all necessary settings to tune your setup to the max.
you should install the environment yourself - following the step-by-step guides. What OS you prefer is up to your defaults.
The description that it is “slow” and you fixed it somehow is that generic like “my phone rings, and then stops making noise”.
Did you check your disk usage? how many messages you are ingesting? how many resources does the server have? All services up and running? How much processing did you do with your messages? What happens short before the server becoming slow? What did you have done to fix it? What was the result?
Hi Jan, your are right, my question is really ambiguous, sorry for that. I’m brand new on Graylog and i’m not a sysadmin, I read forums and some documentation to try to solve this thing. Sometimes work fine, but sometime not.
So, i think someone change the configuration of one device, modifying the logging level, so graylog exploted. I don’t know if this the definitive solution, but i’ll see it in these days.