The centralized logs where one can find bugs quicker and find the line of code that is a problem has made us more efficient. The turn around time for production support is quite high when using this kind of solution.

Application event messaging, or logging, until I show an organization the result of seeing the application in real time. Then, I can mentor the importance of a good log event message. To have proper context, logging is more than exception logging, it is positive and negative logging. Once you show what can be done with a proper logging message, the entire application can become more robust. The ability to make an extractor out of a non-standard stream of strings, which allows for you to index on a plethora of fields, and you gain some insights that you may have missed. 

Graylog brings life to the application execution.

Logs were previously stored in various database tables. Log consumers were required to write SQL for retrieval, then correlate/join disparate sources by hand. Since most logging fields were not indexed, the retrieval process was painfully slow.

Graylog captures our financial logs and preserves them, mainly for any audit that may come up. The compliance is very good.

We use this system as a central log collector with the possibility to search through the archive backward for specific string definitions.

It has sped up the investigation of incidents.

It is used as a log manager/SIEM. It provides visibility into the infrastructure and security related events.

This had increased productivity for the dev and support teams, because we are directly notifying them. Now, they have to come to dev for every issue.