diff --git a/src/data/roadmaps/full-stack/content/125-monitoring.md b/src/data/roadmaps/full-stack/content/125-monitoring.md
index 620186450..0301d9798 100644
--- a/src/data/roadmaps/full-stack/content/125-monitoring.md
+++ b/src/data/roadmaps/full-stack/content/125-monitoring.md
@@ -1,46 +1,12 @@
-# Checkpoint — Monitoring
+# Checkpoint
 
-# Monitoring
+You should now implement monitoring and autorestarts for your application using monit.
 
-Monitoring is a crucial aspect of maintaining a healthy and well-performing full stack application. As a full stack developer, you need to understand and implement various monitoring tools and techniques to ensure the smooth functioning of your application throughout its life cycle.
+Here are some of the monitors you should implement for the application.
 
-In this section, we'll cover the following topics:
-
-## Importance of Monitoring
-
-Monitoring helps you to:
-
-- Detect and fix issues before they affect users and result in system downtime.
-- Optimize performance and resource usage.
-- Predict and scale for future growth by identifying trends and predicting traffic spikes.
-- Ensure security by identifying weak spots and tracking malicious activities.
-
-## Monitoring Tools
-
-There are various monitoring tools available, and it's essential to choose the right one based on your specific needs. Some popular monitoring tools include:
-
-- **Infrastructure Monitoring** (e.g., [Nagios](https://www.nagios.org/), [Zabbix](https://www.zabbix.com/), [Prometheus](https://prometheus.io/))
-- **Application Performance Monitoring (APM)** (e.g., [New Relic](https://newrelic.com/), [Dynatrace](https://www.dynatrace.com/), [AppDynamics](https://www.appdynamics.com/))
-- **Log Management** (e.g., [Elastic Stack](https://www.elastic.co/), [Graylog](https://www.graylog.org/), [Loggly](https://www.loggly.com/))
-- **Error Tracking** (e.g., [Sentry](https://sentry.io/), [Rollbar](https://rollbar.com/), [Airbrake](https://airbrake.io/))
-
-## Key Metrics to Monitor
-
-When monitoring your full stack application, make sure to track the following key metrics:
-
-- **Availability:** Percentage of time the system is operational and accessible.
-- **Response Time:** Time taken by the system to respond to a user request.
-- **Throughput:** Number of requests processed by the system per unit of time.
-- **Error Rate:** The frequency of errors occurring in the system.
-- **Resource Utilization:** Percentage of system resources (CPU, memory, disk, etc.) being used.
-
-## Monitoring Best Practices
-
-Follow these best practices to ensure effective monitoring and smooth functioning of your application:
-
-1. **Establish Goals:** Define measurable objectives based on your business requirements and use them to set performance thresholds.
-2. **Monitor Across Different Levels:** Monitor at the infrastructure, application, and individual user levels to get a complete view of your system's performance.
-3. **Set Up Alerts:** Configure alerts for when critical thresholds are breached, ensuring you can react promptly and minimize downtime.
-4. **Analyze and Optimize:** Regularly review monitoring data to identify trends and areas of improvement, and then make necessary changes to enhance your application's performance.
-
-Implementing robust monitoring solutions in your full stack application helps ensure it remains reliable, available, and secure while providing valuable insights to optimize performance and scalability for future growth.
\ No newline at end of file
+- CPU Usage
+- Memory Usage
+- Disk Usage
+- Network Usage
+- Service Availability
+- Process Availability