diff --git a/doc/requirements.txt b/doc/requirements.txt
index 9ef34773c3..bb94d5c7d5 100644
--- a/doc/requirements.txt
+++ b/doc/requirements.txt
@@ -3,6 +3,5 @@
 # process, which may cause wedges in the gate later.
 
 sphinx>=2.0.0,!=2.1.0 # BSD
-sphinxcontrib-blockdiag>=1.1.0
 openstackdocstheme>=2.2.1 # Apache-2.0
 reno>=3.1.0 # Apache-2.0
diff --git a/doc/source/conf.py b/doc/source/conf.py
index f337d608a3..19fe28d9d9 100755
--- a/doc/source/conf.py
+++ b/doc/source/conf.py
@@ -21,7 +21,6 @@ sys.path.insert(0, os.path.abspath('../..'))
 # extensions coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
 extensions = [
     'openstackdocstheme',
-    'sphinxcontrib.blockdiag'
 ]
 
 # openstackdocstheme options
diff --git a/doc/source/devref/fluent-logging.rst b/doc/source/devref/fluent-logging.rst
index 423193af0f..5c8291f93a 100644
--- a/doc/source/devref/fluent-logging.rst
+++ b/doc/source/devref/fluent-logging.rst
@@ -32,14 +32,6 @@ Elasticsearch indexes the logs in a logstash-* index by default. Kafka stores
 the logs in a ``logs`` topic by default. Any external tool can then consume the
 ``logs`` topic.
 
-.. blockdiag::
-
-   diagram {
-     fluent-bit [stacked];
-     fluent-bit -> fluentd -> elasticsearch -> kibana;
-          fluentd -> kafka -> external_tool;
-   }
-
 The resulting logs can then be queried directly through Elasticsearch, or they
 can be viewed via Kibana. Kibana offers a dashboard that can create custom views
 on logged events, and Kibana integrates well with Elasticsearch by default.