Coralogix works well for our needs, but there are a few areas where improvements can be made. One area is querying performance for large-scale data sets. When we are dealing with very high log volumes, some complex queries take time to return results. Improving query speed and optimization would enhance the troubleshooting experience. Another point is the learning curve for advanced features. While basic usage is straightforward, advanced querying and dashboard configurations can take time for new users we are onboarding. We have faced this situation in our organization's domain frequently. More simplified UI options or guided templates would help new team members onboard faster. Additionally, dashboard customization flexibility needs improvement. Although dashboards are useful, having more flexibility in customization would make them even more powerful. An important point is cost optimization. Since log volume is high in our environment, better visibility and control over cost optimization would be beneficial. These are minor improvements overall. Coralogix already provides strong capabilities for centralized logging and monitoring, but enhancing these areas would make it even more efficient for large-scale environments in our telecom servers. Improvements could include query performance, alert noise reduction, and ease of use for advanced features, especially for large-scale environments like ours.
DevOps & FinOps Engineer at a tech services company with 501-1,000 employees
MSP
Top 20
Apr 29, 2026
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.
The only improvement I remember is that the cost aspect is a bit more tedious. My company often did not store older logs due to the high cost. There were multiple tiers for querying high-priority logs and archiving low-priority ones. Sometimes, while filtering based on tags, it broke, but it was usually fixed. It would also be beneficial if I could see Kafka-related logs in the system, as we were using a separate system for Kafka. I remember the OpenTelemetry configuration was not working properly in Coralogix. I am not sure if it is working now or not.
Coralogix has many features, but we usually use only these two, and the syntax has not been so straightforward. It was a bit difficult to write specific queries, so I have templates of specific queries where I just change the ID or the service. It is nice to see the whole picture, but it requires getting used to the program. Coralogix can be improved by simplifying it. Perhaps, with AI now, it could allow users to write in plain text and then create the query automatically. The main pain issue for me with Coralogix was that the syntax was a little tricky. Although Coralogix has so many features, I mainly used only a few due to difficulties in knowing how to write them. It was also chained, making it a little tricky. Therefore, I created templates for easier usage. The potential of Coralogix is huge, but we used it this way since no one knew how to use it correctly. We once had a session explaining all the features, but we took very little from it as it was difficult for us. With many microservices, it was sometimes tricky to understand where the data goes. I often activated multiple services to track the flow and would sometimes need extra time to grasp it. I believe now, with AI, it can be improved, allowing for easier queries created from plain text.
I think Coralogix can be improved by setting up some AI type of tool inside it which can help new users. Whenever they face any kind of issue or troubleshooting problem, I know that they already share a user guide whenever we try to set up and install Coralogix and use it for the first time. However, I would prefer an AI feature as per current trends. AI is coming into most tools, so I would prefer the same for Coralogix.
Software Engineer at a computer software company with 201-500 employees
Real User
Top 20
Dec 4, 2025
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 feel there should be room for improvement with Coralogix. Since we are in the present-day generation, I believe there can be more AI integration. Many AI tools are out in the market, and the focus should be on integrating AI with Coralogix as well as expanded capabilities for all notification centers or notification routing. I would appreciate more integrations with different vendors for notification and support. In terms of documentation, I think there can be more user-friendly documentation that stresses more on day-to-day issues.
Change might not be the correct word, but with every service, there is always room to improve. They are improving their services daily and deploy new features. When we had missing features that we needed, they developed and published them quickly. The features we were missing in the past were related to the way we see our metrics and aggregate our data. It was not a problem or an issue, but rather features we needed to view our data in specific ways. Once they realized these features were missing, they developed them rapidly. I would appreciate seeing more AI integration aspects.
Platform Engineer at a tech vendor with 51-200 employees
Real User
Top 20
May 28, 2025
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.
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.
Nowadays, tools are often divided into modules. It would be helpful if Coralogix could integrate the main modules that any organization requires into a single subscription. It would streamline the process for organizations like ours. Merging some of the modules into a single subscription would be beneficial. Nowadays, modules are often separated, so if an organization needs additional modules after subscribing to one, they may have to purchase another subscription. Combining the availability module with tracing metrics or other relevant modules would be beneficial.
Senior data engeneer at a manufacturing company with 11-50 employees
Real User
Jul 18, 2022
I couldn't find anything lacking. It's pretty much perfectly put together. From my side, I don't have any notes as of now for any improvements. Maybe they could make it more user-friendly. Errors should be shown in terms of text.
VP of Engineering at a financial services firm with 51-200 employees
Real User
Jul 18, 2022
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.
Coralogix provides a robust platform for real-time logging and analysis, offering seamless integration with cloud services and DevOps tools to enhance visibility and error detection.Coralogix is recognized for facilitating efficient log management through intuitive drill-down capabilities and AI-powered anomaly detection. Its platform supports smooth integration with multiple cloud providers and DevOps tools, focusing on ease of use and effective data migration. Users benefit from rich...
Coralogix works well for our needs, but there are a few areas where improvements can be made. One area is querying performance for large-scale data sets. When we are dealing with very high log volumes, some complex queries take time to return results. Improving query speed and optimization would enhance the troubleshooting experience. Another point is the learning curve for advanced features. While basic usage is straightforward, advanced querying and dashboard configurations can take time for new users we are onboarding. We have faced this situation in our organization's domain frequently. More simplified UI options or guided templates would help new team members onboard faster. Additionally, dashboard customization flexibility needs improvement. Although dashboards are useful, having more flexibility in customization would make them even more powerful. An important point is cost optimization. Since log volume is high in our environment, better visibility and control over cost optimization would be beneficial. These are minor improvements overall. Coralogix already provides strong capabilities for centralized logging and monitoring, but enhancing these areas would make it even more efficient for large-scale environments in our telecom servers. Improvements could include query performance, alert noise reduction, and ease of use for advanced features, especially for large-scale environments like ours.
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.
The only improvement I remember is that the cost aspect is a bit more tedious. My company often did not store older logs due to the high cost. There were multiple tiers for querying high-priority logs and archiving low-priority ones. Sometimes, while filtering based on tags, it broke, but it was usually fixed. It would also be beneficial if I could see Kafka-related logs in the system, as we were using a separate system for Kafka. I remember the OpenTelemetry configuration was not working properly in Coralogix. I am not sure if it is working now or not.
Coralogix has many features, but we usually use only these two, and the syntax has not been so straightforward. It was a bit difficult to write specific queries, so I have templates of specific queries where I just change the ID or the service. It is nice to see the whole picture, but it requires getting used to the program. Coralogix can be improved by simplifying it. Perhaps, with AI now, it could allow users to write in plain text and then create the query automatically. The main pain issue for me with Coralogix was that the syntax was a little tricky. Although Coralogix has so many features, I mainly used only a few due to difficulties in knowing how to write them. It was also chained, making it a little tricky. Therefore, I created templates for easier usage. The potential of Coralogix is huge, but we used it this way since no one knew how to use it correctly. We once had a session explaining all the features, but we took very little from it as it was difficult for us. With many microservices, it was sometimes tricky to understand where the data goes. I often activated multiple services to track the flow and would sometimes need extra time to grasp it. I believe now, with AI, it can be improved, allowing for easier queries created from plain text.
I think Coralogix can be improved by setting up some AI type of tool inside it which can help new users. Whenever they face any kind of issue or troubleshooting problem, I know that they already share a user guide whenever we try to set up and install Coralogix and use it for the first time. However, I would prefer an AI feature as per current trends. AI is coming into most tools, so I would prefer the same for Coralogix.
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 feel there should be room for improvement with Coralogix. Since we are in the present-day generation, I believe there can be more AI integration. Many AI tools are out in the market, and the focus should be on integrating AI with Coralogix as well as expanded capabilities for all notification centers or notification routing. I would appreciate more integrations with different vendors for notification and support. In terms of documentation, I think there can be more user-friendly documentation that stresses more on day-to-day issues.
Change might not be the correct word, but with every service, there is always room to improve. They are improving their services daily and deploy new features. When we had missing features that we needed, they developed and published them quickly. The features we were missing in the past were related to the way we see our metrics and aggregate our data. It was not a problem or an issue, but rather features we needed to view our data in specific ways. Once they realized these features were missing, they developed them rapidly. I would appreciate seeing more AI integration aspects.
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.
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.
Nowadays, tools are often divided into modules. It would be helpful if Coralogix could integrate the main modules that any organization requires into a single subscription. It would streamline the process for organizations like ours. Merging some of the modules into a single subscription would be beneficial. Nowadays, modules are often separated, so if an organization needs additional modules after subscribing to one, they may have to purchase another subscription. Combining the availability module with tracing metrics or other relevant modules would be beneficial.
The user interface could be more intuitive and explanatory. Additionally, more advanced functionalities can be included in the next release.
I couldn't find anything lacking. It's pretty much perfectly put together. From my side, I don't have any notes as of now for any improvements. Maybe they could make it more user-friendly. Errors should be shown in terms of text.
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.
From my experience, Coralogix has horrible Terraform providers. For sure, it should be improved with the Terraform provider.