diff --git a/opsec/anonymous_server_monitoring/index.html b/opsec/anonymous_server_monitoring/index.html
index 8840555..be5254b 100644
--- a/opsec/anonymous_server_monitoring/index.html
+++ b/opsec/anonymous_server_monitoring/index.html
@@ -60,8 +60,22 @@
 	    <div class="container">
 			<div class="row">
 				<div class="col-lg-8 col-lg-offset-2">
-  					<a href="../index.html">Previous Page</a></br></br><p><img src="../../assets/img/mulligan_sec.jpeg" width="50px" height="50px"> <ba>Mulligan Security - 06 / 02 / 2025</a></p>
+  					<a href="../index.html">Previous Page</a></br></br><p><img src="../../assets/img/mulligan_sec.jpeg" width="50px" height="50px"> <ba>Mulligan Security - 2025-02-07 </a></p>
           
+                    <h1><b>Server Monitoring</b></h1>
+
+                    <h2>What is server monitoring?</h2>
+
+                    When deploying compute resources (bare-metal, VPSes or more abstract work units) you will have to manage a living system. This system will <b>always</b> have the following characteristics:
+                    <ul>
+                        <li>Limited ressources: the amounts of RAM and CPU cycles, network bandwidth as well as storage space are neither infinite nor free.</li>
+                        <li>Evolving requirements: depending on how you use your services, how many concurrent users you have you might need more or less ressources than what you initially purchased </li>
+                        <li>Nominal operating parameters: range of RAM and CPU use, temperatures and so on in which your service performs as expected </li>
+                    </ul>
+
+                    <br><br>
+
+                    The first item is fixed and only linked to your financial constraints.
 	       </div>
 			</div><!-- /row -->
 	    </div> <!-- /container -->