Skip to content

Commit 6aa729a

Browse files
committed
fix: Updated incorrect image link for monitoring article
1 parent ccfb5ea commit 6aa729a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

thoughts/articles/2019-09-09_The-Importance-of-Monitoring-and-Alerting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Ok, let's assume we did have that monitoring in place - what is the expected num
4343

4444
Great - now let's have a look at the actual:
4545

46-
![alt text](https://dvelp-production.s3.amazonaws.com/uploads/image/file/177/x_large_1568038850-tol_service_final.PNG "Site Actual")
46+
![alt text](https://dvelp-production.s3.amazonaws.com/uploads/image/file/179/x_large_1568038897-tol_site_actual.PNG "Site Actual")
4747

4848
I think that would do it, yes. Overloading the service with around 50x the expected calls (that's already taking into account the headroom planned).
4949

0 commit comments

Comments
 (0)