ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Elastic Beats autodiscover dynamically starts and stops log harvesters in Kubernetes based on pod labels, with a concrete Filebeat nginx example and practical limitations.
Filebeat’s Autodiscover can silently drop new logs when templates fail to apply. This guide lists symptoms, a cause‑diagnostic matrix, ordered checks, fixes tied to findings, and escalation criteria to quickly restore log ingestion.
Filebeat Autodiscover lets Beats automatically detect and ship logs from new containers, eliminating manual config. Learn how to set up Docker providers, write matching templates, test, and avoid common pitfalls.
Filebeat’s autodiscover feature lets a single config file dynamically create log inputs based on container metadata. Learn how to set it up for Docker, test it, and understand the trade‑offs in this practical guide.
Goal Verify that an Autodiscover CNAME record resolves to autodiscover.outlook.com and that the TLS certificate presented by Exchange Online matches the custom domain used by Outlook clients. Uncertainty When a CNAME exists but points to a non‑Microsoft host, Exchange Online may still return a DigiCert certificate containing the custom domain. Outlook client
Filebeat autodiscover: multi‑level glob pattern support in nested modules Goal We want to ingest logs from a directory hierarchy using Filebeat’s autodiscover, but the current configuration seems to miss files that match glob patterns spanning several levels. Constraints & Uncertainty The autodiscover module accepts glob patterns, yet the implementation
beats
logstash
docker