November 15 2018

Greater Database Monitoring Simplicity and Power for Engineering Teams

CHARLOTTESVILLE, VA  November 15, 2018 − VividCortex, the leading provider of database performance monitoring, announced today that its cloud-based platform now provides engineering teams with increased visibility and control over the way they monitor database behavior and workload. Three new features – Explorer, Notebooks and Charts Dashboards – allow developers and technical operations engineers to use VividCortex to meet their respective needs as well as supporting workflows within the application.

Beta testers for the latest VividCortex enhancements offered strong positive feedback. For example, Silvia Botros, Principal DBA at SendGrid, said,”We've started using the new VividCortex Explorer during our Black Friday preparedness tests and it has already given us great insight into improvements we could make in our cache layer. VividCortex has become indispensable to the team during critical times and has empowered all of our delivery engineers to own the performance of their services.” (See additional case study.)

"Customers want performance at scale in a simple, straightforward way.  Diagnosing problems in the data tier is key to ensuring application performance for developers and tech ops alike. Our enhancements speak directly to customer needs to understand where and why database problems are occurring and how teams can better communicate and collaborate to address them," said Amena Ali, CEO of VividCortex.

While VividCortex makes improvements to the SaaS platform many times daily, these three new features represent an especially important leap forward:

  • Explorer lets users rank and chart specific sections of the data set and compare it to other metrics with the same time and host filter selections. Users can diagnose issues faster by looking at the exact information they need and readily see the relationships between different kinds of performance data, including query and system metrics (e.g. CPU usage), in a single view.

  • Notebooks allow users to add rich context and commentary to charts including text, code snippets, links and images, all in Markdown syntax. Fully integrated into VividCortex – with its robust filtering of hosts, time and selection of any metric or chart – Notebooks make it easy to reuse content and quickly generate reports on new events including outage post-mortems, diagnosis narratives and runbooks.

  • Charts Dashboards can now be built and edited easily in VividCortex using simple, familiar Markdown-based syntax. Users can develop the views that work best for them with charts that display any metric VividCortex captures plus any additional metrics they send to the app. They can graph multiple hosts in each chart and/or collect the charts they want into any given dashboard to help monitor performance and diagnose issues.

“It’s exciting that our customers are already using these new features to solve problems they couldn’t before,” said Baron Schwartz, Chief Technology Officer and Founder. “This launch is a significant step towards making database monitoring simpler and more powerful for the entire engineering team. With the workflows these features support, it’s easier for the whole engineering team – especially application developers – to master database performance, take ownership of the code they deploy, and collaborate seamlessly with other stakeholders.”

General availability of the new VividCortex features is scheduled for November 26.  The VividCortex team will demonstrate Explorer, Notebooks and Charts Dashboards for attendees at AWS re: Invent in Las Vegas at Booth #1406 in Expo at The Venetian.


FIGURE:  See how a recent code deployment impacted system performance.  Developers use VividCortex Explorer to examine CPU Utilization. Explorer shows a spike in CPU usage and the effect that it had on the Total Time of all queries. To find the query that is causing the spike, we switch to a graph of Count instead of Time. After checking and eliminating two queries, we discover that the CPU-usage spike was due to the third query (orange bullet). Culprit identified!



Media Contact