Making Cloud Monitoring
More Actionable and Consistent
I led a 15-person cloud monitoring team and helped improve
how application alerts were reviewed, incidents were
investigated, and operational knowledge was shared.
My focus was on reducing unnecessary monitoring noise,
creating repeatable troubleshooting practices, and
coordinating with developers and QA to investigate issues.
Team Leadership Incident Management Process Improvement
RoleProduct Delivery Manager / Team Lead
Team15-person cloud monitoring team
ToolsSplunk, Datadog, AWS CloudWatch
Core focusIncident handling, alert quality, and process improvement
On this page · Jump to a section
01
Project Overview
Turning monitoring data into actionable information
Application monitoring is most useful when teams can
distinguish important signals from routine noise and
respond to incidents consistently. This work focused
on improving the team's operational practices rather
than simply collecting more monitoring data.
The central problem
Repetitive alerts, inconsistent troubleshooting practices,
and issues discovered after testing made it harder to
investigate application problems efficiently. The team
needed clearer monitoring visibility, reusable procedures,
and stronger coordination across monitoring, development,
and QA.
02
The Challenge
Improving consistency across monitoring operations
The monitoring team worked with application alerts and
operational issues across a cloud-based environment.
Several challenges affected the team's ability to
investigate and follow up on problems consistently:
Alert noise: Repetitive or lower-priority alerts could make significant application issues harder to spot.
Inconsistent investigation: Troubleshooting approaches and knowledge of recurring failures needed to be documented more consistently.
Gaps discovered after testing: Some application issues surfaced during monitoring rather than being identified earlier in testing.
Cross-team follow-up: Investigating technical issues required clear coordination with developers and QA.
03
My Objective
Make monitoring actionable and repeatable
My objective was to help the team establish a more
structured and repeatable monitoring process. This
involved improving alert quality, making recurring
problems easier to investigate, documenting known
troubleshooting steps, and strengthening issue
follow-up across teams.
My approach
Help the team recognize meaningful signals, follow
consistent investigation steps, and communicate findings
clearly.
04
Interactive Monitoring Workflow
Select a stage to explore the operational process
This workflow illustrates how monitoring signals could
be reviewed, investigated, documented, and used to
improve operational practices.
From alert to process improvement
6 connected stages
01 · Monitor application health
Use Splunk, Datadog, and AWS CloudWatch to review
application signals, alerts, and recurring failures.
Simplified representation of the operational process,
not a screenshot of an internal monitoring system.
05
Monitoring Tools
Platforms used to support monitoring and investigation
Splunk
Review logs and application signals to investigate errors, recurring patterns, and operational issues.
Datadog
Use monitoring visibility and dashboards to review application behaviour and investigate issues.
AWS CloudWatch
Review cloud monitoring signals and support investigation of application and environment issues.
These tools supported the monitoring work. The cards
describe their general role in the process, not a
claim that every tool was used for every incident.
06
My Role and Contributions
Expand each area to explore my responsibilities
My contribution combined team leadership, operational
process improvement, monitoring visibility, and
cross-functional coordination.
01Monitoring & Alert Quality
Making monitoring information more actionable
Created and improved dashboards to make application behaviour and recurring issues easier to review.
Reviewed repetitive alerts and worked to reduce unnecessary monitoring noise.
Helped distinguish important application problems from lower-priority warnings.
Worked on alert thresholds and filtering practices to make monitoring information more actionable.
02SOPs & Troubleshooting
Making operational knowledge reusable
Created standard operating procedures and troubleshooting guides for common failures.
Documented repeatable investigation steps for known issues.
Improved knowledge sharing across the team.
Supported onboarding and knowledge transfer through reusable operational documentation.
03Team Leadership & Process
Coordinating a 15-person monitoring team
Led and coordinated a 15-person cloud monitoring team.
Established more consistent approaches to alert handling, investigation, and escalation.
Helped define repeatable ways of working across monitoring operations.
Tracked operational observations and opportunities for improvement.
04Developer & QA Coordination
Following technical issues through investigation
Coordinated with developers to investigate application errors and recurring failures.
Worked with QA on issues that required additional technical investigation.
Helped bring monitoring findings to the attention of the appropriate teams.
Followed up on bugs and supported clearer communication between teams.
07
How I Approached the Problem
A repeatable process for monitoring improvement
Identify recurring patterns.
Review repeated alerts and application failures to
understand where monitoring noise or repeated
investigation was affecting the team.
Improve monitoring visibility.
Use dashboards and alert refinement to make relevant
application problems easier to identify.
Standardize investigation.
Document known troubleshooting steps and establish
clearer alert-handling and escalation practices.
Coordinate technical follow-up.
Work with developers and QA when an issue required
additional analysis, a bug investigation, or further
technical attention.
Use observations to improve the process.
Track recurring issues and operational feedback to
identify areas where monitoring and investigation
practices could be improved.
08
Outcomes and Impact
Operational improvements observed through the work
The work helped establish a more structured and
repeatable approach to monitoring operations and
incident investigation.
✓
Reduced Monitoring Noise
Improved alert filtering and prioritization made monitoring information more actionable.
✓
Consistent Troubleshooting
SOPs and reusable guides gave the team clearer starting points for common issues.
✓
Better Issue Visibility
Dashboards and recurring-issue reviews helped the team identify application problems and patterns.
✓
Cross-Team Coordination
More structured communication supported investigation and follow-up with developers and QA.
✓
Earlier Issue Identification
Monitoring findings helped surface some application problems before they were reported by clients.
✓
Reusable Operational Knowledge
Documented procedures supported knowledge sharing, onboarding, and continuity across the team.
How impact is presented
These outcomes are described qualitatively because
verified numerical measurements are not available
for publication. The case study does not claim
unverified percentages or time savings.
09
Key Learnings
Lessons from monitoring and incident operations
Monitoring quality matters more than alert volume.
Teams need useful signals and clear prioritization
to focus attention on meaningful issues.
Documentation makes operational knowledge reusable.
Repeatable procedures reduce reliance on informal,
individual knowledge.
Incident management is cross-functional.
Monitoring teams, developers, and QA need to work
together to investigate and follow up on issues.
Process improvement requires ongoing review.
Recurring issues and team observations can reveal
where monitoring and investigation practices need
further refinement.
10
Skills Demonstrated
Capabilities applied throughout this work
Team LeadershipProduct DeliveryIncident ManagementProcess ImprovementStakeholder CoordinationRoot Cause InvestigationOperational DocumentationMonitoring DashboardsAlert PrioritizationSplunkDatadogAWS CloudWatchCross-functional Collaboration
11
Confidentiality
Protecting internal operational information
This case study describes my responsibilities
and experience at a high level. Internal
monitoring configurations, customer details,
proprietary dashboards, and sensitive operational
information have been omitted.