Services Consulting & support
24/7 monitoring
Continuous monitoring of your services, with alerts reviewed by an engineer, so problems are noticed early and reach the right person.
At a glance
- Includes
- Metrics, logs and uptime checks, tuned alerts, regular review of recurring incidents
- Works with
- Your cloud accounts, applications and ticketing tools
- Delivered as
- An agreed monitoring setup, run continuously, with a written escalation path
- Starts with
- A review of your services and what matters most to keep running
Fit
Is this right for you?
Usually the right call when one of these sounds familiar.
Customers tell you first
Problems come to light through complaints, not through your own alerts.
Alerts nobody trusts
So many fire that the real ones are missed.
Nobody watching out of hours
Systems run overnight and at weekends without anyone looking.
Repeat incidents
The same fault returns and no one has time to find the cause.
Not the right service? Need routine upkeep and fixes: Maintenance. Need advice on what to monitor and why: IT consultancy.
Scope
Scope and what you get
Agreed with you in writing before work starts. Each piece of work has a matching thing you receive.
- What we do
Metrics, logs and uptime checks
We set up measurement across the services you name, in your own accounts.
What you receiveVisibility you can read
Dashboards that show how your services are behaving, in your own tools.
- What we do
Alerts tuned to your services
We decide with you what deserves an alert and what is only noise.
What you receiveAlerts that matter
Fewer, clearer alerts, each routed to a named engineer.
- What we do
Engineer-reviewed alerts
Alerts are looked at by an engineer rather than passed on untouched.
What you receiveA written escalation path
Who is contacted, in what order and for which kind of problem.
- What we do
Review of recurring incidents
We look for patterns in what keeps happening and suggest the fix.
What you receiveRegular findings
A written summary of incidents and the changes that would prevent them.
Use cases
Relevant use cases
Practical situations where this service is put to work. Open a card to see how it applies.
Watching a customer-facing service
Checks that a service your customers rely on is up and behaving, with the right person told when it is not.
- Uptime checks on the pages and APIs you name
- Alerts routed to a named engineer
- Dashboards your team can read
Cutting alert noise
A clean-up of existing alerts so the ones that fire are worth acting on.
- Existing alerts reviewed with you
- Duplicates and low-value alerts retired
- Thresholds based on observed behaviour
Covering nights and weekends
Monitoring that keeps running when your own team is away, with an agreed way to reach someone.
- Coverage hours and contacts agreed in writing
- Escalation steps documented
- Incident notes shared afterwards
Sample use cases, drafted as placeholders. The Plethora team confirms the final list.
Process
How it works
Four stops, agreed with you as we go. Each shows what we do and what we need from you.
Understand
We doWe map the services you run, how they fit together and which failures matter most.
You doYou list your key services and tell us who should be contacted for each.
Plan
We doWe agree what to measure, what deserves an alert and how alerts are escalated.
You doYou confirm the alert rules, contacts and the hours of coverage you want.
Support
We doWe run the monitoring, review alerts as they arrive and pass on what needs action.
You doYou act on or hand on what we escalate, and tell us when something changes.
Review
We doWe go through recurring incidents and alert quality, and recommend changes.
You doYou decide which changes to make and tell us what to watch next.
Quality
Quality and handover
How the work is checked, accepted and passed to you.
Alerts reviewed by a person
An engineer looks at an alert before it is passed to you.
Rules written down
What triggers an alert and who receives it is documented.
Regular review
Alerts and incidents are checked together, and thresholds adjusted.
A defined handover
Dashboards, rules and runbooks stay in your accounts if you choose to take over.
Tools
Tools and technology
Tools we use in delivery. We choose them to suit your team, and the list does not imply any partnership. Logos belong to their owners.
- Prometheus
- Grafana
- Sentry
- Jira Service Management
- Confluence
Engagement
Engagement and cost factors
Ways to work with us
Ongoing support
Monitoring and alert review run continuously under a written agreement.
A scoped setup
Monitoring built, documented and handed to your own team.
A team alongside yours
Our engineers join your on-call and review process.
What shapes scope, timing and cost
- How many services and environments are monitored
- Which hours and days need coverage
- Your existing tools and how much can be reused
- How alerts are escalated and to whom
- How much reporting you want
Scope and cost are confirmed with you in writing before work starts.
FAQ
Frequently asked questions
Not on this page. Response targets, if any, are written into the support plan we agree with you.
Monitoring finds and escalates problems. Fixes can be agreed as part of a support plan or handled by your own team.
Often, yes. We review your current setup first and keep what works.
You can. They are set up in your own accounts, with the access you choose.
Know about a problem before your customers do. Start with a conversation.
Tell us what you need and we will come back with next steps.
Talk to usRelated