Log Sorting done good through Coralogix
Use Cases and Deployment Scope
The product solves the problem of search-ability of the logs which I was facing when presented with high number of concurrent containers on which it was impossible to find the issue individually. We have a large amount of logs coming from different services and containers. We need search, anomaly detection and tracing for these. Coralogix help us do that.
Pros
- Search-ability of logs from all containers: We have a service with multiple containers (which can go beyond 100). There was an issue which was happening intermittently and we wanted to figure this out using logs. It would have been impractical to check 100 containers manually, so when I checked Coralogix in the logs and searched the error logs, the issue was identified immediately and solved.
- Sending Alerts: We have a critical system which requires continuous monitoring and we need to be alerted whenever we face any error. Instead of identifying all probable points and adding an alert in code, it was super easy to add them in Coralogix.
- Automatic Classification of logs: Even without externally specifying the level of log, Coralogix can identify which log belongs to which level. This has helped us identify errors which were disguised as info level log in the code.
Cons
- Login issue with SSO: In some cases, the SSO login button is not visible on the Login page. This causes issue to access Coralogix.
- Duplicate Logs: In some cases, we get duplicate logs in Coralogix and it becomes difficult to identify if these are duplicate logs.
- Sometimes the tracing feature has glitches
Return on Investment
- Searchability of logs has improved
- Finding issues during live issues has improved
- Real time monitoring for anomalies in the logs has improved
Usability
Alternatives Considered
Observe.ai, New Relic and Datadog
