I'm not quite sure what you mean by "log analyses AFTER", but yes, Graylog is an excellent choice for collecting and analyzing logs through any stages of your application (dev, stage, QA, prod, ...). It is simple, reliable and can be integrated easy into most applications.
I am currently learning ELK stack and going to implement it on a virtual environment. After that I will definitely look into Graylog and try to implement it too. Thanks for the suggestion.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Is it a good choice for Log analysis after a dev environment is deployed or QA testing is in process?
I'm not quite sure what you mean by "log analyses AFTER", but yes, Graylog is an excellent choice for collecting and analyzing logs through any stages of your application (dev, stage, QA, prod, ...). It is simple, reliable and can be integrated easy into most applications.
I am currently learning ELK stack and going to implement it on a virtual environment. After that I will definitely look into Graylog and try to implement it too. Thanks for the suggestion.