You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: thoughts/articles/2019-09-09_The-Importance-of-Monitoring-and-Alerting.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,9 @@
1
-
_This thought was first published on the [DVELP blog](https://dvelp.co.uk/articles/monitoring-and-alerting) - but it was still written by me!_
2
-
3
1
We all know that monitoring and alerting are important, right? But just _how_ important do we really think that? How much do we show that in what we do?
4
2
5
-
## What happened?
6
-
7
3
This is a story about an experience I had at a previous company, where I had the pleasure of being at least partially responsible for the system going down, and what we learned.
8
4
5
+
## What happened?
6
+
9
7
As some scene-setting - we had to implement a service that would be accessed anytime a user visited the site. I did the work, got it reviewed, tested, and hey-presto, got it live. More testing, ensure nothing went bang, and went home.
10
8
11
9
The next morning, I return to work, and all is well. About 3 hours in the site goes down. _Panic!_ Time to follow the steps...
@@ -72,3 +70,5 @@ So, some takeaways from my (traumatic) trip down memory lane about how I took do
72
70
- Data is only important if you use it
73
71
- Graphs and alerts are really boring until _they save you_
74
72
- Give developers time to make "of no immediate value" things like monitoring and alerting, and make it part of any Acceptance into Service checklists
73
+
74
+
_This thought was first published on the [DVELP blog](https://dvelp.co.uk/articles/monitoring-and-alerting) - but it was still written by me!_
0 commit comments