Coralogix

What do you like best about the product?

I like how easy Coralogix is to use, especially when querying logs. Finding and narrowing down the information I need feels straightforward, which helps with day-to-day investigation.

What do you dislike about the product?

The newer UI is the main thing I like less about Coralogix. I preferred the previous interface, and I would like the current one to feel as comfortable and straightforward to use.

What problems is the product solving and how is that benefiting you?

Coralogix helps me query and investigate log data when I need to understand what is happening in a system. Being able to search and narrow down results makes troubleshooting more straightforward.

What do you like best about the product?

I really appreciate how smoothly Coralogix integrated into our existing setup without needing to change application code or add new agents, thanks to our use of OpenTelemetry. The speed of search is a huge plus, enabling us to quickly jump from log lines to related traces, which is invaluable during incidents. Having control over costs is another benefit, as we can allocate logs based on need, sending less critical ones to cheaper storage and keeping vital logs fully indexed. The support team has also been great; they provided clear, fast answers to our setup queries, which made onboarding easier.

What do you dislike about the product?

The biggest challenge for us was the learning curve. DataPrime, the query language, is powerful, but it took a while for the team to get comfortable with it. Engineers who only look at logs during an incident found it hard to write the right query under pressure, so we ended up keeping a shared list of saved queries to help them out. A simpler guided search for common cases would help a lot. Building dashboards also feels slower than it should. Getting a chart to look the way we want often takes several tries, and some of the settings are hard to find. We have used other tools where this was quicker. The interface can feel crowded. There are a lot of features, and it is not always obvious where something lives, especially for new users. It took some time before people on the team knew their way around. Understanding cost took some effort at the start. The pricing model makes sense once you learn it, but early on it was hard to predict how a change in log volume would affect the bill. Clearer estimates inside the product would help. None of these stopped us from using it day to day, but they did slow down how quickly new people on the team got comfortable with the tool.

What problems is the product solving and how is that benefiting you?

Coralogix centralizes our logs and traces, drastically reducing incident investigation time. We easily trace requests across services and optimize log costs with selective indexing. The platform's alert system catches issues early, and its seamless integration with OpenTelemetry simplifies setup and management for us.

What do you like best about the product?

We’re able to build dashboards very easily based on real-time data. The UI is neat and easy to use, which makes configuration much simpler. The integration of coralogix with email alerts and aws cloudwatch logs is lot simpler. The support team is always available to help with very fast response time.

What do you dislike about the product?

The older UI was more easier to understand than the new one.

What problems is the product solving and how is that benefiting you?

Basically, Coralogix helps me dump all my logs into one place, which makes troubleshooting a lot easier.

What do you like best about the product?

I like that Coralogix's dashboard is super easy to use, user-friendly, and very neat and clean. It allows even non-technical people to easily understand what's happening with our scan packages. It's super helpful for both technical and non-technical team members. The dashboard helps us quickly identify bugs and any coverage drops in scan packages. Another great thing is the ease of setup; it's really simple to get started by just opening the URL on the browser, much like opening any website. It's been our main tool for years, and I'm giving it a nine out of ten for recommending it to friends or colleagues.

What do you dislike about the product?

I find it a bit limiting that Coralogix only lets me see data from the last seven days. It would be more helpful if it could show the previous thirty days to better support developers. Also, there's a noticeable delay when loading the scan packages. If this could be sped up, it would definitely improve the experience.

What problems is the product solving and how is that benefiting you?

Coralogix helps us monitor thousands of scan packages, identifying coverage issues and bugs easily. The user-friendly dashboard is helpful for both technical and non-technical members, making it easier to understand issues in the scan packages.

What do you like best about the product?

The graphs below the log search (Explorer) are really helpful. I also like the data flow and background queries, and how easy it is to use Dataprime to get whatever I need. Filters and alerts (including integrations) are another strong point.

What do you dislike about the product?

Log search is slow at times, and the UX could be improved. For example, why does the custom timespan in log search show future dates? Also, the Quick range is limited to 7 days and should offer more options. Double-clicking a date in the custom timespan should reset the time to midnight, instead of forcing me to manually enter the time down to the second. Query Assistant also doesn’t help with “working queries,” and the queries it generates don’t work at times.

When a log is shared using a relative time window (like “last 15 mins”), it stops working after 15 minutes. That means every time I share logs, I have to switch to a custom timeframe, set the exact time range, and then share. This flow should be smoother.

Search results are limited to 2000, and if possible, this should be improved. I’ve also noticed that sometimes the case of words is automatically converted to lowercase. Finally, when exporting results to CSV, it asks for a filename, but the downloaded file still adds other metadata in front of the filename on its own.

What problems is the product solving and how is that benefiting you?

Production debugging and alerts.

With Coralogix alerting and the Slack integration, we receive an alert that includes the trace_id. Our Slack bot automatically picks it up and uses the Coralogix MCP or CLI tool with that trace_id to debug the request end to end on its own.

As a result, our production debugging is fully automated.