Loki is used for service process logging and sharing of logging data with other services and display dashboards. Engineers can use Loki as a logging repository to enhance troubleshooting and error tracing as issues arise. Loki, used with Grafana, provides a more user-friendly user interface that less adept engineers can use to query logs.
Pros
Compile logs.
Offer modular access.
Track and trace log queries.
Cons
Offer log suggestions.
Offer basic query syntax check.
Offer data range controls.
Likelihood to Recommend
Grafana Loki can compile data logs for easy exploration of a service and enable quick troubleshooting and error tracing for engineers who may not have deeper access. However, Loki is dependent on the service logging complexity, which, depending on the logger, may not be robust enough and limit the value offered.
As Grafana Loki is open-source logging and monitoring solution. We are using Kubernetes Cluster for our application deployment we are using Loki for Log aggregation of pods logs, jobs logs, and nodes logs, so we don't have to give access to Kubernetes cluster. Also, we are using Grafana for monitoring our Infrastructure, Cluster, Nodes Monitoring, Pods Monitoring, and our public cloud service provider.
Pros
Access to many open-source dashboards, access to add many data-sources to gather and visualize data from.
Grafana Loki does well gathering of logs from various data-sources, we can also filter the logs based on our needs.
One stop solution for all the logs and monitoring.
Cons
We can modify the logs directly from UI of Grafana Loki
Better and simplified options for logs filtering
Easy usability with SMTP configuration and other system level configuration
Likelihood to Recommend
In our application there are many points from where logs are coming so in order to go to each and every application and check logs its very overhead so we are using Grafana Loki for the logs gathering and monitoring.