Merge pull request #21 from VersusControl/docs

hoalongnatsu · web-flow · commit be29afb85ac1 · 2025-02-18T22:36:41.000+07:00
(docs): update README
diff --git a/README.md b/README.md
@@ -334,7 +334,7 @@ spec:
     spec:
       containers:
       - name: versus-incident
-        image: ghcr.io/versuscontrol/versus-incident:v1.0.0
+        image: ghcr.io/versuscontrol/versus-incident
         ports:
         - containerPort: 3000
         livenessProbe:
diff --git a/src/cloudwatch-alarm-sns.md b/src/cloudwatch-alarm-sns.md
@@ -1,5 +1,7 @@
 ## Configuring CloudWatch to send Alert to Versus Incident
 
+![Diagram](docs/images/diagram.png)
+
 In this guide, you’ll learn how to set up a CloudWatch alarm to trigger when RDS CPU usage exceeds 80% and send an alert to Slack and Telegram.
 
 **Prerequisites**
diff --git a/src/docs/images/diagram.png b/src/docs/images/diagram.png
diff --git a/src/fluent-bit.md b/src/fluent-bit.md
@@ -1,5 +1,7 @@
 ## Configuring Fluent Bit to Send Error Logs to Versus Incident
 
+![Diagram](docs/images/diagram.png)
+
 Fluent Bit is a lightweight log processor and forwarder that can filter, modify, and forward logs to various destinations. In this tutorial, we will configure Fluent Bit to filter logs containing [ERROR] and send them to the Versus Incident Management System using its REST API.
 
 ### Understand the Log Format
diff --git a/src/getting_started.md b/src/getting_started.md
@@ -285,7 +285,7 @@ spec:
     spec:
       containers:
       - name: versus-incident
-        image: ghcr.io/versuscontrol/versus-incident:v1.0.0
+        image: ghcr.io/versuscontrol/versus-incident
         ports:
         - containerPort: 3000
         livenessProbe:
