Coralogix Reviews

My main use case for Coralogix is to trace logs and debug the telemetry that we have across the microservices. Whenever our microservices get deployed on production or in stage, we emit these logs to Coralogix, and whenever something goes wrong, I go to Coralogix and debug it based on the applications and the services, looking after all the traces to find out what went wrong.

I sometimes also perform log searches based on certain keyword pattern matching with certain logs across different traces. We put that keyword in the complex search, and then it gives us all the logs that are included in it.

There were multiple scenarios where we have different microservices connected to each other, and if we want to know at what place and which microservice is failing and what the issue is, we search based on the request ID and get all the logs from all different microservices, then figure out where it is failing.

The best features Coralogix offers include the search feature, and the regex search is quite good. The period, network, and all those filters about why the same logs or trace has been connected across different services and microservices help tremendously.

The AI feature is also quite good for writing down the queries and those things. Coralogix improves the resolution speed because we have these logs integrated with our native AI agents, so it automatically fetches the data from Coralogix, and then we have it on Slack to resolve or identify the issue quite quickly.

Time is being saved in tracing logs or debugging any production issues or incidents.

Coralogix can be improved by cleaning up the UI, as it is too cluttered. If the search speed could also be improved, that would be helpful.

I chose seven for my rating because it is good for traces and logs, but I still feel that it can improve its UI and the search feature.

I have been using Coralogix for more than two years.

Coralogix is quite stable.

Coralogix is quite scalable. It is distributed, so we have never felt any issue with Coralogix's scalability.

Customer support is quite good.

Earlier, we were using Sumo Logic, and we migrated from Sumo Logic to Coralogix.

We purchased Coralogix through the AWS Marketplace, but I have less knowledge about the infrastructure and those things. I don't have information about the pricing, setup cost, and licensing, because the infrastructure and those things are handled by a different team.

Time is being saved in tracing logs or debugging any production issues or incidents, but I don't have any handy numbers because I am not the right person to look into the infrastructure or the metrics of Coralogix.

I don't have information about the pricing, setup cost, and licensing, because the infrastructure and those things are handled by a different team.

I didn't evaluate other options before choosing Coralogix. It was our team who did that.

Others looking into using Coralogix can trust it and can adopt it because it is good enough to use, with costs also being less than competitors. I gave this product a rating of seven.

Our company's use case for Coralogix is to protect our customers and support some attacks because here in Brazil, EFT is responsible for that.

The most valuable feature of Coralogix is the Social Security feature designed to protect machines that run on various systems such as Windows Server, including all versions from 2008 to 2022. The solution supports any Linux operating system distribution and can also be used to back up Mac systems.

The benefit of Coralogix for my organization is that Five9 is feature-rich, but we're not utilizing all available tools due to our size, with about 65 users split across three teams. This limits our use of analytics and other Five9 tools.

If I could improve Coralogix in any way, I would suggest additional customization options for our dashboards.

The customizable dashboards haven't really helped with my company's efficiency at all, and I think there's room for improvement.

I was part of the deployment at all, and since I'm new to the company, I haven't had the opportunity to talk to Coralogix customer support yet.

The overall stability and reliability of Coralogix are excellent, and I rarely encounter issues.

There are no downtimes, no crashes, or any performance issues that I've noticed since we started using it.

The product is scalable, and I believe it will grow with our needs.

I don't know what the experience overall with them is, but I've heard good things.

Positive

When I compared Coralogix to DataDog, the pros include better usability and features, while the cons involve some learning curves with both products.

The integration capabilities of Coralogix are perfect, and they work seamlessly with our existing tools.

I use the customizable dashboards from Coralogix, and they provide great insight into our data.

My overall experience with the pricing and licensing is good, and I appreciate the transparency.

The solution integrates with other tools, which is a significant advantage for our workflows.

On a scale of one to ten with one being worst and ten being best, I would rate Coralogix an eight for its performance and features.

My main use case for Coralogix was that we transferred from DataDog because DataDog was expensive at the time, and we wanted something more cost-effective. The VP of R&D thought Coralogix would be a great solution to replace DataDog. We used it for observability, logs of services, traceability of services that reach from certain endpoints, and everything related to metrics. We also used it in the queries and their Grafana managed dashboards, so we could view all of our Kubernetes workloads, whether it was RabbitMQ brokers panels or Kafka. We integrated it with so many things.

A specific example of how I used Coralogix in my daily work is that I opened Coralogix when developers had issues with their services, such as having 500 error codes or 400 error codes. We would observe the logs and see the logs that were transferred to Coralogix for the service, which were enriched with the data of the name of their service, the tags, and many other things that we did with the help of OpenTelemetry agents that transferred the data to Coralogix. We also sent log groups of specific RDSs that we managed via AWS, so it was better for metrics gathering and logs observability.

The best features Coralogix offers include its very nice tool and the usage of AI, which was very useful. The AI could describe the log that was received, providing a window that explains what the log actually says, what the issues are, the impact, and many things that help to summarize the log. The console is pretty fine; you can navigate and see many things that you want.

The AI feature impacted my work by helping me to reduce my time wasted on exploring what the error means and going to Google to search for it or maybe going inside the pods of the services to see what the issue actually is. The AI summarizes the data, enriches it, and provides a better view of what I actually need to handle.

Coralogix has positively impacted my organization by handling the responsibility for the developers to track their services and see what is actually going on there in terms of logs of their services, whether it is info, debug, error, or warnings. It gave a better view of things, and you can query against things that you want to see in terms of logs. The Grafana-managed dashboards allow you to actually see the metrics of your specific workloads. I believe it provides better observability and visibility. Coralogix is a nice tool that helps developers, DevOps, and SRE track services and see their health status.

After implementing Coralogix, we noticed improvements such as integrating it with our Squadcast, which is an alerting system that actually alerts when an incident arises. We used the alerting system of Coralogix and explained via PromQL, which is a query language that helped us write alerts based on queries. When we saw a pod's CPU utilization metrics exceed the predefined limit, we wanted to alert our SRE and DevOps team so they can open and see the alert URL and log URL. Via Coralogix, we could examine the logs and see the actual issue. It was very nice to integrate it with Squadcast and have SMS and calls when an alert is received.

This setup helped our team respond to incidents more quickly, and I think we improved our incident response time. The SMS and phone calls are received immediately; once the alert is triggered, it triggers Squadcast, which notifies me with SMS and then calls me.

Coralogix can be improved by having better documentation to help new people onboard into this platform and understand the systems, including how they can integrate their cloud provider to better understand how Coralogix and the cloud provider work in sync. If you really want to understand it, I think you need to find someone who has worked with it for at least a couple of years.

There are other improvements needed for Coralogix, such as their Helm charts and Terraform providers. I remember back at that time, the Terraform providers were without any support from the engineering team, and they were outdated and had many bugs.

I have been using Coralogix for at least two years.

I do not have any specific advice for others looking into using Coralogix. My overall review rating for Coralogix is eight out of ten.

We are building a reconciliation system where we handle the in and out of transactions daily. We maintain a record to verify if transactions came at the expected time and match them with the bank statement. We also deal with Kafka and pod failures, high Kafka lag, and have integrated Grafana with Coralogix to monitor Kafka lag on each topic.

One of the most valuable features of Coralogix is its time range feature, which allows us to specify a time range and get the exact logs needed. This feature is frequently used by our team. Coralogix also allows us to query in a way similar to querying a database, but this is not commonly known among our team members.

We need to reduce the number of logs generated by our system, which are substantial. We require some form of grouping or categorization of logs to identify them better. Additionally, we find that the user interface is not intuitive, especially when first onboarding, and improvements could be made here.

I have been using Coralogix for around one year.

There was an instance where we faced difficulty understanding why there was a lot of Kafka lag. The aggregation process in Coralogix makes it hard to see the exact metric. For example, high CPU usage on one pod can be averaged out by others, concealing potential issues. This averaging can sometimes be troublesome.

Coralogix scales well, and I will rate it nine out of ten. We have never faced any scalability issues.

The support team is doing well. They are helpful, especially when we created several custom dashboards.

Positive

The initial setup is straightforward and easy to integrate with Coralogix. Creating a custom dashboard depends on the team.

The pricing is expensive. We need to reduce logs to manage costs. Despite the expense, I believe it is worth the money to have Coralogix as a tool.

I would recommend considering New Relic, as it is a big competitor. New Relic provides specific metrics for each function and line of code, which is beneficial.

I would rate Coralogix eight out of ten overall. While I recommend Coralogix, New Relic has advantages in specific areas.

My main use case for Coralogix is logging and log monitoring. I use Coralogix for log analytics, as whatever logs are going into it are analyzed for any issues that arise.

In my experience, the best feature Coralogix offers is that the dashboard is pretty good.

Coralogix has impacted my organization, but I have noticed nothing different; it is similar to other solutions. Coralogix feels the same as other solutions; there is nothing special about faster incident resolution, better visibility, or improved collaboration.

I think Coralogix can be improved with flexible dashboards. Creating specific views, such as saving a dev environment as a separate view rather than adding filters every time, would be great.

I have been using Coralogix for more than six months.

Before Coralogix, I used a lot of tools including Elasticsearch and Kibana.

I switched from Elasticsearch to Coralogix because it is a logging solution. We are not a logging company, so it is a build versus buy decision. The hassle of hosting is very easy, and we do not want to solve that problem.

Coralogix's dashboard and search capabilities do not help me in any particular way. I feel Coralogix is expensive, but I am not sure if I have seen a return on investment since using it; I have not saved time, reduced costs, or needed fewer employees. I gave this review a rating of 9.

We are using Coralogix for log monitoring and creating dashboards. We have not explored the SIEM part and other capabilities yet.

We are not using Coralogix to the fullest extent. However, the log monitoring is good, and the dashboards that we create are beneficial. Other aspects like the alerting mechanism are also satisfactory.

Coralogix should have some AI capabilities to auto-detect anomalies and provide suggestions. The increasing volume of data and the resulting bandwidth charges are concerns. An in-built solution that remains native could resolve this issue.

We have been using it for almost two years now.

For now, we have not experienced any stability issues.

We have not experienced any scalability issues so far.

The technical support is good. I rate it eight out of ten, and I am satisfied with their response time and overall competence.

Positive

Currently, we are at a very minimal cost, which is around $400 per month since we have reduced our usage. Initially, we were at $900 per month.

We are considering having an in-house mechanism using Grafana Loki.

I would recommend Coralogix to others based on my experience. 

I rate Coralogix seven out of ten. Including AI features could be a game changer.

It's a login solution. We have a bunch of applications running in our cloud and all the logs with stalled applications and rates. We put those logs in Coralogix. Then we analyze those logs for various things, including alerts, data analysis, investigations, et cetera.

The overall capability of the platform and the kind of interface they have is excellent. The way I can query the data and pinpoint the issues, the kind of alerts they have, is so advantageous. The functionality is the most essential part for me.

The initial setup is straightforward.

We have asked for a couple of features from the company already. What typically happens is a lot of people - and developers are one of the biggest consumers of this product - go to this product to optimize their investigation process and specific configurations. That increases our data flow at times, so the cost changes. And a lot of changes happen due to that. We have asked the company to auto-revert the changes after a while so that the system works typically. We want it to work at what it is expected to work at and not really based on the updated configuration which one developer has decided to change.

I’ve been using the solution for over a year.

The solution is stable and the performance is good. It’s reliable. There are no bugs or glitches, and it doesn’t crash or freeze.

The scalability is pretty good.

We have about 60 to 70 people using this product. The majority of the backend and seniors use it regularly.

Technical support is above average. They have been pretty fast and pretty supportive on issues.

In this company, this I the first solution used. Before this, we were using an in-house solution. However, I've previously used some solutions such as Splunk and Datadog, if I remember correctly. Functionality-wise, this product is more mature compared to them. Plus, there are additional capabilities For example, I can keep my cost in check. Certain functionality in these terms of cost control is better. Overall product, it is slightly better than other products which are used.

The solution is acceptably easy to set up. That said, of course, you need enough technical understanding to set it up.

The deployment took a while for us, almost a month, I would say. The majority of the things were not ready on our side, however. The product was ready from almost day one, yet it took us quite a while to collect all the logs, redirect them to Coralogix, and create the logs in a format which were possible to ingest in Coralogix. A lot of work on our side was needed initially. Any new company which is onboarding has to go through the same cycle. It’s a sizeable investment in terms of time if they the company is not ready to onboard. If they have already been a customer or have done similar work, at least it should be pretty straightforward and only take a few days.

We did the initial setup ourselves. It's a pretty straightforward process.

We are paying roughly $5,000 a month.

It is not a pay-as-you-go model and suddenly you pump in a lot of data and your cost blows up. I can have a monthly billing which is in my control. I can tweak around costs to reduce my cost and all that.

I’m just an end-user.

Since we are using the cloud, we’re always using the latest solution version.

For any company getting onboarded to Coralogix or an equivalent solution for the first time, they need to do their in-house streamlining before they start working on this. It took us almost a month to streamline our systems and our processes to get onboarded. And during that time, we were just waiting to get onboarded. It's better to sort out internal things before you start looking at for a solution.

I’d rate the solution eight out of ten.

We use the tracing service from Coralogix mainly to store logs.

The best feature of this solution allows us to correlate logs, metrics and traces.

The documentation of the tool could be improved. The amount of data the system can process at one time is not that high. In a future release, it would be great to have an easier way to manipulate data that has already been ingested. It could also be more user-friendly.

I have been using this solution for a year and a half. 

I would rate this solution a nine out of ten for stability.

I would rate this solution a nine out of ten for customer support.

Positive

The initial setup is easy and only took a couple of hours. 

The cost of the solution is per volume of data ingested.

Coralogix is an Israeli startup so the headquarters of the company is in Israel. I believe it was easier for our company to find a company in Israel.

If a company has the budget and the log service is critical for them, I would say use Coralogix. It is a very good service for that.

I would rate Coralogix an eight out of ten. It is an excellent service for storing logs for a long time. The capacity is unlimited for unindexed logs. The cost model is also very efficient because you pay for the ingested data per month. This can be compared to a solution like New Relic where you have to pay it upfront and cannot limit the data ingestion. 

Coralogix provides an easy way to search for logs and to visualize them. This a great feature because developers are constantly looking for or browsing logs.