Monolog VS Grafana

To add onto this, what's more commonly done these days is to use a library like Monolog which can be configured with multiple log handlers. One of the handlers which are typically enabled is one which writes to error_log. You can add more which write directly to a logging service like Sentry or whatever, or even in dev write an HTTP header paired with a browser extension which puts your backend log messages in your browser console (see the handler + install the extension for chrome or firefox)

Monolog is a highly regarded PHP logging library with open source code. This project extends a straightforward and adaptable API, allowing developers to log messages from their PHP applications to diverse channels, including files, databases, and various third-party services. The modularity of this project’s source code provides an assortment of handlers and processors that seamlessly combine and configure to cater to specific logging requirements for any application.

If you need something more flexible you could always use Monolog which provides a bunch of adapters to log to any service want. You could for example use the syslog adapter to send your logs to syslog, and then configure rsyslog to print them directly into your terminal (or just `tail -f` a log file).

PHP -> Built in Logger, Monolog, Analog, KLogger, Log4PHP

So far, I've been discussing what PHP itself has to offer, which, quite frankly, is not very appealing. Luckily, though, there are great developers involved in pushing beyond those boundaries, making the appearance of great tools a reality. That is the case for Monolog.

Laravel (and many other frameworks) use the Monolog Package for logging by default. Using their formatter does everything you need!

Nowadays all popular frameworks comes with logging system built in. If not, you should use http://seldaek.github.io/monolog/.

Laravel logging is created on top of Monolog, which is a powerful logging library for PHP projects. In this guide, we will be looking at how to send our laravel logs to telegram channel with the help of the Telegram Bot API.

To help us visualize these scenarios, we'll build a Grafana Dashboard so we can follow along.

Visualization and Analysis: Choose a tool with intuitive and customizable dashboards, charts, and visualizations. A question to ask is, "Are the visualization features of this tool user-friendly and adaptable to our team's specific needs?" Tools like Grafana and Kibana provide powerful visualization capabilities.

Prometheus: Open-source monitoring system. Often used together with Grafana.

Grafana

Yes I'm aware that Grafana is open source but the method I used to find the API endpoints is far quicker than digging through hundreds of files in a codebase I'm not familiar with.

So, you will add one last container to allow us to visualize this data: Grafana, an open-source analytics and visualization platform that allows us to see traces and metrics simply. You can set Grafana to read data from both Tempo and Prometheus by setting them as datastores with the following grafana.datasource.yaml config file:

In example above, we use 2 additional parameters: code (HTTP response code) and page (page identifier), which provide detailed statistics. For example, you can build such graphs in Grafana:

Robin switched to the Grafana dashboard tab, and sure enough, the 5xx volume on web service was rising. It had not hit the critical alert thresholds yet, but customers had already started noticing.

I completely agree but do feel it needs qualifying. The problems beginners run into aren't usually the same as the problems experienced devs run into when adopting a language new to them, but where I see the two overlap I know something is a serious hazard in a language.

Java as a first language: won't like the boilerplate but won't have any point of comparison anyway, will get a few NPEs, might use threads and get data races but won't experience memory unsafety.

Go as a first language: much less boilerplate, but will still get nil panics, will be encouraged to use goroutines because every tutorial shows off how "easy" they are, will get data races with full blown memory unsafety immediately.

Rust as a first language: `None` // no examples found

I think Go as a beginner language would be better if people were discouraged from using goroutines instead of actively encouraged (the myth of "CSP solves everything"), otherwise I think it needs much better tooling to save people from walking off a cliff with their goroutines. And no, -race clearly isn't it, especially not for a beginner.

And in one respect I've found Go more of a hazard for experienced devs than beginners: the function signature of append() gives you the intuition of a functional programming append that never modifies the original slice. This has literally resulted in CVEs[1] even by experienced devs, especially combined with goroutines. Beginners won't have an intuition for this and will hopefully check the documentation instead of assuming.

[1] https://github.com/grafana/grafana/security/advisories/GHSA-...