diff --git a/src/pages/guides/using/logging_monitoring.md b/src/pages/guides/using/logging_monitoring.md
index 9a0e91a..95c55fa 100644
--- a/src/pages/guides/using/logging_monitoring.md
+++ b/src/pages/guides/using/logging_monitoring.md
@@ -47,9 +47,6 @@ I/O Runtime doesn’t offer a configuration to send activations and logs to an e
 
 Although there is no out-of-the-box integration, there are still ways you can push data from I/O Runtime to an external tool in order to monitor and debug your actions. 
 
-#### Epsagon
-One tool that made it easy to do this is [Epsagon](https://epsagon.com/?utm_source=adobe.io&utm_medium=referral&utm_campaign=adobe_io_docs). Epsagon built an integration for OpenWhisk based systems (I/O Runtime is built on top of the open source project OpenWhisk) that makes super easy to see your activations, errors, latency information and logs in their system. Check this [guide](https://docs.epsagon.com/docs/openwhisk?utm_source=adobe.io&utm_medium=referral&utm_campaign=adobe_io_docs) or this [video presentation](https://www.youtube.com/watch?v=4iprbivqrxQ&t=1517s) if you want to find more.
-
 #### New Relic
 Another tool that can be used to monitor your actions is New Relic, which offers a Node.js agent that can be used to monitor your actions. Check this [guide](https://docs.newrelic.com/docs/agents/nodejs-agent/getting-started/introduction-new-relic-nodejs) to learn more.
 
@@ -74,4 +71,4 @@ You need to package the new relic agent as part of your action code and deploy t
 
 ## Debugging Locally
 
-Check this [page](debugging.md) if you want to learn how to debug your actions locally.
\ No newline at end of file
+Check this [page](debugging.md) if you want to learn how to debug your actions locally.