diff --git a/changelog.d/16091.doc b/changelog.d/16091.doc
new file mode 100644
index 0000000000000000000000000000000000000000..a043df4efd8ddb6733cbff69e6cc849b3abf40c0
--- /dev/null
+++ b/changelog.d/16091.doc
@@ -0,0 +1 @@
+Structured logging docs: add a link to explain the ELK stack
diff --git a/docs/structured_logging.md b/docs/structured_logging.md
index d43dc9eb6ee88e5387c7e1c3ee09b413e23756e2..002565b22338d269bed20b3e7bc838f2664b5c2b 100644
--- a/docs/structured_logging.md
+++ b/docs/structured_logging.md
@@ -3,7 +3,7 @@
 A structured logging system can be useful when your logs are destined for a
 machine to parse and process. By maintaining its machine-readable characteristics,
 it enables more efficient searching and aggregations when consumed by software
-such as the "ELK stack".
+such as the [ELK stack](https://opensource.com/article/18/9/open-source-log-aggregation-tools).
 
 Synapse's structured logging system is configured via the file that Synapse's
 `log_config` config option points to. The file should include a formatter which