Merge branch 'main' into leemthompo/deploy-manage-security-overview

Author: leemthompo

deploy-manage/deploy/cloud-on-k8s/troubleshooting-beats.md

@@ -25,7 +25,7 @@ When `kubectl` is used to modify a resource, it calculates the diff between the
 
 If you have configured a Beat to run as a `Deployment` and you are using a `hostPath` volume as the Beats data directory, you might encounter an error similar to the following:
 
-```shell script
+```shell
 ERROR   instance/beat.go:958    Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).
 ```
 

deploy-manage/license/manage-your-license-in-eck.md

@@ -84,7 +84,7 @@ data:
 
 You can easily create this secret using `kubectl` built-in support for secrets. Note that it must be in the same namespace as the operator:
 
-```shell script
+```shell
 kubectl create secret generic eck-license --from-file=my-license-file.json -n elastic-system
 kubectl label secret eck-license "license.k8s.elastic.co/scope"=operator -n elastic-system
 ```

reference/glossary/index.md

@@ -537,7 +537,7 @@ $$$glossary-no-op$$$ no-op
 
 $$$glossary-node$$$ node
 :   1. A single {{es}} server. One or more nodes can form a [cluster](/reference/glossary/index.md#glossary-cluster). See [Clusters, nodes, and shards](/deploy-manage/production-guidance/getting-ready-for-production-elasticsearch.md).
-2. In {{eck}}, it can refer to either an [Elasticsearch Node](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.md) or a [Kubernetes Node](https://kubernetes.io/docs/concepts/architecture/nodes/) depending on the context. ECK maps an Elasticsearch node to a Kubernetes Pod which can get scheduled onto any available Kubernetes node that can satisfy the [resource requirements](/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md) and [node constraints](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/) defined in the [pod template](/deploy-manage/deploy/cloud-on-k8s/customize-pods.md).
+2. In {{eck}}, it can refer to either an [Elasticsearch Node](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html) or a [Kubernetes Node](https://kubernetes.io/docs/concepts/architecture/nodes/) depending on the context. ECK maps an Elasticsearch node to a Kubernetes Pod which can get scheduled onto any available Kubernetes node that can satisfy the [resource requirements](/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md) and [node constraints](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/) defined in the [pod template](/deploy-manage/deploy/cloud-on-k8s/customize-pods.md).
 
 $$$NodeSet$$$NodeSet
 :   A set of Elasticsearch nodes that share the same Elasticsearch configuration and a Kubernetes Pod template. Multiple NodeSets can be defined in the Elasticsearch CRD to achieve a cluster topology consisting of groups of Elasticsearch nodes with different node roles, resource requirements and hardware configurations (Kubernetes node constraints).

reference/ingestion-tools/fleet/elastic-agent-inputs-list.md

@@ -41,7 +41,7 @@ When you [configure inputs](/reference/ingestion-tools/fleet/elastic-agent-input
 | `haproxy/metrics` | Collects stats from [HAProxy](http://www.haproxy.org/). It supports collection from TCP sockets, UNIX sockets, or HTTP with or without basic authentication. | [HAProxy module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-overview.md) ({{metricbeat}} docs) |
 | `http/metrics` | Used to call arbitrary HTTP endpoints for which a dedicated Metricbeat module is not available. | [HTTP module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-http.md) ({{metricbeat}} docs) |
 | `iis/metrics` | Periodically retrieve IIS web server related metrics. | [IIS module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-iis.md) ({{metricbeat}} docs) |
-| `jolokia/metrics` | Collects metrics from [Jolokia agents](https://jolokia.org/reference/html/agents.md) running on a target JMX server or dedicated proxy server. | [Jolokia module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-jolokia.md) ({{metricbeat}} docs) |
+| `jolokia/metrics` | Collects metrics from [Jolokia agents](https://jolokia.org/reference/html/agents.html) running on a target JMX server or dedicated proxy server. | [Jolokia module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-jolokia.md) ({{metricbeat}} docs) |
 | `kafka/metrics` | Collects metrics from the [Apache Kafka](https://kafka.apache.org/intro) event streaming platform. | [Kafka module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-kafka.md) ({{metricbeat}} docs) |
 | `kibana/metrics` | Collects metrics about {{Kibana}}. | [{{kib}} module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-kibana.md) ({{metricbeat}} docs) |
 | `kubernetes/metrics` | As one of the main pieces provided for Kubernetes monitoring, this module is capable of fetching metrics from several components. | [Kubernetes module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-kubernetes.md) ({{metricbeat}} docs) |
@@ -56,15 +56,15 @@ When you [configure inputs](/reference/ingestion-tools/fleet/elastic-agent-input
 | `oracle/metrics` | The [Oracle](https://www.oracle.com/) module for Metricbeat. It is under active development with feedback from the community. A single Metricset for Tablespace monitoring is added so the community can start gathering metrics from their nodes and contributing to the module. | [Oracle module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-oracle.md) ({{metricbeat}} docs) |
 | `postgresql/metrics` | Periodically fetches metrics from [PostgreSQL](https://www.postgresql.org/) servers. | [PostgresSQL module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-postgresql.md) ({{metricbeat}} docs) |
 | `prometheus/metrics` | Periodically scrapes metrics from [Prometheus exporters](https://prometheus.io/docs/instrumenting/exporters/). | [Prometheus module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-prometheus.md) ({{metricbeat}} docs) |
-| `rabbitmq/metrics` | Uses the [HTTP API](http://www.rabbitmq.com/management.md) created by the management plugin to collect RabbitMQ metrics. | [RabbitMQ module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-rabbitmq.md) ({{metricbeat}} docs) |
+| `rabbitmq/metrics` | Uses the [HTTP API](http://www.rabbitmq.com/management.html) created by the management plugin to collect RabbitMQ metrics. | [RabbitMQ module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-rabbitmq.md) ({{metricbeat}} docs) |
 | `redis/metrics` | Periodically fetches metrics from [Redis](http://redis.io/) servers. | [Redis module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-redis.md) ({{metricbeat}} docs) |
 | `sql/metrics` | Allows you to execute custom queries against an SQL database and store the results in {{es}}. | [SQL module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-sql.md) ({{metricbeat}} docs) |
 | `stan/metrics` | Uses [STAN monitoring server APIs](https://github.com/nats-io/nats-streaming-server/blob/master/server/monitor.go) to collect metrics. | [Stan module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-stan.md) ({{metricbeat}} docs) |
 | `statsd/metrics` | Spawns a UDP server and listens for metrics in StatsD compatible format. | [Statsd module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-statsd.md) ({{metricbeat}} docs) |
 | `syncgateway/metrics` | [beta] Monitor a Sync Gateway instance by using its REST API. | [SyncGateway module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-syncgateway.md) ({{metricbeat}} docs) |
 | `system/metrics` | Allows you to monitor your server metrics, including CPU, load, memory, network, processes, sockets, filesystem, fsstat, uptime, and more. | [System module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-system.md) ({{metricbeat}} docs) |
 | `traefik/metrics` | Periodically fetches metrics from a [Traefik](https://traefik.io/) instance. | [Traefik module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-traefik.md) ({{metricbeat}} docs) |
-| `uwsgi/metrics` | By default, collects the uWSGI stats metricset, using [StatsServer](https://uwsgi-docs.readthedocs.io/en/latest/StatsServer.md). | [uWSGI module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-uwsgi.md) ({{metricbeat}} docs) |
+| `uwsgi/metrics` | By default, collects the uWSGI stats metricset, using [StatsServer](https://uwsgi-docs.readthedocs.io/en/latest/StatsServer.html). | [uWSGI module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-uwsgi.md) ({{metricbeat}} docs) |
 | `vsphere/metrics` | Uses the [Govmomi](https://github.com/vmware/govmomi) library to collect metrics from any Vmware SDK URL (ESXi/VCenter). | [vSphere module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-vsphere.md) ({{metricbeat}} docs) |
 | `windows/metrics` | Collects metrics from Windows systems. | [Windows module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-windows.md) ({{metricbeat}} docs) |
 | `zookeeper/metrics` | Fetches statistics from the ZooKeeper service. | [ZooKeeper module](asciidocalypse://docs/beats/docs/reference/metricbeat/metricbeat-module-zookeeper.md) ({{metricbeat}} docs) |

troubleshoot/security.md

@@ -3,6 +3,10 @@ navigation_title: "Security"
 mapped_pages:
   - https://www.elastic.co/guide/en/security/current/troubleshooting-ov.html
   - https://www.elastic.co/guide/en/serverless/current/security-troubleshooting-ov.html
+applies_to:
+  stack: all
+  serverless:
+    security: all
 ---
 
 # Troubleshoot Security [troubleshooting-ov]

troubleshoot/security/agentless-integrations.md

@@ -2,6 +2,10 @@
 mapped_pages:
   - https://www.elastic.co/guide/en/security/current/agentless-integrations.html
   - https://www.elastic.co/guide/en/serverless/current/agentless-integration-troubleshooting.html
+applies_to:
+  stack: all
+  serverless:
+    security: all
 ---
 
 # Agentless integrations FAQ [agentless-integration-troubleshooting]

troubleshoot/security/detection-rules.md

@@ -5,6 +5,10 @@ mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/security-ts-detection-rules.html
   - https://www.elastic.co/guide/en/security/current/alerts-ui-monitor.html#troubleshoot-signals
   - https://www.elastic.co/guide/en/serverless/current/security-alerts-ui-monitor.html#troubleshoot-signals
+applies_to:
+  stack: all
+  serverless:
+    security: all
 ---
 
 # Troubleshoot detection rules [ts-detection-rules]

troubleshoot/security/elastic-defend.md

@@ -3,9 +3,10 @@ navigation_title: "{{elastic-defend}}"
 mapped_pages:
   - https://www.elastic.co/guide/en/security/current/ts-management.html
   - https://www.elastic.co/guide/en/serverless/current/security-troubleshoot-endpoints.html
-applies:
-  serverless: all
-  hosted: all
+applies_to:
+  stack: all
+  serverless:
+    security: all
 ---
 
 # Troubleshoot {{elastic-defend}} [ts-management]

troubleshoot/security/indicators-of-compromise.md

@@ -3,6 +3,10 @@ navigation_title: "Indicators of compromise"
 mapped_pages:
   - https://www.elastic.co/guide/en/security/current/indicators-of-compromise.html
   - https://www.elastic.co/guide/en/serverless/current/security-indicators-of-compromise.html
+applies_to:
+  stack: all
+  serverless:
+    security: all
 ---