diff --git a/src/content/docs/posts/Others/monitoring-websockets.mdx b/src/content/docs/posts/Others/monitoring-websockets.mdx
index 39de622..7500e84 100644
--- a/src/content/docs/posts/Others/monitoring-websockets.mdx
+++ b/src/content/docs/posts/Others/monitoring-websockets.mdx
@@ -6,10 +6,6 @@ lastUpdated: 2024-12-23
 image: /src/assets/monitoring-websockets.png
 ---
 
-:::caution[Warning]
-Still in draft
-:::
-
 ## Introduction
 
 While tools like [Sentry](https://github.com/getsentry/sentry-javascript) or [Datadog](https://github.com/DataDog/browser-sdk) are amazing to track performance issues of HTML, CSS, JavaScript, and XHR requests, they often don’t provide the best tools when it comes to [WebSockets](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket). WebSocket connections themselves may be logged, but the messages/errors sent over them are not captured by these tools.