From 97b55db6d28afa61d0e36473fe0865cd47183e20 Mon Sep 17 00:00:00 2001 From: Aleksandra Spilkowska Date: Fri, 13 Feb 2026 13:04:12 +0100 Subject: [PATCH] docs: add applies_to tags and scope Filebeat section to Stack only - Add mandatory applies_to (stack: ga, serverless: ga) and products to intro.md frontmatter - Add section-level applies_to to Filebeat subsection (stack: ga, serverless: unavailable) so Serverless users are not directed to use Filebeat for log shipping Co-authored-by: Cursor --- docs/reference/intro.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/reference/intro.md b/docs/reference/intro.md index 8773dcb..58a56b1 100644 --- a/docs/reference/intro.md +++ b/docs/reference/intro.md @@ -1,4 +1,12 @@ --- +applies_to: + stack: ga + serverless: ga +products: + - id: ecs-logging + - id: elastic-stack + - id: elasticsearch + - id: kibana mapped_pages: - https://www.elastic.co/guide/en/ecs-logging/overview/current/intro.html - https://www.elastic.co/guide/en/ecs-logging/overview/current/index.html @@ -61,6 +69,11 @@ Using a common schema across different services and teams makes it possible crea ### Additional advantages when using in combination with Filebeat [_additional_advantages_when_using_in_combination_with_filebeat] +```{applies_to} +stack: ga +serverless: unavailable +``` + We recommend shipping the logs with Filebeat. Depending on the way the application is deployed, you may log to a log file or to stdout (for example in Kubernetes). Here are a few benefits to this over directly sending logs from the application to Elasticsearch: