“We already have three monitoring tools”
Head of SRE · Observability
A Head of SRE who already runs three monitoring tools is worried about another dashboard, more context-switching during incidents, and more to maintain. Don't argue that yours is better than all three. Ask about the last incident: how long it took to find the cause, and how many tools they had to open to find it.
Practise it before the real call
Free to start. No credit card.
What the buyer says
We already have three monitoring tools. A fourth is just another dashboard nobody looks at.
How to handle it
Listen
Hear "nobody looks at". The worry is tool sprawl and attention. They haven't said monitoring is solved.
Acknowledge
Agree that adding a dashboard nobody uses makes things worse, and that tool sprawl slows incident response.
Explore
Ask about the last serious incident: how they found out, how long it took to find the cause, which tools they opened and in what order, and where they lost time. Ask which of the three tools they'd keep if they could only keep one.
Respond
Position your product around the time lost in that incident, and around consolidation if it can replace some of what they run. Be specific about what it would replace and what it would sit alongside.
Say this
“That's fair. Another dashboard nobody looks at would make things worse.”
Say this
“Think about your last serious incident. How long did it take to find the cause?”
Say this
“How many tools did you have to open to find it?”
Variations
- SRE Lead: “We've got monitoring coming out of our ears already.”
- Head of IT Operations: “Every team bought their own tool. We don't need another.”
Questions people ask
How do you respond when an SRE team says they already have monitoring tools?
Agree that tool sprawl is a real problem. Ask about their last serious incident, how long it took to find the cause and how many tools they opened, then position your product around that lost time, and say clearly what it would replace.
Why do engineering teams end up with several monitoring tools?
Different teams often choose tools for logs, metrics and tracing separately, or buy new ones as their systems change. Over time this leads to overlapping tools and slower incident response.
More objections in Observability
- “Our monitoring bill keeps going up”
- “We can't send our logs to a vendor”
- “Outages haven't hurt us”
- “Teams won't instrument their code”
Practise it before the real call
Free to start. No credit card.