Groundcover Observability Platform Reviews

My main use case for Groundcover Observability Platform is for application logs, insights, workload observability, and visibility.

Groundcover Observability Platform has helped my organization positively because Fairmoney is a new bank, a FinTech application with a large customer base, which is a B2C application. It has helped us in troubleshooting our backend transactional, high-volume transaction processing systems by enabling us to identify duplicate transactions or transactions that automatically reverse. We can deep dive into the application to see which issues are occurring and identify which particular component of the application is performing slowly or not performing well, so that we can improve and optimize that component.

Troubleshooting is very fast compared to manual investigation or using the other forms of logging that we used to have. Downtime and errors have decreased because we are able to see our performance and workload pods performing better. We can increase the number of CPU and memory resources as soon as we notice that usage is going above the threshold, which allows us to temporarily increase resources and then investigate why memory is increasing. This has helped us make our application more scalable and improve performance metrics, reducing the number of errors in the application. While I do not have the particular numbers right now, I would say it has reduced the number of errors by at least 70% in the application.

The best features Groundcover Observability Platform offers are the ability to view workload metrics of each pod, CPU resource usage, and memory resource usage. Another key feature is that it is very well integrated with Grafana for Grafana dashboard metrics, and it comes with Prometheus log queries. Groundcover Observability Platform is a very broad observability solution where you do not have to get each tool separately. Previously, we needed to get separate tools for all of these things, but Groundcover comes bundled with Grafana, Prometheus, and many other tools, so you can get everything in one go.

Within the same dashboard, you can switch between pods and view visibility of a pod, CPU memory, an entire VM, or a particular component of the application and its performance metrics. The bundled dashboard is the one feature that makes the biggest difference in my work because it comes with many features and serves as a one-stop shop for every visibility and performance metric to see how your application is running on the server. You can set it up on another screen and monitor your application continuously. It is very good for operational teams and also for software engineers who want to see how the application is working for third-level support or second-level support.

Groundcover Observability Platform is already very vast, and improving it requires proper training for even a software developer to be able to use it. A person in tech needs training to navigate the system. The UI is better, but it can be improved to include a more intuitive design that easily explains itself to users so that navigation is simpler. Many features are hidden, and you need someone who is experienced with the platform to direct you on how to view certain information or complete specific tasks and walk you through the process.

It would be better if Groundcover focused more on simplifying the user interface and improving human-computer interactions of the dashboard to make it so easy for a new developer or specialist to navigate and get what they need quickly. Querying data from Groundcover is not easy if you do not have specific information. You cannot perform a wildcard search in the text box. If you go to the log and enter an error message, it will not bring any results for you. You must first specify the workload or pods you are looking for, then enter the error. You need to add tags and put in your strings to be able to search for your particular logs or errors. If you just put a wildcard search in the text box, it will not work and will appear as if there are no logs that relate to that search, when in reality the logs exist. Making it easier for developers, users, and specialists using Groundcover to navigate and get what they need without the help of an experienced person walking them through is very important. This improvement is not about functionality but more about making navigation easier.

I have been using Groundcover Observability Platform for two years.

Groundcover Observability Platform is stable.

Groundcover Observability Platform's scalability is fine, and it is very scalable and reliable.

I previously used Grafana before switching to Groundcover Observability Platform because Groundcover Observability Platform is broader than Grafana and comes with Grafana as well.

I evaluated Datadog before choosing Groundcover Observability Platform, and we tried Datadog for a while before switching to Groundcover Observability Platform.

Groundcover Observability Platform is a good platform and very good to use. I would rate this review as highly positive.

Groundcover Observability Platform serves as my primary observability system, and day-to-day, I am viewing the logs, metrics, and the performance of my application that is deployed in Kubernetes. I use it to get incidents of hosts that are down and are not responding, so I receive alerts immediately. That is my most significant use case. I also have other use cases in using Grafana dashboards and other inspection tools for alternative views, but they are not on a daily basis.

Regarding how Groundcover Observability Platform fits into my workflow, I find the view of workloads in my application and the ability to view logs, metrics, performance, and traces on the same page for one application extremely useful. Even with all the AI agents, having a single visibility tool without any questions or waiting for queries is beneficial. It is great to have one tool that consolidates everything in one place, and it looks very nice and is easy to search logs and find patterns.

The best features Groundcover Observability Platform offers for me include awesome search filters, and the option to view one log while filtering from a specific log using specific labels is very useful. Additionally, a few months ago, they released synthetics to check if a host is down or up, which led me to remove my Uptime Kuma application because this new feature is excellent, and I no longer need to hold anything else on the side.

Groundcover Observability Platform has positively impacted my organization by allowing me to pay only for what I use since it is stored in the cloud, and I do not need to pay for buckets of 1 gigabyte, 5 gigabytes, or other options. The logs and searching are much easier than other platforms I used before, making it very easy and fast for everyone in the company to search for logs and workloads. I moved from a free plan to an enterprise plan very quickly because the features are excellent.

The search filters make my work easier because it is very easy for me to look into the log and identify a specific subquery visible in the logs or traces. I can find the specific parameter I am looking for and filter by that, rather than copy-pasting; I just drop it into the search box, maybe with a minus to filter it out. This allows me to filter out anything irrelevant and find something small in a lot of noisy logs. If I want to see a pattern of a specific log, I can filter only the specific log inside and view the graphs to see how often this log appeared. The synthetic feature has helped me by reducing the need for another service, which I do not need anymore because now they provide it.

I would appreciate the ability to eliminate incident.io and have all the alerting in one place. Currently, I am dropping the critical incidents from Groundcover Observability Platform to incident.io. If they can provide what incident.io has, that would be very useful for managing all my incidents in one place. Having observability and incident management in one tool would be super beneficial.

From my perspective, improving incident management into one platform would be great. For example, being able to send an SMS or make phone calls for a specific team, especially in the support team, would be valuable in managing critical issues, such as when one of my customers is down. This capability could help close the loop in one place. Additionally, I want to try their option to record specific user sessions in the browser to playback and see if there are any issues on my front end.

I would also appreciate options to record sessions for mobile users, as that is something no one has. An option to replay what people do on mobile would set them apart from all other observability tools.

I have been using Groundcover Observability Platform for approximately two years, having started the adoption a few months after I began my role.

My advice for others looking into using Groundcover Observability Platform is that once people try it, they will understand how easy and good it is, but it needs to get a chance. Most people working in enterprises or larger organizations are hesitant to move to new tools. They just need to give it a try, maybe on their dev cluster, using the free version to see how it works. Once they are comfortable, they need to adopt it. I believe it is an excellent tool that deserves widespread adoption. I rated this review a 10 out of 10.

My main use case for Groundcover Observability Platform is monitoring Kubernetes clusters and pods, as well as logs from our production product.

I use Groundcover Observability Platform with my Kubernetes clusters primarily when we encounter bugs in our microservices, and we monitor the logs in Groundcover for this purpose. We also use dashboards to check the performance of the pods.

Groundcover Observability Platform is deployed in my organization within our cluster, and all our microservices are connected to Groundcover so we can view the logs there. Currently, we are using the new Agent Mode, which has helped us create custom dashboards for our product.

The best features Groundcover Observability Platform offers include the Agent Mode, which is beneficial for creating customized dashboards, and the logs and monitoring capabilities.

The Agent Mode and custom dashboards feature stands out to me due to the ease of use and how effectively it functions.

Groundcover Observability Platform has impacted my organization positively as it is the primary way we use observability in our company, so it has a significant impact. The positive impact mainly includes tracking bugs, which is straightforward in Groundcover Observability Platform.

I cannot think of something specific regarding improvements for Groundcover Observability Platform as it is quite effective, especially compared to my previous experience with a Rapid7 platform, which was considerably worse.

I think it would be beneficial to see the body and content of API calls in the traces as a possible improvement.

I have been working in my current field for about five years.

Groundcover Observability Platform is stable.

The scalability of Groundcover Observability Platform is very good. We add microservices frequently, and we have not experienced any downtime.

Before choosing Groundcover Observability Platform, we previously used Rapid7. The decision to switch was an organizational decision, but I am not aware of the specific reason.

I am not certain whether we purchased Groundcover Observability Platform through the Azure Marketplace since I was not the person who purchased the application, as I am a developer.

I have seen a return on investment with regard to bug tracking and monitoring.

My experience with pricing, setup cost, and licensing is outside my field of expertise.

I did not evaluate other options before choosing Groundcover Observability Platform, as this decision was outside my field and I did not make that choice.

My advice to others considering Groundcover Observability Platform is that I would recommend a monitoring application for everyone. It is simply a matter of becoming accustomed to it, and Groundcover Observability Platform is quite easy to adapt to. I would recommend it. I gave this review a rating of eight.

Another notable example with Groundcover Observability Platform is its simple search and query syntax for logs. While this isn't unique to Groundcover specifically, it's really important as our previous vendor had a very difficult-to-use navigation syntax.

Regarding future versions of Groundcover Observability Platform, they deploy new versions every Monday through rolling updates. I think we need to work on our side to better fit Groundcover, as we have situations where it's difficult to connect between different places over an entire API call, but that's our responsibility, not theirs.

I would rate Groundcover Observability Platform's customer service as a ten out of ten based on my personal experience. It was perfect.

Positive