Key insights from a fireside chat with Chris Yates.

Choosing the right database monitoring vendor isn’t just a technical decision, it’s a strategic one that affects your teams, your estate, your growth plans, and the culture of your organisation. It’s also a personal one if you’re a DBA. Something as critical as your monitoring system will shape your day‑to‑day work, and, in many cases, how well you sleep at night.  

Things to consider when reviewing your current or future monitoring systems include, of course, the functionality they provide, but also the impact of the system on your team, the relationship with the vendor, and what the roadmap of that solution can offer you. Many organizations get stuck in the functionality of a tool, and forget to consider the other fundamental factors that take a good monitoring strategy to a great one.  

In a recent webinar, “How to Evaluate Vendors for Your Database Monitoring” I sat down with Chris Yates, Senior Vice President and Managing Director of Data & Architecture at Republic Bank, to talk about what really matters when evaluating monitoring tools. Not features. Not dashboards. But value. 

This first post focuses on why organisations revisit monitoring tools in the first place, and how perspectives on monitoring shift depending on where you sit in the business. Before you evaluate database monitoring tools, you need to understand what your organization requires. Here's how to define your monitoring requirements and who should be in the room.   

Database monitoring through different lenses

Chris has been in the industry a long time. He started as a developer, became a DBA, then a manager, and now operates as an executive leader. Through all of those transitions, database monitoring has remained a constant, but the value he got from it changed over time. 

At the DBA level, monitoring is about staying proactive: 

• Spotting issues early 

• Keeping performance stable 

• Solving problems before users notice 

At this level, a great monitoring tool is about having the complete picture at the click of a button. By removing the manual work of collecting data to evaluate database health, DBAs are given the time and space to do the strategic work to improve the system in the long run. 

As Chris moved into more senior and strategic roles, the lens widened. Monitoring became less about individual incidents and more about: 

• ROI and cost justification

• Regulatory and compliance reporting (particularly critical in regulated industries like finance)

• Capacity planning

• Team enablement and scalability

Monitoring stopped being “just a dashboard” and became a fundamental driver of efficiency and alignment across the organisation. By providing a single source of truth on the database estate, monitoring acts as the foundation that enables key strategic initiatives like moving to the cloud, passing essential audits, and opening up communication between teams that were previously siloed. 

Bringing all stakeholders into the conversation early helps ensure vendors can support the full organisation, and makes any future transition far smoother. 

When is the right time to re-evaluate your current monitoring tool?

Most organisations don’t change monitoring vendors lightly. Switching tools can be disruptive and stressful, so it’s often delayed longer than it should be. 

Chris shared a few clear signs that it may be time to reassess. 

• When friction outweighs value
  If teams spend more time working around the system than with it, that’s a red flag. Monitoring shouldn’t be a blocker, and working with your vendor shouldn’t be a source of stress. 

• Stagnation
  If your monitoring tool hasn’t evolved while your business has, the gap becomes costly quickly - especially with new platforms, cloud services, or compliance requirements. 

• Cultural shifts
  There’s a tipping point where teams stop asking “What’s possible?” and start asking “How do we survive this?” When that happens, the tool has become a constraint, not a solution. 

• Burnout in small teams
  For lone DBAs or small teams, monitoring should feel like an extra pair of hands - not another system to maintain. If it adds work instead of removing it, something isn’t right. 

Questions to ask yourself, and vendors (when you're ready)

Questions to ask yourself:

“Does our current monitoring strategy still serve the organisation we are today?” 

“Who will be impacted if the tool changes?” 

“What’s the impact of our current monitoring system on our team? What are we losing and what are we gaining?” 

“Who need confidence in the outputs our solution provides?” 

“Does everyone in the org have the visibility we need into our systems with this software? / Who else in the business depends on this data?”  

Question to ask a vendor:

“How does this tool support DBAs, developers, infrastructure teams, and leadership - together?” 

“Do you have evidence of how your solution has supported multiple stakeholders?” 

Closing thoughts

Before you compare vendors, features, or pricing models, it’s worth taking a step back. The most successful monitoring decisions Chris described weren’t driven by tooling gaps, they were driven by misalignment between the tool and the organisation’s reality. 

Once you’re clear on why you’re reassessing monitoring and who it needs to serve, the next step becomes clear: understanding the kind of vendor relationship you actually want. 

In Part 2, we’ll look at how to evaluate database monitoring vendors beyond the product, and what to expect from the people behind the technology.