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 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.
Backend Engineer at a insurance company with 201-500 employees
Real User
Top 20
May 28, 2025
I recently visited their booth and reported a bug, which they demonstrated and logged. They assured me it would be fixed by tomorrow.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.
Learn what your peers think about Groundcover Observability Platform. Get advice and tips from experienced pros sharing their opinions. Updated: September 2026.
Groundcover Observability Platform empowers teams by providing crucial insights into application performance, ensuring system reliability and aiding proactive decision-making. Groundcover Observability Platform offers comprehensive observability by harnessing cutting-edge technology. It transforms how teams manage systems by effectively monitoring, identifying issues, and simplifying troubleshooting processes. With a focus on scalability, it enables seamless integrations while ensuring...
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 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 recently visited their booth and reported a bug, which they demonstrated and logged. They assured me it would be fixed by tomorrow.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.