Dev Ops Engineer at a tech services company with 11-50 employees
Real User
Top 10
Jun 16, 2026
Our main use case was to monitor an entire infrastructure as well as the application tech stack which we were having in a cloud environment. We had application telemetry as well, like monitoring traces, metrics, and logs. On the infrastructure side, we also monitored their metrics. Specifically with Chronosphere, we integrated OpenTelemetry as a collector on a centralized platform and used that to divert all the telemetry logs coming from our infrastructure as well as our application into Chronosphere where we have the dashboarding done. It is best that we have alerting integrated directly into Chronosphere. This means we don't need to set up a third party alerting mechanism. Chronosphere helped us in setting up a detailed dashboard with proper filtration of the data which is coming as well as custom filtering of data traces. We set up an alert for each and every metric and trace which we wanted to monitor, which is very critical at the production level. We were based on an e-commerce platform so each and every order failure or something similar would be very crucial to us to get notified. Chronosphere helped us in setting up those alerts very quickly on a single platform instead of hopping around multiple platforms. We integrated an entire monitoring setup. We were getting the data from OpenTelemetry collector into Chronosphere, wherein we had a centralized collector picking up the metrics and traces at different endpoints. We had dashboards created and alerting mechanisms also integrated into that, which was directly integrated into some notification mechanisms like Slack or other tools. Specifically, we had EKS monitoring as well. We were more into a data related environment and had a big data lake setup. Chronosphere helped us in having custom automatic instrumentations which helped us to instrument our application easily and have a proper detailed monitoring setup using Chronosphere which helped us in multiple scenarios. The support team was very good for us. They had a dedicated person assigned to us who would help us very thoroughly in terms of having all the issues sorted out. We had pretty good options of monitoring multiple applications using different methods. One method is using OpenTelemetry, and we also used multiple Lake view setups. This was very useful.
I work as a data engineer, and we have many streaming pipelines. We use Chronosphere to monitor various metrics, such as how much data our pipeline is processing in each batch, the volume of incoming data, our consumption rates, and the time to process each batch. Additionally, we set alerts in Chronosphere for situations like job failures or when the number of processed records falls below a certain threshold. We get alerts if the record count drops below our threshold. Sometimes, we face silent failures, where our system appears to be working fine but isn't consuming any data because another system has stopped sending data. Chronosphere helps us detect these cases. Another team member was involved in setting up a framework using Terraform on Chronosphere to monitor our job SLAs. We receive alerts on Slack or via email if any job fails to meet its SLA.
Find out what your peers are saying about Chronosphere, Datadog, Honeycomb.io and others in Application Performance Monitoring (APM) and Observability. Updated: August 2026.
Application Performance Monitoring and Observability are critical solutions enabling businesses to monitor and optimize application performance. They provide actionable insights to ensure robust, seamless user experiences and drive operational efficiency. As digital landscapes grow complex, Application Performance Monitoring and Observability tools become essential for understanding system behaviors and preempting disruptions. They offer a comprehensive view by correlating metrics, traces,...
Our main use case was to monitor an entire infrastructure as well as the application tech stack which we were having in a cloud environment. We had application telemetry as well, like monitoring traces, metrics, and logs. On the infrastructure side, we also monitored their metrics. Specifically with Chronosphere, we integrated OpenTelemetry as a collector on a centralized platform and used that to divert all the telemetry logs coming from our infrastructure as well as our application into Chronosphere where we have the dashboarding done. It is best that we have alerting integrated directly into Chronosphere. This means we don't need to set up a third party alerting mechanism. Chronosphere helped us in setting up a detailed dashboard with proper filtration of the data which is coming as well as custom filtering of data traces. We set up an alert for each and every metric and trace which we wanted to monitor, which is very critical at the production level. We were based on an e-commerce platform so each and every order failure or something similar would be very crucial to us to get notified. Chronosphere helped us in setting up those alerts very quickly on a single platform instead of hopping around multiple platforms. We integrated an entire monitoring setup. We were getting the data from OpenTelemetry collector into Chronosphere, wherein we had a centralized collector picking up the metrics and traces at different endpoints. We had dashboards created and alerting mechanisms also integrated into that, which was directly integrated into some notification mechanisms like Slack or other tools. Specifically, we had EKS monitoring as well. We were more into a data related environment and had a big data lake setup. Chronosphere helped us in having custom automatic instrumentations which helped us to instrument our application easily and have a proper detailed monitoring setup using Chronosphere which helped us in multiple scenarios. The support team was very good for us. They had a dedicated person assigned to us who would help us very thoroughly in terms of having all the issues sorted out. We had pretty good options of monitoring multiple applications using different methods. One method is using OpenTelemetry, and we also used multiple Lake view setups. This was very useful.
I work as a data engineer, and we have many streaming pipelines. We use Chronosphere to monitor various metrics, such as how much data our pipeline is processing in each batch, the volume of incoming data, our consumption rates, and the time to process each batch. Additionally, we set alerts in Chronosphere for situations like job failures or when the number of processed records falls below a certain threshold. We get alerts if the record count drops below our threshold. Sometimes, we face silent failures, where our system appears to be working fine but isn't consuming any data because another system has stopped sending data. Chronosphere helps us detect these cases. Another team member was involved in setting up a framework using Terraform on Chronosphere to monitor our job SLAs. We receive alerts on Slack or via email if any job fails to meet its SLA.