DEV Community

loading...

Discussion on: Live, Log, and Prosper

Collapse
biros profile image
Boris Jamot ✊ /

Great article Molly!

I also give a big priority to my logs because it's the only feedback I can have from my app.
We use a JSON logs specification to have a common logs format on all the apps in my project and to allow to build common kibana dashboards for all of them.
But with a high trafic, logs can become a bottleneck and may sometimes be replaced by some "code instrumentalization" (e.g. Prometheus exporter or whatever).

Collapse
molly profile image
Molly Struve (she/her) Author

Interesting! I have never heard of Prometheus, that looks neat. For production we have Fluentd setup for exporting logs to our Elasticsearch logging cluster and we also use Kibana for creating dashboards and saving searches. We have found Fluentd works really nice with Ruby which is why we choose it over something like logstash.

Collapse
david_j_eddy profile image
David J Eddy

Prometheus + Graphana = graphing heaven. :)

Collapse
biros profile image
Boris Jamot ✊ /

We also use Fluentd rather than logstash in our logs stack.
Prometheus is a great tool, but it's not based on the logs. Your app has to provide an API from which Prometheus will grab your metrics to build real-time aggregated dashboards.

Collapse
david_j_eddy profile image
David J Eddy

I heart common log formatting. Done right it is very helpfuil; done wrong, the problem you stated.