diff --git a/opsec/anonymous_server_monitoring/index.html b/opsec/anonymous_server_monitoring/index.html
index be5254b..378c977 100644
--- a/opsec/anonymous_server_monitoring/index.html
+++ b/opsec/anonymous_server_monitoring/index.html
@@ -75,7 +75,26 @@
 
                     <br><br>
 
-                    The first item is fixed and only linked to your financial constraints.
+                    The first item is fixed and only linked to your financial constraints. The other two are constantly evolving and thus must be <b>monitored</b>.
+
+                    <h2>What if I don't?</h2>
+
+                    If you don't properly monitor your infrastructure you will face the following consequences sooner or later:
+
+                    <ul>
+                        <li>service instability: you won't notice when things start going awry</li>
+                        <li>costs overrun: you will end up paying more than you need to in order to deliver the same service</li>
+                        <li>undetected attacks: attacks that impact your services can go unnoticed when the cues (eg: high RAM consumption from a cryptojacking) are not picked up</li>
+                    </ul>
+
+                    <h2>How do I do it?</h2>
+                    How you monitor your systems can vary based on your technical requirements. It can be as simple as logging in once a week, check the output of some diagnostic command and calling it a day.
+                    This will give you a snapshot but you will miss a lot of important information. You can also set up a complicated system that reports current metrics, trends and gives you capacity planning alerts
+                    based on the data obtained!
+
+                    You will have to find the middle-ground yourself, this article will propose one that you can tweak whichever way you need.
+
+                    <h2>Risks of doing it improperly</h2>
 	       </div>
 			</div><!-- /row -->
 	    </div> <!-- /container -->