docs(buffers): note known restart bugs in disk buffer docs (#25679)

Co-authored-by: Janine Chan <64388808+janine-c@users.noreply.github.com>

Author: pront

website/content/en/docs/architecture/buffering-model.md

@@ -123,6 +123,10 @@ detected, to give as accurate of a view into the number of events that were lost
 {{< warning >}}
 Disk buffers have some unique monitoring requirements compared to in-memory buffers,
 specifically around free storage space.
+
+Look at [known bugs][disk_buffer_bugs] before deploying to production.
+
+[disk_buffer_bugs]: https://github.com/vectordotdev/vector/issues?q=sort%3Aupdated-desc+is%3Aissue+state%3Aopen+label%3A%22domain%3A+buffers%22+type%3ABug
 {{< /warning >}}
 
 I/O errors are notoriously hard to recover from, as it can be difficult to know what data made it to