Coralogix

What do you like best about the product?

I like the flexibility of creating dashboards in Coralogix. The AI query tool is really helpful for finding necessary data for debugging.

What do you dislike about the product?

I think more widgets for the dashboard would be helpful. I'm not exactly sure what specific widgets are missing, but I remember there were times when I was trying to create dashboards and couldn't find the right widgets to show certain kinds of data.

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

Coralogix helps with observability and debugging issues, and I find the AI query tool useful for finding necessary data. Dashboards are flexible too.

What do you like best about the product?

I really like Coralogix for its speed and the intuitive interface. It's very easy to use, which makes it simple for me to click on different services and check their logs, filtering by particular fields to navigate effortlessly. I also find the diagram feature really helpful for plotting the number of errors or specific logs, like when I'm checking how many payments failed in a certain timeframe and then plotting a bar chart. The straightforward setup process and low friction to use the software were aspects that really appealed to me.

What do you dislike about the product?

I think building more complex dashboards could be improved.

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

Coralogix's fast dashboard and filters help me view logs and errors quickly. Its intuitive interface allows easy navigation across services, and I can plot diagrams for error analysis. This speeds up debugging and makes it easier to monitor specific metrics efficiently.

What do you like best about the product?

Tiering lets us route low-value logs to cheap storage, keeping costs predictable as volume grows. Fast queries and unified logs, metrics and traces help in incidents.

What do you dislike about the product?

Advanced query syntax has a learning curve, and the many parsing rule and tier settings can feel overwhelming when first configuring the platform.

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

Coralogix gives us one place for logs, metrics and traces, so we spend less time switching tools and find root causes faster during incidents.

What do you like best about the product?

Logs are easy to read and dashboards are intuitive to navigate. Integrating with multiple cloud and OS environments is straightforward with minimal friction. The Coralogix support team is consistently responsive and helpful whenever issues arise. All logs are available in real time with no delays, which makes troubleshooting much faster. One standout capability is the Coralogix integration with Claude AI via MCP — this significantly reduces time spent on debugging by bringing AI-assisted analysis directly into the workflow

What do you dislike about the product?

The main drawback with Coralogix is its reliance on OpenTelemetry for Windows OS and Server environments. While OpenTelemetry is a capable standard, the configuration overhead is significant - particularly for a small number of critical infrastructure servers such as Windows Active Directory, Domain Controllers, and Application Servers. A more lightweight, native Windows agent would make onboarding these components far less time-consuming.

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

Coralogix solves the challenge of centralising and making sense of logs across a complex, multi-cloud and multi-OS environment. Before, identifying issues required jumping between different tools and systems now everything is visible in one place, in real time, with no delays. The intuitive dashboards reduce the time engineers spend interpreting data, and the responsive support team means blockers are resolved quickly rather than escalating into outages. The integration with Claude AI via MCP has been particularly impactful, bringing AI-assisted debugging directly into our observability workflow and cutting the time spent diagnosing issues significantly.

What do you like best about the product?

I like Coralogix for its ability to create complicated queries using partial data. Plus, its amazing MCP server really enhances its usage with AI.

What do you dislike about the product?

The new UI feels too cluttered compared to the previous one, and I find myself switching back most of the time. There's sometimes slowness in the logs, but that's very rare. It would be great to consider separating usage for technical and non-technical users with a Simple and Advanced mode, where the advanced mode should be very technical, minimalist, and quick to use.

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

Coralogix helps me find relevant logs across many microservices, trace issues, and understand complex routing flows.

What do you like best about the product?

The Pagerduty integration for alerts, along with Coralogix’s MCP, helps me a lot by boosting my work speed and reducing the time it takes to resolve technical issues. The UI is mostly fine, and I’m very familiar with it now after using it for a while. In terms of ROI, the packages of Coralogix are quite affordable compared to Sentry and other log monitoring systems. When it comes to AI intelligence, I’m not very impressed. There are a lot of improvements required, and most of the time I don’t get the specific answers and solutions I need. The refinement can be improved by using more specific RAG systems, and the system could be more intuitive for the specific user in terms of AI enhancement. The support system is fast based on what I’ve used. I got replies instantly whenever I was stuck on something. Performance is fine for now, and I don’t have any complaints at the moment.

What do you dislike about the product?

AI features provided are not up to the mark as per the industry standard, in my opinion. Also, the logs UI and the APM part for specific APIs can be improved. Sometimes I have faced issues with incorrect error rates being shown.

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

Debugging any production issues and optimizing code in these cases, the cologix logs system helps me a lot. Apart from that, the pQuery-based (promituous) etc.-based system helps me a lot during any major production bugs by providing alerts and warnings, and it helps keep the system running smoothly.

What do you like best about the product?

I like how Coralogix makes centralized log analysis and troubleshooting straightforward. The search and filtering capabilities make it easy to quickly find relevant logs during production investigations, while the dashboards and alerting features are useful for monitoring application and infrastructure health. From an SRE perspective, it has helped reduce the time needed to investigate issues and correlate logs across different services.

What do you dislike about the product?

The platform has a lot of features, so it can take some time to become familiar with the different capabilities and workflows. Some advanced configurations and queries also require a learning curve for new users. A more streamlined experience and clearer guidance for advanced features would make the onboarding process easier.

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

Coralogix provides a centralized platform for collecting, searching, and analyzing logs across different services and environments. From an SRE perspective, it has made production troubleshooting easier by allowing us to quickly search and correlate logs when investigating issues. The migration also helped consolidate our observability workflow into a single platform, making it easier to identify errors, investigate incidents, and monitor application and infrastructure behaviour.

What do you like best about the product?

What I like best is how fast I can go from a failing pod or deploy to the actual logs. We push K8s app logs into Coralogix, and being able to filter by service/namespace and jump into the right stream during an incident saves a lot of time versus hopping across clusters and nodes. Querying and correlating logs in one place for stage/prod troubleshooting is the main upside for me day to day.

What do you dislike about the product?

Querying can feel heavy when log volume is high, and it takes some tuning to keep searches fast and costs under control. For day-to-day K8s ops I sometimes want a simpler path to the exact pod/container stream without building a fuller query first. Pricing also adds up as traffic grows, so we have to be careful what we ship and retain.

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

Main problem it solves for us is scattered logs across GKE/EKS services. Instead of SSHing into nodes or digging through each cluster separately, app logs land in one place and I can filter by service, namespace, or error during an incident. That cuts time to find root cause on failed deploys and pod crashes, and makes it easier for on-call to share the same view without everyone needing cluster access.

What do you like best about the product?

It’s easy to use and understand. It’s also straightforward to create alerts and dashboards, and to integrate it with other vendors.

What do you dislike about the product?

Sometimes it feels like there are just too many features, and the overall experience can be a bit overwhelming.

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

When it comes to APM, logging, and monitoring, Coralogix provides me with an all-in-one platform. Integrating it with their AI features is awesome.

What do you like best about the product?

I like that information from different sources is gathered together and easily accessible from one place. For example, when I'm looking at a log message I can open the related trace and spans directly from it, so I don't have to search for them separately. This makes investigating issues a lot faster, especially when a request goes through several services.

What do you dislike about the product?

At first the UI was a bit unintuitive. For example, in the logs filtering the top category is "Application", which in our case actually means the environment (production or staging), and "Subsystem" is the actual service running there. This was a bit weird and confusing in the beginning. It would be nice to be able to rename these categories, or at least have some hint in the UI about what they mean.

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

Before, we had more alerts that turned out to be false positives, which made it harder to notice the ones that really mattered. Now we can set thresholds and budgets for when an alert should be raised, so we only get alerted when something actually needs attention.