Grafana Loki vs. TIBCO LogLogic

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.

Incentivized

• 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.

Incentivized

• Learning curve is very steep
• Longer term log insight is a challenge
• Very easy on AWS, integration with other systems can be more of a challenge

Incentivized

Grafana Loki makes accessing and viewing service logs easy for engineers who may not be familiar with going into service. However, useability can be limited if engineers are unaware of what the queries should look like or where in the service to direct Loki to look for logging.

Incentivized

First and foremost if Grafana Loki is based on CNCF open source projects so organizations can get freedom to choice to configure it at your own other main thing is Grafana Loki is totally free of cost and we can deploy it on our infrastructure. On compared with other managed services like Datadog, New Relic it is very expensive and we also don't have much control on the tools we use.

Incentivized

• Company wide (realtime) insights in complex aws setup is great
• Dashboarding options are easily set up

Incentivized