3 ms·
I'm going through this article and it seems to me that is suggesting very low level techniques. Grep-able messages? Like ssh-ing into a machine and running grep
by kostarelo 6y ago
I'm going through this article and it seems to me that is suggesting very low level techniques. Grep-able messages? Like ssh-ing into a machine and running grep to see your logs?
I would go for a centralized logging system.
If you are working on a PaaS, probably has its own logging feature already built in.
If you are looking to self-host, give the ELK stack a try(many alternatives as well).
If you are looking a third-party service, look over at Loggly (many alternatives as well).
And the most important one is: export structured JSON. A centralized logging system will parse and index your logs.
In the ELK case, logs will be indexed in ElasticSearch. From there you will be able to not only filter and search but also create monitors and alerts on your logs.
- kyuudou 6y agoStrongly agree with this comment. ELK and now EFK using fluentd are fairly mature and the dashboards used to view the data e.g. Kibana, Grafana are full of useful features to get around the "endless series of greps" method of manually parsing through logs. Another benefit of offloading app, system and security logging to a central logging server is removing a potential single point of failure from simply running out of storage. Elasticsearch clusters are easy to build out to scale, also.