From 81bb1bd95a1b90fd1687d17f5f419582abfc0adc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Tue, 4 Feb 2025 17:52:34 +0100 Subject: [PATCH 01/11] applies added to all monitoring files --- deploy-manage/monitor.md | 6 ++++++ deploy-manage/monitor/autoops.md | 2 ++ .../monitor/autoops/ec-autoops-deployment-view.md | 2 ++ .../monitor/autoops/ec-autoops-dismiss-event.md | 2 ++ .../monitor/autoops/ec-autoops-event-settings.md | 2 ++ deploy-manage/monitor/autoops/ec-autoops-events.md | 2 ++ deploy-manage/monitor/autoops/ec-autoops-faq.md | 2 ++ .../monitor/autoops/ec-autoops-how-to-access.md | 2 ++ .../monitor/autoops/ec-autoops-index-view.md | 2 ++ .../monitor/autoops/ec-autoops-nodes-view.md | 2 ++ .../autoops/ec-autoops-notifications-settings.md | 2 ++ .../monitor/autoops/ec-autoops-overview-view.md | 2 ++ deploy-manage/monitor/autoops/ec-autoops-regions.md | 2 ++ .../monitor/autoops/ec-autoops-shards-view.md | 2 ++ .../monitor/autoops/ec-autoops-template-optimizer.md | 2 ++ .../monitor/kibana-task-manager-health-monitoring.md | 4 +++- deploy-manage/monitor/logging-configuration.md | 7 +++++++ .../logging-configuration/_cli_configuration.md | 2 ++ .../logging-configuration/auditing-search-queries.md | 5 +++++ .../correlating-kibana-elasticsearch-audit-logs.md | 5 +++++ .../elasticsearch-audit-events.md | 5 +++++ .../elasticsearch-deprecation-logs.md | 5 +++++ .../elasticsearch-log4j-configuration-self-managed.md | 2 ++ ...enabling-audit-logs-in-orchestrated-deployments.md | 4 ++++ .../enabling-elasticsearch-audit-logs.md | 5 +++++ .../enabling-kibana-audit-logs.md | 5 +++++ .../monitor/logging-configuration/kibana-logging.md | 5 +++++ .../logging-configuration/log-settings-examples.md | 2 ++ .../logfile-audit-events-ignore-policies.md | 5 +++++ .../logging-configuration/logfile-audit-output.md | 7 +++++++ .../security-event-audit-logging.md | 7 +++++++ .../update-elasticsearch-logging-levels.md | 5 +++++ deploy-manage/monitor/monitoring-data.md | 11 ++++++++++- .../access-performance-metrics-on-elastic-cloud.md | 2 ++ deploy-manage/monitor/monitoring-data/beats-page.md | 5 +++++ .../config-monitoring-data-streams-elastic-agent.md | 5 +++++ .../config-monitoring-data-streams-metricbeat-8.md | 5 +++++ ...toring-indices-metricbeat-7-internal-collection.md | 5 +++++ .../configure-stack-monitoring-alerts.md | 5 +++++ .../configuring-data-streamsindices-for-monitoring.md | 5 +++++ .../monitor/monitoring-data/ec-memory-pressure.md | 3 +++ .../monitoring-data/ec-saas-metrics-accessing.md | 2 ++ .../monitor/monitoring-data/ec-vcpu-boost-instance.md | 2 ++ .../monitor/monitoring-data/ech-memory-pressure.md | 2 ++ .../monitoring-data/ech-saas-metrics-accessing.md | 2 ++ .../monitoring-data/ech-vcpu-boost-instance.md | 4 ++++ .../monitor/monitoring-data/elasticsearch-metrics.md | 5 +++++ .../monitor/monitoring-data/kibana-alerts.md | 7 +++++++ deploy-manage/monitor/monitoring-data/kibana-page.md | 5 +++++ .../monitor/monitoring-data/logstash-page.md | 5 +++++ .../monitoring-data/monitor-troubleshooting.md | 3 +++ .../monitoring-data/visualizing-monitoring-data.md | 5 +++++ deploy-manage/monitor/monitoring-overview.md | 7 +++++++ deploy-manage/monitor/orchestrators.md | 6 ++++++ .../orchestrators/ece-monitoring-ece-access.md | 2 ++ .../orchestrators/ece-monitoring-ece-set-retention.md | 2 ++ .../monitor/orchestrators/ece-platform-monitoring.md | 2 ++ .../monitor/orchestrators/ece-proxy-log-fields.md | 2 ++ .../orchestrators/eck-metrics-configuration.md | 2 ++ .../orchestrators/k8s-enabling-metrics-endpoint.md | 2 ++ .../orchestrators/k8s-prometheus-requirements.md | 2 ++ .../orchestrators/k8s-securing-metrics-endpoint.md | 2 ++ deploy-manage/monitor/stack-monitoring.md | 5 +++++ .../collecting-log-data-with-filebeat.md | 2 ++ .../collecting-monitoring-data-with-elastic-agent.md | 2 ++ .../collecting-monitoring-data-with-metricbeat.md | 2 ++ .../stack-monitoring/ece-restrictions-monitoring.md | 2 ++ .../elasticsearch-monitoring-self-managed.md | 2 ++ .../enable-stack-monitoring-on-ece-deployments.md | 2 ++ .../enable-stack-monitoring-on-eck-deployments.md | 2 ++ .../stack-monitoring/es-monitoring-collectors.md | 2 ++ .../stack-monitoring/es-monitoring-exporters.md | 2 ++ .../monitor/stack-monitoring/http-exporter.md | 2 ++ .../monitor/stack-monitoring/k8s_audit_logging.md | 2 ++ ...to_an_external_monitoring_elasticsearch_cluster.md | 2 ++ .../monitor/stack-monitoring/k8s_how_it_works.md | 2 ++ .../k8s_override_the_beats_pod_template.md | 2 ++ .../monitor/stack-monitoring/k8s_when_to_use_it.md | 2 ++ .../kibana-monitoring-self-managed.md | 4 +++- .../stack-monitoring/legacy-collection-methods.md | 3 +++ .../monitor/stack-monitoring/local-exporter.md | 2 ++ .../monitor/stack-monitoring/monitoring-data.md | 8 +++++++- .../stack-monitoring/monitoring-elastic-agent.md | 2 ++ .../monitor/stack-monitoring/monitoring-kibana.md | 3 +++ .../monitor/stack-monitoring/monitoring-metricbeat.md | 2 ++ .../monitor/stack-monitoring/pause-export.md | 2 ++ .../stack-monitoring-on-elastic-cloud-deployments.md | 2 ++ 87 files changed, 290 insertions(+), 4 deletions(-) diff --git a/deploy-manage/monitor.md b/deploy-manage/monitor.md index 1a607aa46..a2d231bcc 100644 --- a/deploy-manage/monitor.md +++ b/deploy-manage/monitor.md @@ -2,6 +2,12 @@ mapped_urls: - https://www.elastic.co/guide/en/elasticsearch/reference/current/monitor-elasticsearch-cluster.html - https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-monitoring.html +applies: + serverless: all + hosted: all + ece: all + eck: all + stack: all --- # Monitoring diff --git a/deploy-manage/monitor/autoops.md b/deploy-manage/monitor/autoops.md index 63e19c082..0c8f17f71 100644 --- a/deploy-manage/monitor/autoops.md +++ b/deploy-manage/monitor/autoops.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops.html +applies: + hosted: all --- # AutoOps [ec-autoops] diff --git a/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md b/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md index 9f15ae799..26ac5ec0d 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-deployment-view.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-deployment-view.html +applies: + hosted: all --- # Deployment [ec-autoops-deployment-view] diff --git a/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md b/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md index 9f0c308e3..ddff08d80 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md +++ b/deploy-manage/monitor/autoops/ec-autoops-dismiss-event.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-dismiss-event.html +applies: + hosted: all --- # Dismiss Events [ec-autoops-dismiss-event] diff --git a/deploy-manage/monitor/autoops/ec-autoops-event-settings.md b/deploy-manage/monitor/autoops/ec-autoops-event-settings.md index 32f4e1437..baa32c7a6 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-event-settings.md +++ b/deploy-manage/monitor/autoops/ec-autoops-event-settings.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-event-settings.html +applies: + hosted: all --- # Events Settings [ec-autoops-event-settings] diff --git a/deploy-manage/monitor/autoops/ec-autoops-events.md b/deploy-manage/monitor/autoops/ec-autoops-events.md index 313c62bff..66f390d73 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-events.md +++ b/deploy-manage/monitor/autoops/ec-autoops-events.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-events.html +applies: + hosted: all --- # AutoOps events [ec-autoops-events] diff --git a/deploy-manage/monitor/autoops/ec-autoops-faq.md b/deploy-manage/monitor/autoops/ec-autoops-faq.md index 0cf1eff85..b568084df 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-faq.md +++ b/deploy-manage/monitor/autoops/ec-autoops-faq.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-faq.html +applies: + hosted: all --- # AutoOps FAQ [ec-autoops-faq] diff --git a/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md b/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md index fd0bf60c2..ffa3d70a6 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md +++ b/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-how-to-access.html +applies: + hosted: all --- # How to access AutoOps [ec-autoops-how-to-access] diff --git a/deploy-manage/monitor/autoops/ec-autoops-index-view.md b/deploy-manage/monitor/autoops/ec-autoops-index-view.md index c2f10acef..d6d477d43 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-index-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-index-view.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-index-view.html +applies: + hosted: all --- # Indices [ec-autoops-index-view] diff --git a/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md b/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md index 47b4ec3d3..ebd0d0f02 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-nodes-view.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-nodes-view.html +applies: + hosted: all --- # Nodes [ec-autoops-nodes-view] diff --git a/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md b/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md index 0143922b1..a98231d86 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md +++ b/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-notifications-settings.html +applies: + hosted: all --- # Notifications settings [ec-autoops-notifications-settings] diff --git a/deploy-manage/monitor/autoops/ec-autoops-overview-view.md b/deploy-manage/monitor/autoops/ec-autoops-overview-view.md index 1479e4c1e..99e9037b9 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-overview-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-overview-view.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-overview-view.html +applies: + hosted: all --- # Overview [ec-autoops-overview-view] diff --git a/deploy-manage/monitor/autoops/ec-autoops-regions.md b/deploy-manage/monitor/autoops/ec-autoops-regions.md index ee1eeecba..eae21ab9a 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-regions.md +++ b/deploy-manage/monitor/autoops/ec-autoops-regions.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-regions.html +applies: + hosted: all --- # AutoOps regions [ec-autoops-regions] diff --git a/deploy-manage/monitor/autoops/ec-autoops-shards-view.md b/deploy-manage/monitor/autoops/ec-autoops-shards-view.md index 64b898316..1b5421a90 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-shards-view.md +++ b/deploy-manage/monitor/autoops/ec-autoops-shards-view.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-shards-view.html +applies: + hosted: all --- # Shards [ec-autoops-shards-view] diff --git a/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md b/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md index 75e939acc..036541b2a 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md +++ b/deploy-manage/monitor/autoops/ec-autoops-template-optimizer.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-autoops-template-optimizer.html +applies: + hosted: all --- # Template Optimizer [ec-autoops-template-optimizer] diff --git a/deploy-manage/monitor/kibana-task-manager-health-monitoring.md b/deploy-manage/monitor/kibana-task-manager-health-monitoring.md index fde3dcb27..8aa04470c 100644 --- a/deploy-manage/monitor/kibana-task-manager-health-monitoring.md +++ b/deploy-manage/monitor/kibana-task-manager-health-monitoring.md @@ -1,7 +1,9 @@ --- -navigation_title: "Health monitoring" +navigation_title: "Kibana task manager monitoring" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/task-manager-health-monitoring.html +applies: + stack: preview --- diff --git a/deploy-manage/monitor/logging-configuration.md b/deploy-manage/monitor/logging-configuration.md index 6d2a21122..80a04a2b2 100644 --- a/deploy-manage/monitor/logging-configuration.md +++ b/deploy-manage/monitor/logging-configuration.md @@ -1,3 +1,10 @@ +--- +applies: + hosted: all + ece: all + eck: all + stack: all +--- # Logging configuration % What needs to be done: Write from scratch diff --git a/deploy-manage/monitor/logging-configuration/_cli_configuration.md b/deploy-manage/monitor/logging-configuration/_cli_configuration.md index f16638fa4..b207bd7eb 100644 --- a/deploy-manage/monitor/logging-configuration/_cli_configuration.md +++ b/deploy-manage/monitor/logging-configuration/_cli_configuration.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/kibana/current/_cli_configuration.html +applies: + stack: all --- # Cli configuration [_cli_configuration] diff --git a/deploy-manage/monitor/logging-configuration/auditing-search-queries.md b/deploy-manage/monitor/logging-configuration/auditing-search-queries.md index 03aec6569..f91abe8fb 100644 --- a/deploy-manage/monitor/logging-configuration/auditing-search-queries.md +++ b/deploy-manage/monitor/logging-configuration/auditing-search-queries.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/auditing-search-queries.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Auditing search queries [auditing-search-queries] diff --git a/deploy-manage/monitor/logging-configuration/correlating-kibana-elasticsearch-audit-logs.md b/deploy-manage/monitor/logging-configuration/correlating-kibana-elasticsearch-audit-logs.md index 4cdc2c8ff..467d76aa5 100644 --- a/deploy-manage/monitor/logging-configuration/correlating-kibana-elasticsearch-audit-logs.md +++ b/deploy-manage/monitor/logging-configuration/correlating-kibana-elasticsearch-audit-logs.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/kibana/current/xpack-security-audit-logging.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Correlating Kibana and Elasticsearch audit logs [xpack-security-audit-logging] diff --git a/deploy-manage/monitor/logging-configuration/elasticsearch-audit-events.md b/deploy-manage/monitor/logging-configuration/elasticsearch-audit-events.md index 1e4da56ad..cbca6ce14 100644 --- a/deploy-manage/monitor/logging-configuration/elasticsearch-audit-events.md +++ b/deploy-manage/monitor/logging-configuration/elasticsearch-audit-events.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/audit-event-types.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Elasticsearch audit events [audit-event-types] diff --git a/deploy-manage/monitor/logging-configuration/elasticsearch-deprecation-logs.md b/deploy-manage/monitor/logging-configuration/elasticsearch-deprecation-logs.md index d86fe96e1..e79f2bfc5 100644 --- a/deploy-manage/monitor/logging-configuration/elasticsearch-deprecation-logs.md +++ b/deploy-manage/monitor/logging-configuration/elasticsearch-deprecation-logs.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/logging.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Elasticsearch deprecation logs [logging] diff --git a/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md b/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md index 5138d9d19..0842231f9 100644 --- a/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md +++ b/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/logging.html +applies: + stack: all --- # Elasticsearch log4j configuration (self-managed) [logging] diff --git a/deploy-manage/monitor/logging-configuration/enabling-audit-logs-in-orchestrated-deployments.md b/deploy-manage/monitor/logging-configuration/enabling-audit-logs-in-orchestrated-deployments.md index b64e75d28..06e2ffd2d 100644 --- a/deploy-manage/monitor/logging-configuration/enabling-audit-logs-in-orchestrated-deployments.md +++ b/deploy-manage/monitor/logging-configuration/enabling-audit-logs-in-orchestrated-deployments.md @@ -3,6 +3,10 @@ mapped_urls: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-enable-auditing.html - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s_audit_logging.html - https://www.elastic.co/guide/en/cloud/current/ec-enable-logging-and-monitoring.html#ec-enable-audit-logs +applies: + hosted: all + ece: all + eck: all --- # Enabling audit logs in orchestrated deployments diff --git a/deploy-manage/monitor/logging-configuration/enabling-elasticsearch-audit-logs.md b/deploy-manage/monitor/logging-configuration/enabling-elasticsearch-audit-logs.md index 6ca3ed0ec..462a6ef47 100644 --- a/deploy-manage/monitor/logging-configuration/enabling-elasticsearch-audit-logs.md +++ b/deploy-manage/monitor/logging-configuration/enabling-elasticsearch-audit-logs.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/enable-audit-logging.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Enabling elasticsearch audit logs [enable-audit-logging] diff --git a/deploy-manage/monitor/logging-configuration/enabling-kibana-audit-logs.md b/deploy-manage/monitor/logging-configuration/enabling-kibana-audit-logs.md index 3d91280a5..e3ace4b82 100644 --- a/deploy-manage/monitor/logging-configuration/enabling-kibana-audit-logs.md +++ b/deploy-manage/monitor/logging-configuration/enabling-kibana-audit-logs.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/kibana/current/xpack-security-audit-logging.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Enabling Kibana audit logs [xpack-security-audit-logging] diff --git a/deploy-manage/monitor/logging-configuration/kibana-logging.md b/deploy-manage/monitor/logging-configuration/kibana-logging.md index deca01a3a..687e38e9b 100644 --- a/deploy-manage/monitor/logging-configuration/kibana-logging.md +++ b/deploy-manage/monitor/logging-configuration/kibana-logging.md @@ -1,8 +1,13 @@ --- mapped_pages: - https://www.elastic.co/guide/en/kibana/current/logging-configuration.html +applies: + stack: all --- +% this might not be valid for all deployment types. needs review. +% certain topics like LEVELS are valid for all deployment types, but not all + # Kibana logging [logging-configuration] The {{kib}} logging system has three main components: *loggers*, *appenders* and *layouts*. These components allow us to log messages according to message type and level, to control how these messages are formatted and where the final logs will be displayed or stored. diff --git a/deploy-manage/monitor/logging-configuration/log-settings-examples.md b/deploy-manage/monitor/logging-configuration/log-settings-examples.md index aa7dfc035..226346121 100644 --- a/deploy-manage/monitor/logging-configuration/log-settings-examples.md +++ b/deploy-manage/monitor/logging-configuration/log-settings-examples.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/kibana/current/log-settings-examples.html +applies: + stack: all --- # Examples [log-settings-examples] diff --git a/deploy-manage/monitor/logging-configuration/logfile-audit-events-ignore-policies.md b/deploy-manage/monitor/logging-configuration/logfile-audit-events-ignore-policies.md index 19ab65fc3..f7a164d4e 100644 --- a/deploy-manage/monitor/logging-configuration/logfile-audit-events-ignore-policies.md +++ b/deploy-manage/monitor/logging-configuration/logfile-audit-events-ignore-policies.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/audit-log-ignore-policy.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Logfile audit events ignore policies [audit-log-ignore-policy] diff --git a/deploy-manage/monitor/logging-configuration/logfile-audit-output.md b/deploy-manage/monitor/logging-configuration/logfile-audit-output.md index 68f98eff1..6ee7bbf23 100644 --- a/deploy-manage/monitor/logging-configuration/logfile-audit-output.md +++ b/deploy-manage/monitor/logging-configuration/logfile-audit-output.md @@ -1,8 +1,15 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/audit-log-output.html +applies: + hosted: all + ece: all + eck: all + stack: all --- +% evaluate the applies section + # Logfile audit output [audit-log-output] The `logfile` audit output is the only output for auditing. It writes data to the `_audit.json` file in the logs directory. diff --git a/deploy-manage/monitor/logging-configuration/security-event-audit-logging.md b/deploy-manage/monitor/logging-configuration/security-event-audit-logging.md index 9685480bc..7d12c21f7 100644 --- a/deploy-manage/monitor/logging-configuration/security-event-audit-logging.md +++ b/deploy-manage/monitor/logging-configuration/security-event-audit-logging.md @@ -1,3 +1,10 @@ +--- +applies: + hosted: all + ece: all + eck: all + stack: all +--- # Security event audit logging % What needs to be done: Write from scratch diff --git a/deploy-manage/monitor/logging-configuration/update-elasticsearch-logging-levels.md b/deploy-manage/monitor/logging-configuration/update-elasticsearch-logging-levels.md index e25780af6..f7ae66e00 100644 --- a/deploy-manage/monitor/logging-configuration/update-elasticsearch-logging-levels.md +++ b/deploy-manage/monitor/logging-configuration/update-elasticsearch-logging-levels.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/logging.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Update Elasticsearch logging levels [logging] diff --git a/deploy-manage/monitor/monitoring-data.md b/deploy-manage/monitor/monitoring-data.md index 8413ab1f7..240512af5 100644 --- a/deploy-manage/monitor/monitoring-data.md +++ b/deploy-manage/monitor/monitoring-data.md @@ -1,7 +1,16 @@ +--- +applies: + hosted: all + ece: all + eck: all + stack: all +--- # Managing monitoring data +% Probably ALL THIS NEEDS TO BE UNDER STACK MONITORING + % What needs to be done: Write from scratch % GitHub issue: https://github.com/elastic/docs-projects/issues/350 -% Scope notes: we can review the name of this section... \ No newline at end of file +% Scope notes: we can review the name of this section... diff --git a/deploy-manage/monitor/monitoring-data/access-performance-metrics-on-elastic-cloud.md b/deploy-manage/monitor/monitoring-data/access-performance-metrics-on-elastic-cloud.md index e62052455..7b56e1240 100644 --- a/deploy-manage/monitor/monitoring-data/access-performance-metrics-on-elastic-cloud.md +++ b/deploy-manage/monitor/monitoring-data/access-performance-metrics-on-elastic-cloud.md @@ -2,6 +2,8 @@ mapped_urls: - https://www.elastic.co/guide/en/cloud/current/ec-saas-metrics-accessing.html - https://www.elastic.co/guide/en/cloud-heroku/current/ech-saas-metrics-accessing.html +applies: + hosted: all --- # Access performance metrics on Elastic Cloud diff --git a/deploy-manage/monitor/monitoring-data/beats-page.md b/deploy-manage/monitor/monitoring-data/beats-page.md index 0db60e043..c65f2bd2d 100644 --- a/deploy-manage/monitor/monitoring-data/beats-page.md +++ b/deploy-manage/monitor/monitoring-data/beats-page.md @@ -2,6 +2,11 @@ navigation_title: "Beats Metrics" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/beats-page.html +applies: + hosted: all + ece: all + eck: all + stack: all --- diff --git a/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-elastic-agent.md b/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-elastic-agent.md index ed96335eb..e228fb578 100644 --- a/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-elastic-agent.md +++ b/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-elastic-agent.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/config-monitoring-data-streams-elastic-agent.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Configuring data streams created by Elastic Agent [config-monitoring-data-streams-elastic-agent] diff --git a/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-metricbeat-8.md b/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-metricbeat-8.md index 4f6262800..d267e42bf 100644 --- a/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-metricbeat-8.md +++ b/deploy-manage/monitor/monitoring-data/config-monitoring-data-streams-metricbeat-8.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/config-monitoring-data-streams-metricbeat-8.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Configuring data streams created by Metricbeat 8 [config-monitoring-data-streams-metricbeat-8] diff --git a/deploy-manage/monitor/monitoring-data/config-monitoring-indices-metricbeat-7-internal-collection.md b/deploy-manage/monitor/monitoring-data/config-monitoring-indices-metricbeat-7-internal-collection.md index c380d1807..81c4589d2 100644 --- a/deploy-manage/monitor/monitoring-data/config-monitoring-indices-metricbeat-7-internal-collection.md +++ b/deploy-manage/monitor/monitoring-data/config-monitoring-indices-metricbeat-7-internal-collection.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/config-monitoring-indices-metricbeat-7-internal-collection.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Configuring indices created by Metricbeat 7 or internal collection [config-monitoring-indices-metricbeat-7-internal-collection] diff --git a/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md b/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md index 30fa91112..866d30463 100644 --- a/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md +++ b/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md @@ -1,8 +1,13 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-cluster-health-notifications.html +applies: + hosted: all --- +% NEEDS MERGING WITH kibana-alerts.md +% this one is written for Elastic Cloud but needs to be generic, except if it's really about Elastic cloud. + # Configure Stack monitoring alerts [ec-cluster-health-notifications] You can configure Stack monitoring alerts to be sent to you by email when health related events occur in your deployments. To set up email notifications: diff --git a/deploy-manage/monitor/monitoring-data/configuring-data-streamsindices-for-monitoring.md b/deploy-manage/monitor/monitoring-data/configuring-data-streamsindices-for-monitoring.md index 6a3bd103a..e43b9c0a3 100644 --- a/deploy-manage/monitor/monitoring-data/configuring-data-streamsindices-for-monitoring.md +++ b/deploy-manage/monitor/monitoring-data/configuring-data-streamsindices-for-monitoring.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/config-monitoring-indices.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Configuring data streams/indices for monitoring [config-monitoring-indices] diff --git a/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md b/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md index 4a3b62fbf..30e72025e 100644 --- a/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md +++ b/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md @@ -1,6 +1,9 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-memory-pressure.html +applies: + hosted: all + ece: all --- # JVM memory pressure indicator [ec-memory-pressure] diff --git a/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md b/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md index 26d58bb8b..c4691c251 100644 --- a/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md +++ b/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-saas-metrics-accessing.html +applies: + hosted: all --- # Access performance metrics [ec-saas-metrics-accessing] diff --git a/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md b/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md index 162e660e6..f3f246db7 100644 --- a/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md +++ b/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-vcpu-boost-instance.html +applies: + hosted: all --- # vCPU boosting and credits [ec-vcpu-boost-instance] diff --git a/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md b/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md index 93636ef70..59f50f661 100644 --- a/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md +++ b/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md @@ -3,6 +3,8 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud-heroku/current/ech-memory-pressure.html --- +% FILE TO REMOVE (HEROKU IT COMES FROM A LIFT AND SHIFT WITH MULTIPLE URLS) + # JVM memory pressure indicator [ech-memory-pressure] In addition to the more detailed [cluster performance metrics](../stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md), the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) also includes a JVM memory pressure indicator for each node in your cluster. This indicator can help you to determine when you need to upgrade to a larger cluster. diff --git a/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md b/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md index ad331febd..bf0be6f54 100644 --- a/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md +++ b/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md @@ -3,6 +3,8 @@ mapped_pages: - https://www.elastic.co/guide/en/cloud-heroku/current/ech-saas-metrics-accessing.html --- +% FILE TO REMOVE (HEROKU IT COMES FROM A LIFT AND SHIFT WITH MULTIPLE URLS) + # Access performance metrics [ech-saas-metrics-accessing] Cluster performance metrics are available directly in the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body). The graphs on this page include a subset of Elasticsearch Add-On for Heroku-specific performance metrics. diff --git a/deploy-manage/monitor/monitoring-data/ech-vcpu-boost-instance.md b/deploy-manage/monitor/monitoring-data/ech-vcpu-boost-instance.md index 895ec40af..9b8505e72 100644 --- a/deploy-manage/monitor/monitoring-data/ech-vcpu-boost-instance.md +++ b/deploy-manage/monitor/monitoring-data/ech-vcpu-boost-instance.md @@ -1,8 +1,12 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-heroku/current/ech-vcpu-boost-instance.html +applies: + hosted: all --- +% FILE TO REMOVE (HEROKU IT COMES FROM A LIFT AND SHIFT WITH MULTIPLE URLS) + # vCPU boosting and credits [ech-vcpu-boost-instance] Elastic Cloud allows smaller instance sizes to get temporarily boosted vCPU when under heavy load. vCPU boosting is governed by vCPU credits that instances can earn over time when vCPU usage is less than the assigned amount. diff --git a/deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md b/deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md index 29d869a8e..bb53190d6 100644 --- a/deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md +++ b/deploy-manage/monitor/monitoring-data/elasticsearch-metrics.md @@ -2,6 +2,11 @@ navigation_title: "{{es}} Metrics" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/elasticsearch-metrics.html +applies: + hosted: all + ece: all + eck: all + stack: all --- diff --git a/deploy-manage/monitor/monitoring-data/kibana-alerts.md b/deploy-manage/monitor/monitoring-data/kibana-alerts.md index fcd729e92..5aa523890 100644 --- a/deploy-manage/monitor/monitoring-data/kibana-alerts.md +++ b/deploy-manage/monitor/monitoring-data/kibana-alerts.md @@ -1,8 +1,15 @@ --- mapped_pages: - https://www.elastic.co/guide/en/kibana/current/kibana-alerts.html +applies: + hosted: all + ece: all + eck: all + stack: all --- +% NEEDS TO BE MERGED WITH configure-stack-monitoring-alerts.md + # Kibana alerts [kibana-alerts] The {{stack}} {monitor-features} provide [Alerting rules](../../../explore-analyze/alerts/kibana.md) out-of-the box to notify you of potential issues in the {{stack}}. These rules are preconfigured based on the best practices recommended by Elastic. However, you can tailor them to meet your specific needs. diff --git a/deploy-manage/monitor/monitoring-data/kibana-page.md b/deploy-manage/monitor/monitoring-data/kibana-page.md index 4cc9cdb26..79b0a8bb9 100644 --- a/deploy-manage/monitor/monitoring-data/kibana-page.md +++ b/deploy-manage/monitor/monitoring-data/kibana-page.md @@ -2,6 +2,11 @@ navigation_title: "{{kib}} Metrics" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/kibana-page.html +applies: + hosted: all + ece: all + eck: all + stack: all --- diff --git a/deploy-manage/monitor/monitoring-data/logstash-page.md b/deploy-manage/monitor/monitoring-data/logstash-page.md index 4a896750b..440228333 100644 --- a/deploy-manage/monitor/monitoring-data/logstash-page.md +++ b/deploy-manage/monitor/monitoring-data/logstash-page.md @@ -2,6 +2,11 @@ navigation_title: "Logstash Metrics" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/logstash-page.html +applies: + hosted: all + ece: all + eck: all + stack: all --- diff --git a/deploy-manage/monitor/monitoring-data/monitor-troubleshooting.md b/deploy-manage/monitor/monitoring-data/monitor-troubleshooting.md index 010b0611a..fbd94e37b 100644 --- a/deploy-manage/monitor/monitoring-data/monitor-troubleshooting.md +++ b/deploy-manage/monitor/monitoring-data/monitor-troubleshooting.md @@ -2,8 +2,11 @@ navigation_title: "Troubleshooting" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/monitor-troubleshooting.html +applies: + stack: all --- +% this page probably needs to be moved # Troubleshooting [monitor-troubleshooting] diff --git a/deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md b/deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md index 5cac99ea2..364b99dfa 100644 --- a/deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md +++ b/deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md @@ -1,6 +1,11 @@ --- mapped_pages: - https://www.elastic.co/guide/en/kibana/current/xpack-monitoring.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Visualizing monitoring data [xpack-monitoring] diff --git a/deploy-manage/monitor/monitoring-overview.md b/deploy-manage/monitor/monitoring-overview.md index dd77e09a5..eab8b2690 100644 --- a/deploy-manage/monitor/monitoring-overview.md +++ b/deploy-manage/monitor/monitoring-overview.md @@ -1,3 +1,10 @@ +--- +applies: + hosted: all + ece: all + eck: all + stack: all +--- # Monitoring overview % What needs to be done: Write from scratch diff --git a/deploy-manage/monitor/orchestrators.md b/deploy-manage/monitor/orchestrators.md index 9f6e51709..2d671dbd2 100644 --- a/deploy-manage/monitor/orchestrators.md +++ b/deploy-manage/monitor/orchestrators.md @@ -1,3 +1,9 @@ +--- +applies: + ece: all + eck: all +--- + # Monitoring Orchestrators % What needs to be done: Write from scratch diff --git a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md index 3e06693b6..b369d1369 100644 --- a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md +++ b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-monitoring-ece-access.html +applies: + ece: all --- # Access logs and metrics [ece-monitoring-ece-access] diff --git a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md index 7105de040..af3a7f194 100644 --- a/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md +++ b/deploy-manage/monitor/orchestrators/ece-monitoring-ece-set-retention.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-monitoring-ece-set-retention.html +applies: + ece: all --- # Set the retention period for logging and metrics indices [ece-monitoring-ece-set-retention] diff --git a/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md b/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md index a73d3e077..2414e97ce 100644 --- a/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md +++ b/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-monitoring-ece.html +applies: + ece: all --- # ECE platform monitoring [ece-monitoring-ece] diff --git a/deploy-manage/monitor/orchestrators/ece-proxy-log-fields.md b/deploy-manage/monitor/orchestrators/ece-proxy-log-fields.md index 5fde6bc67..d80f84bbe 100644 --- a/deploy-manage/monitor/orchestrators/ece-proxy-log-fields.md +++ b/deploy-manage/monitor/orchestrators/ece-proxy-log-fields.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-proxy-log-fields.html +applies: + ece: all --- # Proxy Log Fields [ece-proxy-log-fields] diff --git a/deploy-manage/monitor/orchestrators/eck-metrics-configuration.md b/deploy-manage/monitor/orchestrators/eck-metrics-configuration.md index 223a4743c..ee351b7ad 100644 --- a/deploy-manage/monitor/orchestrators/eck-metrics-configuration.md +++ b/deploy-manage/monitor/orchestrators/eck-metrics-configuration.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-configure-operator-metrics.html +applies: + eck: all --- # ECK metrics configuration [k8s-configure-operator-metrics] diff --git a/deploy-manage/monitor/orchestrators/k8s-enabling-metrics-endpoint.md b/deploy-manage/monitor/orchestrators/k8s-enabling-metrics-endpoint.md index e11e4b23f..2c8ac4285 100644 --- a/deploy-manage/monitor/orchestrators/k8s-enabling-metrics-endpoint.md +++ b/deploy-manage/monitor/orchestrators/k8s-enabling-metrics-endpoint.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-enabling-the-metrics-endpoint.html +applies: + eck: all --- # Enabling the metrics endpoint [k8s-enabling-the-metrics-endpoint] diff --git a/deploy-manage/monitor/orchestrators/k8s-prometheus-requirements.md b/deploy-manage/monitor/orchestrators/k8s-prometheus-requirements.md index 964e60919..3e9bb2d39 100644 --- a/deploy-manage/monitor/orchestrators/k8s-prometheus-requirements.md +++ b/deploy-manage/monitor/orchestrators/k8s-prometheus-requirements.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-prometheus-requirements.html +applies: + eck: all --- # Prometheus requirements [k8s-prometheus-requirements] diff --git a/deploy-manage/monitor/orchestrators/k8s-securing-metrics-endpoint.md b/deploy-manage/monitor/orchestrators/k8s-securing-metrics-endpoint.md index da923c22e..8177a7697 100644 --- a/deploy-manage/monitor/orchestrators/k8s-securing-metrics-endpoint.md +++ b/deploy-manage/monitor/orchestrators/k8s-securing-metrics-endpoint.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-securing-the-metrics-endpoint.html +applies: + eck: all --- # Securing the metrics endpoint [k8s-securing-the-metrics-endpoint] diff --git a/deploy-manage/monitor/stack-monitoring.md b/deploy-manage/monitor/stack-monitoring.md index 17f524092..1a8e02612 100644 --- a/deploy-manage/monitor/stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring.md @@ -3,6 +3,11 @@ mapped_urls: - https://www.elastic.co/guide/en/elasticsearch/reference/current/monitoring-overview.html - https://www.elastic.co/guide/en/elasticsearch/reference/current/how-monitoring-works.html - https://www.elastic.co/guide/en/cloud/current/ec-monitoring.html +applies: + hosted: all + ece: all + eck: all + stack: all --- # Stack Monitoring diff --git a/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md b/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md index cf06e7425..f95355ec3 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md @@ -2,6 +2,8 @@ navigation_title: "Collecting log data with {{filebeat}}" mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-filebeat.html +applies: + stack: all --- diff --git a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md index 2db0f2e4e..14baada1f 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md @@ -2,6 +2,8 @@ navigation_title: "Collecting monitoring data with {{agent}}" mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-elastic-agent.html +applies: + stack: ga 8.5.0 --- diff --git a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md index 16f2113b4..7d981f75b 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md @@ -2,6 +2,8 @@ navigation_title: "Collecting monitoring data with {{metricbeat}}" mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-metricbeat.html +applies: + stack: ga 6.5.0 --- diff --git a/deploy-manage/monitor/stack-monitoring/ece-restrictions-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-restrictions-monitoring.md index a11e1d8de..06391bd4e 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-restrictions-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-restrictions-monitoring.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-restrictions-monitoring.html +applies: + ece: all --- # Restrictions and limitations [ece-restrictions-monitoring] diff --git a/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md b/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md index 59d38d2ea..56238289a 100644 --- a/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md +++ b/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md @@ -2,6 +2,8 @@ mapped_urls: - https://www.elastic.co/guide/en/elasticsearch/reference/current/monitoring-production.html - https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-monitoring.html +applies: + stack: all --- # Elasticsearch monitoring self-managed diff --git a/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md b/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md index d6c6f0be2..5aed4cd0c 100644 --- a/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md +++ b/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-enable-logging-and-monitoring.html +applies: + ece: all --- # Enable stack monitoring on ECE deployments [ece-enable-logging-and-monitoring] diff --git a/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-eck-deployments.md b/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-eck-deployments.md index defe7cfe8..12eeabee2 100644 --- a/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-eck-deployments.md +++ b/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-eck-deployments.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-stack-monitoring.html +applies: + eck: all --- # Enable stack monitoring on ECK deployments [k8s-stack-monitoring] diff --git a/deploy-manage/monitor/stack-monitoring/es-monitoring-collectors.md b/deploy-manage/monitor/stack-monitoring/es-monitoring-collectors.md index b07ba8717..70e521348 100644 --- a/deploy-manage/monitor/stack-monitoring/es-monitoring-collectors.md +++ b/deploy-manage/monitor/stack-monitoring/es-monitoring-collectors.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/es-monitoring-collectors.html +applies: + stack: deprecated 7.16.0 --- # Collectors [es-monitoring-collectors] diff --git a/deploy-manage/monitor/stack-monitoring/es-monitoring-exporters.md b/deploy-manage/monitor/stack-monitoring/es-monitoring-exporters.md index 7aea5b922..ddf003035 100644 --- a/deploy-manage/monitor/stack-monitoring/es-monitoring-exporters.md +++ b/deploy-manage/monitor/stack-monitoring/es-monitoring-exporters.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/es-monitoring-exporters.html +applies: + stack: deprecated 7.16.0 --- # Exporters [es-monitoring-exporters] diff --git a/deploy-manage/monitor/stack-monitoring/http-exporter.md b/deploy-manage/monitor/stack-monitoring/http-exporter.md index 05c168b4c..5d2bef6d3 100644 --- a/deploy-manage/monitor/stack-monitoring/http-exporter.md +++ b/deploy-manage/monitor/stack-monitoring/http-exporter.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/http-exporter.html +applies: + stack: deprecated 7.16.0 --- # HTTP exporters [http-exporter] diff --git a/deploy-manage/monitor/stack-monitoring/k8s_audit_logging.md b/deploy-manage/monitor/stack-monitoring/k8s_audit_logging.md index 819713023..cf4d89394 100644 --- a/deploy-manage/monitor/stack-monitoring/k8s_audit_logging.md +++ b/deploy-manage/monitor/stack-monitoring/k8s_audit_logging.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s_audit_logging.html +applies: + eck: all --- # Audit logging [k8s_audit_logging] diff --git a/deploy-manage/monitor/stack-monitoring/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.md b/deploy-manage/monitor/stack-monitoring/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.md index 800a8334c..9fe2e4398 100644 --- a/deploy-manage/monitor/stack-monitoring/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.md +++ b/deploy-manage/monitor/stack-monitoring/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.html +applies: + eck: all --- # Connect to an external monitoring Elasticsearch cluster [k8s_connect_to_an_external_monitoring_elasticsearch_cluster] diff --git a/deploy-manage/monitor/stack-monitoring/k8s_how_it_works.md b/deploy-manage/monitor/stack-monitoring/k8s_how_it_works.md index 777b2440d..38ea5faaf 100644 --- a/deploy-manage/monitor/stack-monitoring/k8s_how_it_works.md +++ b/deploy-manage/monitor/stack-monitoring/k8s_how_it_works.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s_how_it_works.html +applies: + eck: all --- # How it works [k8s_how_it_works] diff --git a/deploy-manage/monitor/stack-monitoring/k8s_override_the_beats_pod_template.md b/deploy-manage/monitor/stack-monitoring/k8s_override_the_beats_pod_template.md index 62e7daa88..0a43e3f70 100644 --- a/deploy-manage/monitor/stack-monitoring/k8s_override_the_beats_pod_template.md +++ b/deploy-manage/monitor/stack-monitoring/k8s_override_the_beats_pod_template.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s_override_the_beats_pod_template.html +applies: + eck: all --- # Override the Beats Pod Template [k8s_override_the_beats_pod_template] diff --git a/deploy-manage/monitor/stack-monitoring/k8s_when_to_use_it.md b/deploy-manage/monitor/stack-monitoring/k8s_when_to_use_it.md index 1f880569c..5f67296ac 100644 --- a/deploy-manage/monitor/stack-monitoring/k8s_when_to_use_it.md +++ b/deploy-manage/monitor/stack-monitoring/k8s_when_to_use_it.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s_when_to_use_it.html +applies: + eck: all --- # When to use it [k8s_when_to_use_it] diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md index f50125f5a..ae4992594 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md @@ -1,7 +1,9 @@ --- -navigation_title: "Configure monitoring" +navigation_title: "Kibana monitoring self-managed" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/configuring-monitoring.html +applies: + stack: all --- diff --git a/deploy-manage/monitor/stack-monitoring/legacy-collection-methods.md b/deploy-manage/monitor/stack-monitoring/legacy-collection-methods.md index b53a15917..da5424284 100644 --- a/deploy-manage/monitor/stack-monitoring/legacy-collection-methods.md +++ b/deploy-manage/monitor/stack-monitoring/legacy-collection-methods.md @@ -2,6 +2,9 @@ navigation_title: "Legacy collection methods" mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/collecting-monitoring-data.html +applies: + stack: deprecated 7.16.0 + stack: removed 9.0.0 --- diff --git a/deploy-manage/monitor/stack-monitoring/local-exporter.md b/deploy-manage/monitor/stack-monitoring/local-exporter.md index 895eb9490..89c175e7f 100644 --- a/deploy-manage/monitor/stack-monitoring/local-exporter.md +++ b/deploy-manage/monitor/stack-monitoring/local-exporter.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/local-exporter.html +applies: + stack: deprecated 7.16.0 --- # Local exporters [local-exporter] diff --git a/deploy-manage/monitor/stack-monitoring/monitoring-data.md b/deploy-manage/monitor/stack-monitoring/monitoring-data.md index 98eabc7e2..24d26275a 100644 --- a/deploy-manage/monitor/stack-monitoring/monitoring-data.md +++ b/deploy-manage/monitor/stack-monitoring/monitoring-data.md @@ -2,9 +2,15 @@ navigation_title: "View monitoring data" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/monitoring-data.html +applies: + hosted: all + ece: all + eck: all + stack: all --- - + +% hola # View monitoring data [monitoring-data] diff --git a/deploy-manage/monitor/stack-monitoring/monitoring-elastic-agent.md b/deploy-manage/monitor/stack-monitoring/monitoring-elastic-agent.md index 264f36a2b..190636cfd 100644 --- a/deploy-manage/monitor/stack-monitoring/monitoring-elastic-agent.md +++ b/deploy-manage/monitor/stack-monitoring/monitoring-elastic-agent.md @@ -2,6 +2,8 @@ navigation_title: "Collect monitoring data with {{agent}}" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/monitoring-elastic-agent.html +applies: + stack: ga 8.5.0 --- diff --git a/deploy-manage/monitor/stack-monitoring/monitoring-kibana.md b/deploy-manage/monitor/stack-monitoring/monitoring-kibana.md index ecea504b4..dbc9be5d2 100644 --- a/deploy-manage/monitor/stack-monitoring/monitoring-kibana.md +++ b/deploy-manage/monitor/stack-monitoring/monitoring-kibana.md @@ -2,6 +2,9 @@ navigation_title: "Legacy collection methods" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/monitoring-kibana.html +applies: + stack: deprecated 7.16.0 + stack: removed 9.0.0 --- diff --git a/deploy-manage/monitor/stack-monitoring/monitoring-metricbeat.md b/deploy-manage/monitor/stack-monitoring/monitoring-metricbeat.md index 0a9039b3c..3025cfb13 100644 --- a/deploy-manage/monitor/stack-monitoring/monitoring-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/monitoring-metricbeat.md @@ -2,6 +2,8 @@ navigation_title: "Collect monitoring data with {{metricbeat}}" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/monitoring-metricbeat.html +applies: + stack: ga 6.5.0 --- diff --git a/deploy-manage/monitor/stack-monitoring/pause-export.md b/deploy-manage/monitor/stack-monitoring/pause-export.md index 29c140aaa..ce63d4008 100644 --- a/deploy-manage/monitor/stack-monitoring/pause-export.md +++ b/deploy-manage/monitor/stack-monitoring/pause-export.md @@ -1,6 +1,8 @@ --- mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/pause-export.html +applies: + stack: deprecated 7.16.0 --- # Pausing data collection [pause-export] diff --git a/deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md b/deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md index c383459fc..ac8929def 100644 --- a/deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md +++ b/deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md @@ -6,6 +6,8 @@ mapped_urls: - https://www.elastic.co/guide/en/cloud-heroku/current/ech-enable-logging-and-monitoring.html - https://www.elastic.co/guide/en/cloud-heroku/current/ech-monitoring-setup.html - https://www.elastic.co/guide/en/cloud-heroku/current/ech-restrictions-monitoring.html +applies: + hosted: all --- # Stack Monitoring on Elastic Cloud deployments From ab562bb2c5182dbf9405211aeffd313a75536f3d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Tue, 4 Feb 2025 20:13:42 +0100 Subject: [PATCH 02/11] renaming monitoing files stage 1 --- ...ud-hosted-deployment-billing-dimensions.md | 2 +- .../ece-configuring-ece-create-templates.md | 2 +- .../system-deployments-configuration.md | 2 +- .../cloud-on-k8s/manage-compute-resources.md | 2 +- .../elastic-cloud/azure-native-isv-service.md | 2 +- .../ec-customize-deployment-components.md | 2 +- .../ech-customize-deployment-components.md | 2 +- .../deploy/elastic-cloud/ech-restrictions.md | 4 ++-- .../elastic-cloud/manage-deployments.md | 2 +- .../restrictions-known-problems.md | 2 +- .../configure-stack-monitoring-alerts.md | 2 +- .../ec-saas-metrics-accessing.md | 4 ++-- .../monitoring-data/ech-memory-pressure.md | 2 +- .../ech-saas-metrics-accessing.md | 2 +- .../orchestrators/ece-platform-monitoring.md | 2 +- .../collecting-log-data-with-filebeat.md | 2 +- ...ting-monitoring-data-with-elastic-agent.md | 4 ++-- ...lecting-monitoring-data-with-metricbeat.md | 4 ++-- ...deployments.md => ece-stack-monitoring.md} | 4 ++-- ...deployments.md => eck-stack-monitoring.md} | 0 ...s.md => elastic-cloud-stack-monitoring.md} | 0 .../{http-exporter.md => es-http-exporter.md} | 0 ...ods.md => es-legacy-collection-methods.md} | 4 ++-- ...local-exporter.md => es-local-exporter.md} | 0 .../es-monitoring-exporters.md | 6 ++--- .../{pause-export.md => es-pause-export.md} | 0 ...ring-data.md => kibana-monitoring-data.md} | 0 ....md => kibana-monitoring-elastic-agent.md} | 2 +- ...-kibana.md => kibana-monitoring-legacy.md} | 4 ++-- ...eat.md => kibana-monitoring-metricbeat.md} | 2 +- .../kibana-monitoring-self-managed.md | 8 +++---- deploy-manage/toc.yml | 22 +++++++++---------- .../manage-users-roles.md | 2 +- .../cloud-on-k8s/k8s-advanced-topics.md | 2 +- .../ece-monitoring-deployments.md | 2 +- .../cloud-heroku/ech-add-user-settings.md | 2 +- .../cloud-heroku/ech-config-change-errors.md | 2 +- .../cloud/cloud-heroku/ech-configure.md | 2 +- .../ech-enable-logging-and-monitoring.md | 10 ++++----- .../cloud-heroku/ech-manage-apm-settings.md | 2 +- .../ech-manage-kibana-settings.md | 2 +- .../cloud-heroku/ech-monitoring-setup.md | 2 +- .../cloud/cloud-heroku/ech-monitoring.md | 16 +++++++------- .../ech-saas-metrics-accessing.md | 2 +- .../echscenario_why_is_my_node_unavailable.md | 2 +- .../cloud/cloud/ec-add-user-settings.md | 2 +- .../cloud/cloud/ec-config-change-errors.md | 2 +- .../cloud/ec-enable-logging-and-monitoring.md | 10 ++++----- .../cloud/cloud/ec-manage-apm-settings.md | 2 +- .../cloud/cloud/ec-manage-kibana-settings.md | 2 +- .../cloud/cloud/ec-monitoring-setup.md | 2 +- .../cloud/cloud/ec-monitoring.md | 2 +- .../cloud/cloud/ec-prepare-production.md | 2 +- .../cloud/cloud/ec-saas-metrics-accessing.md | 4 ++-- .../ec-scenario_why_are_shards_unavailable.md | 2 +- .../ec-scenario_why_is_my_node_unavailable.md | 2 +- .../how-monitoring-works.md | 2 +- .../monitor-elasticsearch-cluster.md | 2 +- .../monitoring-production.md | 10 ++++----- ...upgrade-elastic-stack-for-elastic-cloud.md | 2 +- .../observability/apps/monitor-apm-server.md | 2 +- .../apps/monitor-fleet-managed-apm-server.md | 2 +- ...rnal-collection-to-send-monitoring-data.md | 2 +- .../use-metricbeat-to-send-monitoring-data.md | 2 +- troubleshoot/elasticsearch/high-cpu-usage.md | 2 +- 65 files changed, 101 insertions(+), 101 deletions(-) rename deploy-manage/monitor/stack-monitoring/{enable-stack-monitoring-on-ece-deployments.md => ece-stack-monitoring.md} (96%) rename deploy-manage/monitor/stack-monitoring/{enable-stack-monitoring-on-eck-deployments.md => eck-stack-monitoring.md} (100%) rename deploy-manage/monitor/stack-monitoring/{stack-monitoring-on-elastic-cloud-deployments.md => elastic-cloud-stack-monitoring.md} (100%) rename deploy-manage/monitor/stack-monitoring/{http-exporter.md => es-http-exporter.md} (100%) rename deploy-manage/monitor/stack-monitoring/{legacy-collection-methods.md => es-legacy-collection-methods.md} (97%) rename deploy-manage/monitor/stack-monitoring/{local-exporter.md => es-local-exporter.md} (100%) rename deploy-manage/monitor/stack-monitoring/{pause-export.md => es-pause-export.md} (100%) rename deploy-manage/monitor/stack-monitoring/{monitoring-data.md => kibana-monitoring-data.md} (100%) rename deploy-manage/monitor/stack-monitoring/{monitoring-elastic-agent.md => kibana-monitoring-elastic-agent.md} (98%) rename deploy-manage/monitor/stack-monitoring/{monitoring-kibana.md => kibana-monitoring-legacy.md} (95%) rename deploy-manage/monitor/stack-monitoring/{monitoring-metricbeat.md => kibana-monitoring-metricbeat.md} (99%) diff --git a/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md b/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md index df2eb4eb0..23a8c7369 100644 --- a/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md +++ b/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md @@ -57,7 +57,7 @@ Data transfer out of deployments and between nodes of the cluster is hard to con The largest contributor to inter-node data transfer is usually shard movement between nodes in a cluster. The only way to prevent shard movement is by having a single node in a single availability zone. This solution is only possible for clusters up to 64GB RAM and is not recommended as it creates a risk of data loss. [Oversharding](https://www.elastic.co/guide/en/elasticsearch/reference/current/avoid-oversharding.html) can cause excessive shard movement. Avoiding oversharding can also help control costs and improve performance. Note that creating snapshots generates inter-node data transfer. The *storage* cost of snapshots is detailed later in this document. -The exact root cause of unusual data transfer is not always something we can identify as it can have many causes, some of which are out of our control and not associated with Cloud configuration changes. It may help to [enable monitoring](../../monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) and examine index and shard activity on your cluster. +The exact root cause of unusual data transfer is not always something we can identify as it can have many causes, some of which are out of our control and not associated with Cloud configuration changes. It may help to [enable monitoring](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) and examine index and shard activity on your cluster. ## Storage [storage] diff --git a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md index 6924741d5..dfa651cea 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-configuring-ece-create-templates.md @@ -72,7 +72,7 @@ Before you start creating your own deployment templates, you should have: [tagge 9. On this page you can [configure index management](ece-configure-templates-index-management.md) by assigning attributes to each of the data nodes in the deployment template. In Kibana, you can configure an index lifecycle management (ILM) policy, based on the node attributes, to control how data moves across the nodes in your deployment. 10. Select **Stack features**. 11. You can select a [snapshot repository](../../tools/snapshot-and-restore/cloud-enterprise.md) to be used by default for deployment backups. -12. You can choose to [enable logging and monitoring](../../monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md) by default, so that deployment logs and metrics are send to a dedicated monitoring deployment, and so that additional log types, retention options, and Kibana visualizations are available on all deployments created using this template. +12. You can choose to [enable logging and monitoring](../../monitor/stack-monitoring/ece-stack-monitoring.md) by default, so that deployment logs and metrics are send to a dedicated monitoring deployment, and so that additional log types, retention options, and Kibana visualizations are available on all deployments created using this template. 13. Select **Extensions**. 14. Select any Elasticsearch extensions that you would like to be available automatically to all deployments created using the template. 15. Select **Save and create template**. diff --git a/deploy-manage/deploy/cloud-enterprise/system-deployments-configuration.md b/deploy-manage/deploy/cloud-enterprise/system-deployments-configuration.md index 7c45c2c23..d76a85d1a 100644 --- a/deploy-manage/deploy/cloud-enterprise/system-deployments-configuration.md +++ b/deploy-manage/deploy/cloud-enterprise/system-deployments-configuration.md @@ -70,7 +70,7 @@ In the case of the `admin-console-elasticsearch` and `security` system deploymen The `logging-and-metrics` cluster is different since, as an ECE admin, you likely want to provide users with access to the cluster in order to troubleshoot issues without your assistance, for example. In order to manage access to that cluster, you can configure roles that will provide access to the relevant indices, map those to users, and manage access to Kibana by leveraging the Elastic security integration with your authentication provider, such as LDAP, SAML, or AD. To configure one of those security realms, check [LDAP](../../users-roles/cluster-or-deployment-auth/ldap.md), [Active Directory](../../users-roles/cluster-or-deployment-auth/active-directory.md) or [SAML](../../users-roles/cluster-or-deployment-auth/saml.md). ::::{note} -The `logging-and-metrics` cluster is only intended for troubleshooting ECE deployment issues. If your use case involves modifying or normalizing logs from {{es}} or {{kib}}, use a separate [dedicated monitoring deployment](../../monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md) instead. +The `logging-and-metrics` cluster is only intended for troubleshooting ECE deployment issues. If your use case involves modifying or normalizing logs from {{es}} or {{kib}}, use a separate [dedicated monitoring deployment](../../monitor/stack-monitoring/ece-stack-monitoring.md) instead. :::: diff --git a/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md b/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md index 1bf9a189d..544cb4ac2 100644 --- a/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md +++ b/deploy-manage/deploy/cloud-on-k8s/manage-compute-resources.md @@ -329,7 +329,7 @@ To avoid this, explicitly define the requests and limits mandated by your enviro #### Monitoring Elasticsearch CPU using Stack Monitoring [k8s-monitor-compute-resources-stack-monitoring] -If [Stack Monitoring](../../monitor/stack-monitoring/enable-stack-monitoring-on-eck-deployments.md) is enabled, the pressure applied by the CPU cgroup controller to an Elasticsearch node can be evaluated from the **Stack Monitoring** page in Kibana. +If [Stack Monitoring](../../monitor/stack-monitoring/eck-stack-monitoring.md) is enabled, the pressure applied by the CPU cgroup controller to an Elasticsearch node can be evaluated from the **Stack Monitoring** page in Kibana. 1. On the **Stack Monitoring** page select the Elasticsearch node you want to monitor. 2. Select the **Advanced** tab. diff --git a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md index abbd39da9..a1b18bcaf 100644 --- a/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md +++ b/deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md @@ -324,7 +324,7 @@ $$$azure-integration-modify-deployment$$$How can I modify my {{ecloud}} deployme * [Update {{stack}} user settings](edit-stack-settings.md) in the component YML files. * [Add or remove custom plugins](add-plugins-extensions.md). * [Configure IP filtering](../../security/traffic-filtering.md). - * [Monitor your {{ecloud}} deployment](../../monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) to ensure it remains healthy. + * [Monitor your {{ecloud}} deployment](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) to ensure it remains healthy. * Add or remove API keys to use the [REST API](https://www.elastic.co/guide/en/cloud/current/ec-restful-api.html). * [And more](cloud-hosted.md) diff --git a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md index 01765f415..dca388774 100644 --- a/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md +++ b/deploy-manage/deploy/elastic-cloud/ec-customize-deployment-components.md @@ -15,7 +15,7 @@ Autoscaling reduces some of the manual effort required to manage a deployment by ## {{es}} [ec-cluster-size] -Depending upon how much data you have and what queries you plan to run, you need to select a cluster size that fits your needs. There is no silver bullet for deciding how much memory you need other than simply testing it. The [cluster performance metrics](../../monitor/stack-monitoring.md) in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) can tell you if your cluster is sized appropriately. You can also [enable deployment monitoring](../../monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) for more detailed performance metrics. Fortunately, you can change the amount of memory allocated to the cluster later without any downtime for HA deployments. +Depending upon how much data you have and what queries you plan to run, you need to select a cluster size that fits your needs. There is no silver bullet for deciding how much memory you need other than simply testing it. The [cluster performance metrics](../../monitor/stack-monitoring.md) in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body) can tell you if your cluster is sized appropriately. You can also [enable deployment monitoring](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) for more detailed performance metrics. Fortunately, you can change the amount of memory allocated to the cluster later without any downtime for HA deployments. To change a cluster’s topology, from deployment management, select **Edit deployment** from the **Actions** dropdown. Next, select a storage and RAM setting from the **Size per zone** drop-down list, and save your changes. When downsizing the cluster, make sure to have enough resources to handle the current load, otherwise your cluster will be under stress. diff --git a/deploy-manage/deploy/elastic-cloud/ech-customize-deployment-components.md b/deploy-manage/deploy/elastic-cloud/ech-customize-deployment-components.md index ddb9f7663..7022c679e 100644 --- a/deploy-manage/deploy/elastic-cloud/ech-customize-deployment-components.md +++ b/deploy-manage/deploy/elastic-cloud/ech-customize-deployment-components.md @@ -15,7 +15,7 @@ Autoscaling reduces some of the manual effort required to manage a deployment by ### {{es}} [ech-cluster-size] -Depending upon how much data you have and what queries you plan to run, you need to select a cluster size that fits your needs. There is no silver bullet for deciding how much memory you need other than simply testing it. The [cluster performance metrics](../../monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) in the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) can tell you if your cluster is sized appropriately. You can also [enable deployment monitoring](../../monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) for more detailed performance metrics. Fortunately, you can change the amount of memory allocated to the cluster later without any downtime for HA deployments. +Depending upon how much data you have and what queries you plan to run, you need to select a cluster size that fits your needs. There is no silver bullet for deciding how much memory you need other than simply testing it. The [cluster performance metrics](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) in the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) can tell you if your cluster is sized appropriately. You can also [enable deployment monitoring](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) for more detailed performance metrics. Fortunately, you can change the amount of memory allocated to the cluster later without any downtime for HA deployments. To change a cluster’s topology, from deployment management, select **Edit deployment** from the **Actions** dropdown. Next, select a storage and RAM setting from the **Size per zone** drop-down list, and save your changes. When downsizing the cluster, make sure to have enough resources to handle the current load, otherwise your cluster will be under stress. diff --git a/deploy-manage/deploy/elastic-cloud/ech-restrictions.md b/deploy-manage/deploy/elastic-cloud/ech-restrictions.md index 316c84efd..6c14ecf9b 100644 --- a/deploy-manage/deploy/elastic-cloud/ech-restrictions.md +++ b/deploy-manage/deploy/elastic-cloud/ech-restrictions.md @@ -19,7 +19,7 @@ When using Elasticsearch Add-On for Heroku, there are some limitations you shoul * [Regions and Availability Zones](#ech-regions-and-availability-zone) * [Known problems](#ech-known-problems) -For limitations related to logging and monitoring, check the [Restrictions and limitations](../../monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) section of the logging and monitoring page. +For limitations related to logging and monitoring, check the [Restrictions and limitations](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) section of the logging and monitoring page. Occasionally, we also publish information about [Known problems](#ech-known-problems) with our Elasticsearch Add-On for Heroku or the Elastic Stack. @@ -53,7 +53,7 @@ Generally, if a feature is shown as available in the [Elasticsearch Add-On for H * Elasticsearch plugins, are not enabled by default for security purposes. Please reach out to support if you would like to enable Elasticsearch plugins support on your account. * Some Elasticsearch plugins do not apply to Elasticsearch Add-On for Heroku. For example, you won’t ever need to change discovery, as Elasticsearch Add-On for Heroku handles how nodes discover one another. * In Elasticsearch 5.0 and later, site plugins are no longer supported. This change does not affect the site plugins Elasticsearch Add-On for Heroku might provide out of the box, such as Kopf or Head, since these site plugins are serviced by our proxies and not Elasticsearch itself. -* In Elasticsearch 5.0 and later, site plugins such as Kopf and Paramedic are no longer provided. We recommend that you use our [cluster performance metrics](../../monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md), [X-Pack monitoring features](../../monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) and Kibana’s (6.3+) [Index Management UI](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-mgmt.html) if you want more detailed information or perform index management actions. +* In Elasticsearch 5.0 and later, site plugins such as Kopf and Paramedic are no longer provided. We recommend that you use our [cluster performance metrics](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md), [X-Pack monitoring features](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) and Kibana’s (6.3+) [Index Management UI](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-mgmt.html) if you want more detailed information or perform index management actions. ## Private Link and SSO to Kibana URLs [ech-restrictions-traffic-filters-kibana-sso] diff --git a/deploy-manage/deploy/elastic-cloud/manage-deployments.md b/deploy-manage/deploy/elastic-cloud/manage-deployments.md index 2bf452927..735a8e32d 100644 --- a/deploy-manage/deploy/elastic-cloud/manage-deployments.md +++ b/deploy-manage/deploy/elastic-cloud/manage-deployments.md @@ -8,7 +8,7 @@ mapped_pages: Sometimes you might need to make changes to the entire deployment, a specific component, or just a single data tier. * Make adjustments to specific deployment components, such as an [Integrations Server](manage-integrations-server.md), [APM & Fleet Server](switch-from-apm-to-integrations-server-payload.md#ec-manage-apm-and-fleet), [Enterprise Search](https://www.elastic.co/guide/en/cloud/current/ec-enable-enterprise-search.html), [Watcher](../../../explore-analyze/alerts/watcher.md), or [Kibana](access-kibana.md#ec-enable-kibana2). -* [Enable logging and monitoring](../../monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) of the deployment performance. +* [Enable logging and monitoring](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) of the deployment performance. * [Disable a data tier](../../../manage-data/lifecycle/index-lifecycle-management.md). * [Restart](../../maintenance/start-stop-services/restart-cloud-hosted-deployment.md), [stop routing](../../maintenance/ece/start-stop-routing-requests.md), or [delete your deployment](../../uninstall/delete-a-cloud-deployment.md). * [Upgrade the Elastic Stack version](../../upgrade/deployment-or-cluster.md) for the deployment. diff --git a/deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md b/deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md index 50a541168..c238c7b68 100644 --- a/deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md +++ b/deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md @@ -21,7 +21,7 @@ When using Elasticsearch Service, there are some limitations you should be aware * [Regions and Availability Zones](#ec-regions-and-availability-zone) * [Known problems](#ec-known-problems) -For limitations related to logging and monitoring, check the [Restrictions and limitations](../../monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ec-restrictions-monitoring) section of the logging and monitoring page. +For limitations related to logging and monitoring, check the [Restrictions and limitations](../../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-restrictions-monitoring) section of the logging and monitoring page. Occasionally, we also publish information about [Known problems](#ec-known-problems) with our Elasticsearch Service or the Elastic Stack. diff --git a/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md b/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md index 866d30463..1709caff0 100644 --- a/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md +++ b/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md @@ -12,7 +12,7 @@ applies: You can configure Stack monitoring alerts to be sent to you by email when health related events occur in your deployments. To set up email notifications: -1. [Enable logging and monitoring](../stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) on deployments for which you want to receive notifications. You need to enable only metrics data being shipped for the notifications to work. +1. [Enable logging and monitoring](../stack-monitoring/elastic-cloud-stack-monitoring.md) on deployments for which you want to receive notifications. You need to enable only metrics data being shipped for the notifications to work. 2. In Kibana, configure the email connector to [send email from Elastic Cloud](https://www.elastic.co/guide/en/kibana/current/email-action-type.html#elasticcloud). If you want to use the preconfigured `Elastic-Cloud-SMTP` connector in Elastic Cloud, then you can skip this step. 3. From the Kibana main menu, go to **Stack Monitoring**. On this page you can find a summary of monitoring metrics for your deployment as well as any alerts. 4. Select **Enter setup mode**. diff --git a/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md b/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md index c4691c251..38cd37322 100644 --- a/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md +++ b/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md @@ -9,7 +9,7 @@ applies: Cluster performance metrics are available directly in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). The graphs on this page include a subset of Elasticsearch Service-specific performance metrics. -For advanced views or production monitoring, [enable logging and monitoring](../stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period. +For advanced views or production monitoring, [enable logging and monitoring](../stack-monitoring/elastic-cloud-stack-monitoring.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period. To access cluster performance metrics: @@ -32,7 +32,7 @@ The following metrics are available: Shows the maximum usage of the CPU resources assigned to your Elasticsearch cluster, as a percentage. CPU resources are relative to the size of your cluster, so that a cluster with 32GB of RAM gets assigned twice as many CPU resources as a cluster with 16GB of RAM. All clusters are guaranteed their share of CPU resources, as Elasticsearch Service infrastructure does not overcommit any resources. CPU credits permit boosting the performance of smaller clusters temporarily, so that CPU usage can exceed 100%. ::::{tip} -This chart reports the maximum CPU values over the sampling period. [Logs and Metrics](../stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) ingested into [Stack Monitoring](visualizing-monitoring-data.md)'s "CPU Usage" instead reflects the average CPU over the sampling period. Therefore, you should not expect the two graphs to look exactly the same. When investigating [CPU-related performance issues](../../../troubleshoot/monitoring/performance.md), you should default to [Stack Monitoring](visualizing-monitoring-data.md). +This chart reports the maximum CPU values over the sampling period. [Logs and Metrics](../stack-monitoring/elastic-cloud-stack-monitoring.md) ingested into [Stack Monitoring](visualizing-monitoring-data.md)'s "CPU Usage" instead reflects the average CPU over the sampling period. Therefore, you should not expect the two graphs to look exactly the same. When investigating [CPU-related performance issues](../../../troubleshoot/monitoring/performance.md), you should default to [Stack Monitoring](visualizing-monitoring-data.md). :::: diff --git a/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md b/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md index 59f50f661..e40859d1c 100644 --- a/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md +++ b/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md @@ -7,7 +7,7 @@ mapped_pages: # JVM memory pressure indicator [ech-memory-pressure] -In addition to the more detailed [cluster performance metrics](../stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md), the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) also includes a JVM memory pressure indicator for each node in your cluster. This indicator can help you to determine when you need to upgrade to a larger cluster. +In addition to the more detailed [cluster performance metrics](../stack-monitoring/elastic-cloud-stack-monitoring.md), the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) also includes a JVM memory pressure indicator for each node in your cluster. This indicator can help you to determine when you need to upgrade to a larger cluster. The percentage number used in the JVM memory pressure indicator is actually the fill rate of the old generation pool. For a detailed explanation of why this metric is used, check [Understanding Memory Pressure](https://www.elastic.co/blog/found-understanding-memory-pressure-indicator/). diff --git a/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md b/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md index bf0be6f54..850c8cf1c 100644 --- a/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md +++ b/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md @@ -9,7 +9,7 @@ mapped_pages: Cluster performance metrics are available directly in the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body). The graphs on this page include a subset of Elasticsearch Add-On for Heroku-specific performance metrics. -For advanced views or production monitoring, [enable logging and monitoring](../stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period. +For advanced views or production monitoring, [enable logging and monitoring](../stack-monitoring/elastic-cloud-stack-monitoring.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period. To access cluster performance metrics: diff --git a/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md b/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md index 2414e97ce..c2a69e58f 100644 --- a/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md +++ b/deploy-manage/monitor/orchestrators/ece-platform-monitoring.md @@ -12,7 +12,7 @@ Elastic Cloud Enterprise by default collects monitoring data for your installati * Logs for all core services that are a part of Elastic Cloud Enterprise and monitoring metrics for core Elastic Cloud Enterprise services, system processes on the host, and any third-party software * Logs and monitoring metrics for Elasticsearch clusters and for Kibana instances -These monitoring indices are collected in addition to the [monitoring you might have enabled for specific clusters](../stack-monitoring/enable-stack-monitoring-on-ece-deployments.md), which also provides monitoring metrics that you can access in Kibana (note that the `logging-and-metrics` deployment is used for monitoring data from system deployments only; for non-system deployments, monitoring data must be sent to a deployment other than `logging-and-metrics`). +These monitoring indices are collected in addition to the [monitoring you might have enabled for specific clusters](../stack-monitoring/ece-stack-monitoring.md), which also provides monitoring metrics that you can access in Kibana (note that the `logging-and-metrics` deployment is used for monitoring data from system deployments only; for non-system deployments, monitoring data must be sent to a deployment other than `logging-and-metrics`). In this section: diff --git a/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md b/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md index f95355ec3..d703bb6df 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md @@ -118,5 +118,5 @@ If you’re using {{agent}}, do not deploy {{filebeat}} for log collection. Inst If you want to use the **Monitoring** UI in {{kib}}, there must also be `.monitoring-*` indices. Those indices are generated when you collect metrics about {{stack}} products. For example, see [Collecting monitoring data with {{metricbeat}}](collecting-monitoring-data-with-metricbeat.md). :::: -10. [View the monitoring data in {{kib}}](monitoring-data.md). +10. [View the monitoring data in {{kib}}](kibana-monitoring-data.md). diff --git a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md index 14baada1f..0e4eb14bc 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md @@ -11,7 +11,7 @@ applies: # Collecting monitoring data with Elastic Agent [configuring-elastic-agent] -In 8.5 and later, you can use {{agent}} to collect data about {{es}} and ship it to the monitoring cluster, rather than [using {{metricbeat}}](collecting-monitoring-data-with-metricbeat.md) or routing it through exporters as described in [Legacy collection methods](legacy-collection-methods.md). +In 8.5 and later, you can use {{agent}} to collect data about {{es}} and ship it to the monitoring cluster, rather than [using {{metricbeat}}](collecting-monitoring-data-with-metricbeat.md) or routing it through exporters as described in [Legacy collection methods](es-legacy-collection-methods.md). ## Prerequisites [_prerequisites_11] @@ -51,4 +51,4 @@ To collect {{es}} monitoring data, add an {{es}} integration to an {{agent}} and 2. Follow the steps in the **Add agent** flyout to download, install, and enroll the {{agent}}. Make sure you choose the agent policy you created earlier. 9. Wait a minute or two until incoming data is confirmed. -10. [View the monitoring data in {{kib}}](monitoring-data.md). +10. [View the monitoring data in {{kib}}](kibana-monitoring-data.md). diff --git a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md index 7d981f75b..169cb0125 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md @@ -11,7 +11,7 @@ applies: # Collecting monitoring data with Metricbeat [configuring-metricbeat] -In 6.5 and later, you can use {{metricbeat}} to collect data about {{es}} and ship it to the monitoring cluster, rather than routing it through exporters as described in [Legacy collection methods](legacy-collection-methods.md). +In 6.5 and later, you can use {{metricbeat}} to collect data about {{es}} and ship it to the monitoring cluster, rather than routing it through exporters as described in [Legacy collection methods](es-legacy-collection-methods.md). Want to use {{agent}} instead? Refer to [Collecting monitoring data with {{agent}}](collecting-monitoring-data-with-elastic-agent.md). @@ -105,5 +105,5 @@ Want to use {{agent}} instead? Refer to [Collecting monitoring data with {{agent For more information about these configuration options, see [Configure the {{es}} output](https://www.elastic.co/guide/en/beats/metricbeat/current/elasticsearch-output.html). 6. [Start {{metricbeat}}](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-starting.html) on each node. -7. [View the monitoring data in {{kib}}](monitoring-data.md). +7. [View the monitoring data in {{kib}}](kibana-monitoring-data.md). diff --git a/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md b/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md similarity index 96% rename from deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md rename to deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md index 5aed4cd0c..d88f253ef 100644 --- a/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md +++ b/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md @@ -55,7 +55,7 @@ When you enable monitoring in Elastic Cloud Enterprise, your monitoring indices $$$ece-logging-and-monitoring-retention-7$$$ When you enable self-monitoring in Elastic Cloud Enterprise, your monitoring indices are retained for a certain period by default. After the retention period has passed, the monitoring indices are deleted automatically. Monitoring data is retained for three days by default or as specified by the [`xpack.monitoring.history.duration` user setting](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-change-user-settings-examples.html#xpack-monitoring-history-duration). -To retain monitoring indices as is without deleting them automatically, you must disable the [cleaner service](local-exporter.md#local-exporter-cleaner) by adding a disabled local exporter in your cluster settings. +To retain monitoring indices as is without deleting them automatically, you must disable the [cleaner service](es-local-exporter.md#local-exporter-cleaner) by adding a disabled local exporter in your cluster settings. For example @@ -112,7 +112,7 @@ An ILM policy is pre-configured to manage log retention. The policy can be adjus ### Index management [ece-logging-and-monitoring-index-management-ilm] -When sending monitoring data to a deployment, you can configure [Index Lifecycle Management (ILM)](../../../manage-data/lifecycle/index-lifecycle-management.md) to manage retention of your monitoring and logging indices. When sending logs to a deployment, an ILM policy is pre-configured to manage log retention and the policy can be customized to your needs. +When sending monitoring data to a deployment, you can configure [Index Lifecycle Management (ILM)](../manage-data/lifecycle/index-lifecycle-management.md) to manage retention of your monitoring and logging indices. When sending logs to a deployment, an ILM policy is pre-configured to manage log retention and the policy can be customized to your needs. ### Enable logging and monitoring [ece-enable-logging-and-monitoring-steps] diff --git a/deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-eck-deployments.md b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md similarity index 100% rename from deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-eck-deployments.md rename to deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md diff --git a/deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md b/deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md similarity index 100% rename from deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md rename to deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md diff --git a/deploy-manage/monitor/stack-monitoring/http-exporter.md b/deploy-manage/monitor/stack-monitoring/es-http-exporter.md similarity index 100% rename from deploy-manage/monitor/stack-monitoring/http-exporter.md rename to deploy-manage/monitor/stack-monitoring/es-http-exporter.md diff --git a/deploy-manage/monitor/stack-monitoring/legacy-collection-methods.md b/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md similarity index 97% rename from deploy-manage/monitor/stack-monitoring/legacy-collection-methods.md rename to deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md index da5424284..ebc7019e6 100644 --- a/deploy-manage/monitor/stack-monitoring/legacy-collection-methods.md +++ b/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md @@ -76,7 +76,7 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). 2. Identify where to store monitoring data. - By default, the data is stored on the same cluster by using a [`local` exporter](local-exporter.md). Alternatively, you can use an [`http` exporter](http-exporter.md) to send data to a separate *monitoring cluster*. + By default, the data is stored on the same cluster by using a [`local` exporter](es-local-exporter.md). Alternatively, you can use an [`http` exporter](es-http-exporter.md) to send data to a separate *monitoring cluster*. ::::{important} The {{es}} {monitor-features} use ingest pipelines, therefore the cluster that stores the monitoring data must have at least one [ingest node](../../../manage-data/ingest/transform-enrich/ingest-pipelines.md). @@ -151,7 +151,7 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). :::: 6. Optional: [Configure the indices that store the monitoring data](../monitoring-data/configuring-data-streamsindices-for-monitoring.md). -7. [View the monitoring data in {{kib}}](monitoring-data.md). +7. [View the monitoring data in {{kib}}](kibana-monitoring-data.md). diff --git a/deploy-manage/monitor/stack-monitoring/local-exporter.md b/deploy-manage/monitor/stack-monitoring/es-local-exporter.md similarity index 100% rename from deploy-manage/monitor/stack-monitoring/local-exporter.md rename to deploy-manage/monitor/stack-monitoring/es-local-exporter.md diff --git a/deploy-manage/monitor/stack-monitoring/es-monitoring-exporters.md b/deploy-manage/monitor/stack-monitoring/es-monitoring-exporters.md index ddf003035..afaf502c4 100644 --- a/deploy-manage/monitor/stack-monitoring/es-monitoring-exporters.md +++ b/deploy-manage/monitor/stack-monitoring/es-monitoring-exporters.md @@ -20,10 +20,10 @@ The purpose of exporters is to take data collected from any Elastic Stack source There are two types of exporters in {{es}}: `local` -: The default exporter used by {{es}} {monitor-features}. This exporter routes data back into the *same* cluster. See [Local exporters](local-exporter.md). +: The default exporter used by {{es}} {monitor-features}. This exporter routes data back into the *same* cluster. See [Local exporters](es-local-exporter.md). `http` -: The preferred exporter, which you can use to route data into any supported {{es}} cluster accessible via HTTP. Production environments should always use a separate monitoring cluster. See [HTTP exporters](http-exporter.md). +: The preferred exporter, which you can use to route data into any supported {{es}} cluster accessible via HTTP. Production environments should always use a separate monitoring cluster. See [HTTP exporters](es-http-exporter.md). Both exporters serve the same purpose: to set up the monitoring cluster and route monitoring data. However, they perform these tasks in very different ways. Even though things happen differently, both exporters are capable of sending all of the same data. @@ -39,7 +39,7 @@ When the exporters route monitoring data into the monitoring cluster, they use ` Routing monitoring data involves indexing it into the appropriate monitoring indices. Once the data is indexed, it exists in a monitoring index that, by default, is named with a daily index pattern. For {{es}} monitoring data, this is an index that matches `.monitoring-es-6-*`. From there, the data lives inside the monitoring cluster and must be curated or cleaned up as necessary. If you do not curate the monitoring data, it eventually fills up the nodes and the cluster might fail due to lack of disk space. ::::{tip} -You are strongly recommended to manage the curation of indices and particularly the monitoring indices. To do so, you can take advantage of the [cleaner service](local-exporter.md#local-exporter-cleaner) or [Elastic Curator](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html). +You are strongly recommended to manage the curation of indices and particularly the monitoring indices. To do so, you can take advantage of the [cleaner service](es-local-exporter.md#local-exporter-cleaner) or [Elastic Curator](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html). :::: diff --git a/deploy-manage/monitor/stack-monitoring/pause-export.md b/deploy-manage/monitor/stack-monitoring/es-pause-export.md similarity index 100% rename from deploy-manage/monitor/stack-monitoring/pause-export.md rename to deploy-manage/monitor/stack-monitoring/es-pause-export.md diff --git a/deploy-manage/monitor/stack-monitoring/monitoring-data.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md similarity index 100% rename from deploy-manage/monitor/stack-monitoring/monitoring-data.md rename to deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md diff --git a/deploy-manage/monitor/stack-monitoring/monitoring-elastic-agent.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md similarity index 98% rename from deploy-manage/monitor/stack-monitoring/monitoring-elastic-agent.md rename to deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md index 190636cfd..7e2e61f3e 100644 --- a/deploy-manage/monitor/stack-monitoring/monitoring-elastic-agent.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md @@ -11,7 +11,7 @@ applies: # Collect monitoring data with Elastic Agent [monitoring-elastic-agent] -In 8.5 and later, you can use {{agent}} to collect data about {{kib}} and ship it to the monitoring cluster, rather than [using {{metricbeat}}](monitoring-metricbeat.md) or routing data through the production cluster as described in [Legacy collection methods](monitoring-kibana.md). +In 8.5 and later, you can use {{agent}} to collect data about {{kib}} and ship it to the monitoring cluster, rather than [using {{metricbeat}}](monitoring-metricbeat.md) or routing data through the production cluster as described in [Legacy collection methods](kibana-monitoring-legacy.md). To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). diff --git a/deploy-manage/monitor/stack-monitoring/monitoring-kibana.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md similarity index 95% rename from deploy-manage/monitor/stack-monitoring/monitoring-kibana.md rename to deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md index dbc9be5d2..a4f5a0ce9 100644 --- a/deploy-manage/monitor/stack-monitoring/monitoring-kibana.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md @@ -19,7 +19,7 @@ If you enable the Elastic {{monitor-features}} in your cluster, you can optional If you have previously configured legacy collection methods, you should migrate to using {{agent}} or {{metricbeat}} collection. Do not use legacy collection alongside other collection methods. -For more information, refer to [Collect monitoring data with {{agent}}](monitoring-elastic-agent.md) and [Collect monitoring data with {{metricbeat}}](monitoring-metricbeat.md). +For more information, refer to [Collect monitoring data with {{agent}}](kibana-monitoring-elastic-agent.md) and [Collect monitoring data with {{metricbeat}}](kibana-monitoring-metricbeat.md). :::: @@ -78,5 +78,5 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). 2. [Configure encryption for traffic between {{kib}} and {{es}}](https://www.elastic.co/guide/en/kibana/current/configuring-tls.html#configuring-tls-kib-es). 5. [Start {{kib}}](../../maintenance/start-stop-services/start-stop-kibana.md). -6. [View the monitoring data in {{kib}}](monitoring-data.md). +6. [View the monitoring data in {{kib}}](kibana-monitoring-data.md). diff --git a/deploy-manage/monitor/stack-monitoring/monitoring-metricbeat.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md similarity index 99% rename from deploy-manage/monitor/stack-monitoring/monitoring-metricbeat.md rename to deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md index 3025cfb13..18cdaabf9 100644 --- a/deploy-manage/monitor/stack-monitoring/monitoring-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md @@ -11,7 +11,7 @@ applies: # Collect monitoring data with Metricbeat [monitoring-metricbeat] -In 6.4 and later, you can use {{metricbeat}} to collect data about {{kib}} and ship it to the monitoring cluster, rather than routing it through the production cluster as described in [Legacy collection methods](monitoring-kibana.md). +In 6.4 and later, you can use {{metricbeat}} to collect data about {{kib}} and ship it to the monitoring cluster, rather than routing it through the production cluster as described in [Legacy collection methods](kibana-monitoring-legacy.md). :::{image} ../../../images/kibana-metricbeat.png :alt: Example monitoring architecture diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md index ae4992594..fb34b6135 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md @@ -13,11 +13,11 @@ applies: If you enable the {{monitor-features}} in your cluster, there are a few methods available to collect metrics about {{kib}}: -* [{{agent}} collection](monitoring-elastic-agent.md): Uses a single agent to gather logs and metrics. Can be managed from a central location in {{fleet}}. -* [{{metricbeat}} collection](monitoring-metricbeat.md): Uses a lightweight {{beats}} shipper to gather metrics. May be preferred if you have an existing investment in {{beats}} or are not yet ready to use {{agent}}. -* [Legacy collection](monitoring-kibana.md): Uses internal collectors to gather metrics. Not recommended. If you have previously configured legacy collection methods, you should migrate to using {{agent}} or {{metricbeat}}. +* [{{agent}} collection](kibana-monitoring-elastic-agent.md): Uses a single agent to gather logs and metrics. Can be managed from a central location in {{fleet}}. +* [{{metricbeat}} collection](kibana-monitoring-metricbeat.md): Uses a lightweight {{beats}} shipper to gather metrics. May be preferred if you have an existing investment in {{beats}} or are not yet ready to use {{agent}}. +* [Legacy collection](kibana-monitoring-legacy.md): Uses internal collectors to gather metrics. Not recommended. If you have previously configured legacy collection methods, you should migrate to using {{agent}} or {{metricbeat}}. -You can also use {{kib}} to [visualize monitoring data from across the {{stack}}](monitoring-data.md). +You can also use {{kib}} to [visualize monitoring data from across the {{stack}}](kibana-monitoring-data.md). To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index 66a6f7a5b..db6933705 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -705,15 +705,15 @@ toc: - file: monitor/autoops/ec-autoops-faq.md - file: monitor/stack-monitoring.md children: - - file: monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md - - file: monitor/stack-monitoring/enable-stack-monitoring-on-eck-deployments.md + - file: monitor/stack-monitoring/elastic-cloud-stack-monitoring.md + - file: monitor/stack-monitoring/eck-stack-monitoring.md children: - file: monitor/stack-monitoring/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.md - file: monitor/stack-monitoring/k8s_when_to_use_it.md - file: monitor/stack-monitoring/k8s_how_it_works.md - file: monitor/stack-monitoring/k8s_audit_logging.md - file: monitor/stack-monitoring/k8s_override_the_beats_pod_template.md - - file: monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md + - file: monitor/stack-monitoring/ece-stack-monitoring.md children: - file: monitor/stack-monitoring/ece-restrictions-monitoring.md - file: monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md @@ -721,19 +721,19 @@ toc: - file: monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md - file: monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md - file: monitor/stack-monitoring/collecting-log-data-with-filebeat.md - - file: monitor/stack-monitoring/legacy-collection-methods.md + - file: monitor/stack-monitoring/es-legacy-collection-methods.md children: - file: monitor/stack-monitoring/es-monitoring-collectors.md - file: monitor/stack-monitoring/es-monitoring-exporters.md - - file: monitor/stack-monitoring/local-exporter.md - - file: monitor/stack-monitoring/http-exporter.md - - file: monitor/stack-monitoring/pause-export.md + - file: monitor/stack-monitoring/es-local-exporter.md + - file: monitor/stack-monitoring/es-http-exporter.md + - file: monitor/stack-monitoring/es-pause-export.md - file: monitor/stack-monitoring/kibana-monitoring-self-managed.md children: - - file: monitor/stack-monitoring/monitoring-elastic-agent.md - - file: monitor/stack-monitoring/monitoring-metricbeat.md - - file: monitor/stack-monitoring/monitoring-data.md - - file: monitor/stack-monitoring/monitoring-kibana.md + - file: monitor/stack-monitoring/kibana-monitoring-elastic-agent.md + - file: monitor/stack-monitoring/kibana-monitoring-metricbeat.md + - file: monitor/stack-monitoring/kibana-monitoring-data.md + - file: monitor/stack-monitoring/kibana-monitoring-legacy.md - file: monitor/orchestrators.md children: - file: monitor/orchestrators/eck-metrics-configuration.md diff --git a/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md b/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md index 91c55f16e..68097cad4 100644 --- a/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md +++ b/deploy-manage/users-roles/cloud-enterprise-orchestrator/manage-users-roles.md @@ -62,7 +62,7 @@ We strongly recommend using three availability zones with at least 1 GB Elastics 1. [Log into the Cloud UI](../../deploy/cloud-enterprise/log-into-cloud-ui.md). 2. Go to **Deployments** a select the **security-cluster**. 3. Configure regular snapshots of the security deployment. This is critical if you plan to create any native users. -4. Optional: [Enable monitoring](../../monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md) on the security deployment to a dedicated monitoring deployment. +4. Optional: [Enable monitoring](../../monitor/stack-monitoring/ece-stack-monitoring.md) on the security deployment to a dedicated monitoring deployment. If you have authentication issues, you check out the security deployment Elasticsearch logs. diff --git a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-advanced-topics.md b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-advanced-topics.md index 81570d702..227a31684 100644 --- a/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-advanced-topics.md +++ b/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-advanced-topics.md @@ -7,6 +7,6 @@ * [*Traffic Splitting*](../../../deploy-manage/deploy/cloud-on-k8s/requests-routing-to-elasticsearch-nodes.md) * [*Network policies*](../../../deploy-manage/deploy/cloud-on-k8s/network-policies.md) * [*Webhook namespace selectors*](../../../deploy-manage/deploy/cloud-on-k8s/webhook-namespace-selectors.md) -* [*Stack Monitoring*](../../../deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-eck-deployments.md) +* [*Stack Monitoring*](../../../deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md) * [*Deploy a FIPS compatible version of ECK*](../../../deploy-manage/deploy/cloud-on-k8s/deploy-fips-compatible-version-of-eck.md) diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-monitoring-deployments.md b/raw-migrated-files/cloud/cloud-enterprise/ece-monitoring-deployments.md index a9a365cd7..023d560f6 100644 --- a/raw-migrated-files/cloud/cloud-enterprise/ece-monitoring-deployments.md +++ b/raw-migrated-files/cloud/cloud-enterprise/ece-monitoring-deployments.md @@ -4,7 +4,7 @@ Elastic Cloud Enterprise monitors many aspects of your installation, but some is * [Find clusters](../../../troubleshoot/deployments/cloud-enterprise/finding-deployments-finding-problems.md) that have issues. * [Move affected nodes off an allocator](../../../deploy-manage/maintenance/ece/move-nodes-instances-from-allocators.md), if the allocator fails. -* [Enable deployment logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/enable-stack-monitoring-on-ece-deployments.md) to keep an eye on the performance of deployments and debug stack and solution issues. +* [Enable deployment logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md) to keep an eye on the performance of deployments and debug stack and solution issues. In addition to the monitoring of clusters that is described here, don’t forget that Elastic Cloud Enterprise also provides [monitoring information for your entire installation](../../../deploy-manage/monitor/orchestrators/ece-platform-monitoring.md). You can you also monitor the physical hosts machines on which Elastic Cloud Enterprise is installed. diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-add-user-settings.md b/raw-migrated-files/cloud/cloud-heroku/ech-add-user-settings.md index 9e47a524c..1d18b41e1 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-add-user-settings.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-add-user-settings.md @@ -275,7 +275,7 @@ The following audit settings are supported: : A list of action names or wildcards. The specified policy will not print audit events for actions matching these values. ::::{note} -To enable auditing you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). +To enable auditing you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). :::: diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-config-change-errors.md b/raw-migrated-files/cloud/cloud-heroku/ech-config-change-errors.md index 43954439a..f76354758 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-config-change-errors.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-config-change-errors.md @@ -6,7 +6,7 @@ When you attempt to apply a configuration change to a deployment, the attempt ma :alt: A screen capture of the deployment page showing an error: Latest change to {{es}} configuration failed. ::: -To help diagnose these and any other types of issues in your deployments, we recommend [setting up monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). Then, you can easily view your deployment health and access log files to troubleshoot this configuration failure. +To help diagnose these and any other types of issues in your deployments, we recommend [setting up monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). Then, you can easily view your deployment health and access log files to troubleshoot this configuration failure. To confirm if your Elasticsearch cluster is bootlooping, you can check the most recent plan under your [Deployment Activity page](../../../deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md) for the error: diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-configure.md b/raw-migrated-files/cloud/cloud-heroku/ech-configure.md index 983733279..87dadfc13 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-configure.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-configure.md @@ -5,7 +5,7 @@ The information in this section covers: * [Plan for production](../../../deploy-manage/production-guidance/plan-for-production-elastic-cloud.md) - Plan for a highly available and scalable deployment. * [Configure your deployment](../../../deploy-manage/deploy/elastic-cloud/ech-configure-settings.md) - Customize your cluster through a full list of settings. * [Enable Kibana](../../../deploy-manage/deploy/elastic-cloud/access-kibana.md) - Explore your data with the Elastic Stack visualization platform. -* [Enable Logging and Monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) - Monitor your cluster’s health and performance and ingest your deployment’s logs. +* [Enable Logging and Monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) - Monitor your cluster’s health and performance and ingest your deployment’s logs. * [Upgrade versions](../../../deploy-manage/upgrade/deployment-or-cluster.md) - Stay current with the latest Elastic Stack versions. * [Delete your deployment](../../../deploy-manage/uninstall/delete-a-cloud-deployment.md) - No undo. Data is lost and billing stops. diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-enable-logging-and-monitoring.md b/raw-migrated-files/cloud/cloud-heroku/ech-enable-logging-and-monitoring.md index c1132d338..6dc86b960 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-enable-logging-and-monitoring.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-enable-logging-and-monitoring.md @@ -15,7 +15,7 @@ The steps in this section cover only the enablement of the monitoring and loggin ### Before you begin [ech-logging-and-monitoring-limitations] -Some limitations apply when you use monitoring on Elasticsearch Add-On for Heroku. To learn more, check the monitoring [restrictions and limitations](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). +Some limitations apply when you use monitoring on Elasticsearch Add-On for Heroku. To learn more, check the monitoring [restrictions and limitations](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). ### Monitoring for production use [ech-logging-and-monitoring-production] @@ -32,7 +32,7 @@ How many monitoring deployments you use depends on your requirements: * If you need to silo {{es}} data for different business departments. Deployments that have been configured to ship logs and metrics to a target monitoring deployment have access to indexing data and can manage monitoring index templates, which is addressed by creating separate monitoring deployments. -Logs and metrics that get sent to a dedicated monitoring {{es}} deployment [may not be cleaned up automatically](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-logging-and-monitoring-retention) and might require some additional steps to remove excess data periodically. +Logs and metrics that get sent to a dedicated monitoring {{es}} deployment [may not be cleaned up automatically](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-logging-and-monitoring-retention) and might require some additional steps to remove excess data periodically. ### Retention of monitoring daily indices [ech-logging-and-monitoring-retention] @@ -48,7 +48,7 @@ When you enable monitoring in Elasticsearch Add-On for Heroku, your monitoring i $$$ech-logging-and-monitoring-retention-7$$$ When you enable self-monitoring in Elasticsearch Add-On for Heroku, your monitoring indices are retained for a certain period by default. After the retention period has passed, the monitoring indices are deleted automatically. Monitoring data is retained for three days by default or as specified by the [`xpack.monitoring.history.duration` user setting](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md#xpack-monitoring-history-duration). -To retain monitoring indices as is without deleting them automatically, you must disable the [cleaner service](../../../deploy-manage/monitor/stack-monitoring/local-exporter.md#local-exporter-cleaner) by adding a disabled local exporter in your cluster settings. +To retain monitoring indices as is without deleting them automatically, you must disable the [cleaner service](../../../deploy-manage/monitor/stack-monitoring/es-local-exporter.md#local-exporter-cleaner) by adding a disabled local exporter in your cluster settings. For example @@ -67,9 +67,9 @@ PUT /_cluster/settings ### Sending monitoring data to a dedicated monitoring deployment [ech-logging-and-monitoring-retention-dedicated-monitoring] -When [monitoring for production use](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-logging-and-monitoring-production), where you configure your deployments **to send monitoring data to a dedicated monitoring deployment** for indexing, this retention period does not apply. Monitoring indices on a dedicated monitoring deployment are retained until you remove them. There are three options open to you: +When [monitoring for production use](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-logging-and-monitoring-production), where you configure your deployments **to send monitoring data to a dedicated monitoring deployment** for indexing, this retention period does not apply. Monitoring indices on a dedicated monitoring deployment are retained until you remove them. There are three options open to you: -* To enable the automatic deletion of monitoring indices from dedicated monitoring deployments, [enable monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-enable-logging-and-monitoring-steps) on your dedicated monitoring deployment in Elasticsearch Add-On for Heroku to send monitoring data to itself. When an {{es}} deployment sends monitoring data to itself, all monitoring indices are deleted automatically after the retention period, regardless of the origin of the monitoring data. +* To enable the automatic deletion of monitoring indices from dedicated monitoring deployments, [enable monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-enable-logging-and-monitoring-steps) on your dedicated monitoring deployment in Elasticsearch Add-On for Heroku to send monitoring data to itself. When an {{es}} deployment sends monitoring data to itself, all monitoring indices are deleted automatically after the retention period, regardless of the origin of the monitoring data. * Alternatively, you can enable the cleaner service on the monitoring deployment by creating a local exporter. You can define the retention period at the same time. For example diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md b/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md index ef8af03c9..8c60608b7 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md @@ -361,7 +361,7 @@ Allow anonymous access only for specified agents and/or services. This is primar : The period after which to log the internal metrics. Defaults to *30s*. ::::{note} -To change logging settings you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). +To change logging settings you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). :::: diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-manage-kibana-settings.md b/raw-migrated-files/cloud/cloud-heroku/ech-manage-kibana-settings.md index 265c07d36..d1530f630 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-manage-kibana-settings.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-manage-kibana-settings.md @@ -784,7 +784,7 @@ If search latency in {{es}} is sufficiently high, such as if you are using cross ## Logging and audit settings [echlogging_and_audit_settings] ::::{note} -To change logging settings or to enable auditing you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). +To change logging settings or to enable auditing you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). :::: diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring-setup.md b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring-setup.md index 2e5da2114..45e26e29a 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring-setup.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring-setup.md @@ -22,7 +22,7 @@ After you have created a new deployment, you should enable shipping logs and met 4. Choose where to send your logs and metrics. ::::{important} - Anything used for production should go to a separate deployment you create only for monitoring. For development or testing, you can send monitoring data to the same deployment. Check [Enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-logging-and-monitoring-production). + Anything used for production should go to a separate deployment you create only for monitoring. For development or testing, you can send monitoring data to the same deployment. Check [Enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-logging-and-monitoring-production). :::: 5. Select **Save**. diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md index 93c9d77dc..b727868df 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md @@ -8,12 +8,12 @@ The most important of these is the {{es}} cluster, because it is the heart of th This section provides some best practices to help you monitor and understand the ongoing state of your deployments and their resources. -* [{{es}} cluster health](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-es-cluster-health) -* [{{es}} cluster performance](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-es-cluster-performance) -* [Health warnings](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-es-health-warnings) -* [Preconfigured logs and metrics](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-es-health-preconfigured) -* [Dedicated logs and metrics](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-es-health-dedicated) -* [Understanding deployment health](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-health-best-practices) +* [{{es}} cluster health](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-es-cluster-health) +* [{{es}} cluster performance](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-es-cluster-performance) +* [Health warnings](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-es-health-warnings) +* [Preconfigured logs and metrics](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-es-health-preconfigured) +* [Dedicated logs and metrics](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-es-health-dedicated) +* [Understanding deployment health](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-health-best-practices) ## {{es}} cluster health [ech-es-cluster-health] @@ -56,7 +56,7 @@ For each issue you can either use a troubleshooting link or get a suggestion to ## {{es}} cluster performance [ech-es-cluster-performance] -The deployment **Health** page does not include information on cluster performance. If you observe issues on search and ingest operations in terms of increased latency or throughput for queries, these might not be directly reported on the **Health** page, unless they are related to shard health or master node availability. The performance page and the out-of-the-box logs allow you to monitor your cluster performance, but for production applications we strongly recommend setting up a dedicated monitoring cluster. Check [Understanding deployment health](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ech-health-best-practices), for more guidelines on how to monitor you cluster performance. +The deployment **Health** page does not include information on cluster performance. If you observe issues on search and ingest operations in terms of increased latency or throughput for queries, these might not be directly reported on the **Health** page, unless they are related to shard health or master node availability. The performance page and the out-of-the-box logs allow you to monitor your cluster performance, but for production applications we strongly recommend setting up a dedicated monitoring cluster. Check [Understanding deployment health](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ech-health-best-practices), for more guidelines on how to monitor you cluster performance. ## Health warnings [ech-es-health-warnings] @@ -94,7 +94,7 @@ In a production environment, it’s important set up dedicated health monitoring You have the option of sending logs and metrics to a separate, specialized monitoring deployment, which ensures that they’re available in the event of a deployment outage. The monitoring deployment also gives you access to Kibana’s stack monitoring features, through which you can view health and performance data for all of your deployment resources. -Check the guide on [how to set up monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) to learn more. +Check the guide on [how to set up monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) to learn more. ## Understanding deployment health [ech-health-best-practices] diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md b/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md index d71b5a9a4..57d0f3f5c 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md @@ -2,7 +2,7 @@ Cluster performance metrics are available directly in the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body). The graphs on this page include a subset of Elasticsearch Add-On for Heroku-specific performance metrics. -For advanced views or production monitoring, [enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period. +For advanced views or production monitoring, [enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period. To access cluster performance metrics: diff --git a/raw-migrated-files/cloud/cloud-heroku/echscenario_why_is_my_node_unavailable.md b/raw-migrated-files/cloud/cloud-heroku/echscenario_why_is_my_node_unavailable.md index baa9f6601..dc76eadea 100644 --- a/raw-migrated-files/cloud/cloud-heroku/echscenario_why_is_my_node_unavailable.md +++ b/raw-migrated-files/cloud/cloud-heroku/echscenario_why_is_my_node_unavailable.md @@ -1,6 +1,6 @@ # Diagnose unavailable nodes [echscenario_why_is_my_node_unavailable] -This section provides a list of common symptoms and possible actions that you can take to resolve issues when one or more nodes become unhealthy or unavailable. This guide is particularly useful if you are not [shipping your logs and metrics](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) to a dedicated monitoring cluster. +This section provides a list of common symptoms and possible actions that you can take to resolve issues when one or more nodes become unhealthy or unavailable. This guide is particularly useful if you are not [shipping your logs and metrics](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) to a dedicated monitoring cluster. **What are the symptoms?** diff --git a/raw-migrated-files/cloud/cloud/ec-add-user-settings.md b/raw-migrated-files/cloud/cloud/ec-add-user-settings.md index c8db3ae68..2a9c70422 100644 --- a/raw-migrated-files/cloud/cloud/ec-add-user-settings.md +++ b/raw-migrated-files/cloud/cloud/ec-add-user-settings.md @@ -275,7 +275,7 @@ The following audit settings are supported: : A list of action names or wildcards. The specified policy will not print audit events for actions matching these values. ::::{note} -To enable auditing you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). +To enable auditing you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). :::: diff --git a/raw-migrated-files/cloud/cloud/ec-config-change-errors.md b/raw-migrated-files/cloud/cloud/ec-config-change-errors.md index 6cc173b76..2edce8d83 100644 --- a/raw-migrated-files/cloud/cloud/ec-config-change-errors.md +++ b/raw-migrated-files/cloud/cloud/ec-config-change-errors.md @@ -6,7 +6,7 @@ When you attempt to apply a configuration change to a deployment, the attempt ma :alt: A screen capture of the deployment page showing an error: Latest change to {{es}} configuration failed. ::: -To help diagnose these and any other types of issues in your deployments, we recommend [setting up monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). Then, you can easily view your deployment health and access log files to troubleshoot this configuration failure. +To help diagnose these and any other types of issues in your deployments, we recommend [setting up monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). Then, you can easily view your deployment health and access log files to troubleshoot this configuration failure. To confirm if your Elasticsearch cluster is bootlooping, you can check the most recent plan under your [Deployment Activity page](../../../deploy-manage/deploy/elastic-cloud/keep-track-of-deployment-activity.md) for the error: diff --git a/raw-migrated-files/cloud/cloud/ec-enable-logging-and-monitoring.md b/raw-migrated-files/cloud/cloud/ec-enable-logging-and-monitoring.md index ffe0d7002..f30761a88 100644 --- a/raw-migrated-files/cloud/cloud/ec-enable-logging-and-monitoring.md +++ b/raw-migrated-files/cloud/cloud/ec-enable-logging-and-monitoring.md @@ -15,7 +15,7 @@ The steps in this section cover only the enablement of the monitoring and loggin ### Before you begin [ec-logging-and-monitoring-limitations] -Some limitations apply when you use monitoring on Elasticsearch Service. To learn more, check the monitoring [restrictions and limitations](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ec-restrictions-monitoring). +Some limitations apply when you use monitoring on Elasticsearch Service. To learn more, check the monitoring [restrictions and limitations](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-restrictions-monitoring). ### Monitoring for production use [ec-logging-and-monitoring-production] @@ -32,7 +32,7 @@ How many monitoring deployments you use depends on your requirements: * If you need to silo {{es}} data for different business departments. Deployments that have been configured to ship logs and metrics to a target monitoring deployment have access to indexing data and can manage monitoring index templates, which is addressed by creating separate monitoring deployments. -Logs and metrics that get sent to a dedicated monitoring {{es}} deployment [may not be cleaned up automatically](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ec-logging-and-monitoring-retention) and might require some additional steps to remove excess data periodically. +Logs and metrics that get sent to a dedicated monitoring {{es}} deployment [may not be cleaned up automatically](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-logging-and-monitoring-retention) and might require some additional steps to remove excess data periodically. ### Retention of monitoring daily indices [ec-logging-and-monitoring-retention] @@ -48,7 +48,7 @@ When you enable monitoring in Elasticsearch Service, your monitoring indices are $$$ec-logging-and-monitoring-retention-7$$$ When you enable self-monitoring in Elasticsearch Service, your monitoring indices are retained for a certain period by default. After the retention period has passed, the monitoring indices are deleted automatically. Monitoring data is retained for three days by default or as specified by the [`xpack.monitoring.history.duration` user setting](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md#xpack-monitoring-history-duration). -To retain monitoring indices as is without deleting them automatically, you must disable the [cleaner service](../../../deploy-manage/monitor/stack-monitoring/local-exporter.md#local-exporter-cleaner) by adding a disabled local exporter in your cluster settings. +To retain monitoring indices as is without deleting them automatically, you must disable the [cleaner service](../../../deploy-manage/monitor/stack-monitoring/es-local-exporter.md#local-exporter-cleaner) by adding a disabled local exporter in your cluster settings. For example @@ -67,9 +67,9 @@ PUT /_cluster/settings ### Sending monitoring data to a dedicated monitoring deployment [ec-logging-and-monitoring-retention-dedicated-monitoring] -When [monitoring for production use](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ec-logging-and-monitoring-production), where you configure your deployments **to send monitoring data to a dedicated monitoring deployment** for indexing, this retention period does not apply. Monitoring indices on a dedicated monitoring deployment are retained until you remove them. There are three options open to you: +When [monitoring for production use](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-logging-and-monitoring-production), where you configure your deployments **to send monitoring data to a dedicated monitoring deployment** for indexing, this retention period does not apply. Monitoring indices on a dedicated monitoring deployment are retained until you remove them. There are three options open to you: -* To enable the automatic deletion of monitoring indices from dedicated monitoring deployments, [enable monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ec-enable-logging-and-monitoring-steps) on your dedicated monitoring deployment in Elasticsearch Service to send monitoring data to itself. When an {{es}} deployment sends monitoring data to itself, all monitoring indices are deleted automatically after the retention period, regardless of the origin of the monitoring data. +* To enable the automatic deletion of monitoring indices from dedicated monitoring deployments, [enable monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-enable-logging-and-monitoring-steps) on your dedicated monitoring deployment in Elasticsearch Service to send monitoring data to itself. When an {{es}} deployment sends monitoring data to itself, all monitoring indices are deleted automatically after the retention period, regardless of the origin of the monitoring data. * Alternatively, you can enable the cleaner service on the monitoring deployment by creating a local exporter. You can define the retention period at the same time. For example diff --git a/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md b/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md index 3833f6291..482d9bc59 100644 --- a/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md +++ b/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md @@ -361,7 +361,7 @@ Allow anonymous access only for specified agents and/or services. This is primar : The period after which to log the internal metrics. Defaults to *30s*. ::::{note} -To change logging settings you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). +To change logging settings you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). :::: diff --git a/raw-migrated-files/cloud/cloud/ec-manage-kibana-settings.md b/raw-migrated-files/cloud/cloud/ec-manage-kibana-settings.md index dd71202fa..3b52d8ee2 100644 --- a/raw-migrated-files/cloud/cloud/ec-manage-kibana-settings.md +++ b/raw-migrated-files/cloud/cloud/ec-manage-kibana-settings.md @@ -784,7 +784,7 @@ If search latency in {{es}} is sufficiently high, such as if you are using cross ## Logging and audit settings [ec_logging_and_audit_settings] ::::{note} -To change logging settings or to enable auditing you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). +To change logging settings or to enable auditing you must first [enable deployment logging](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). :::: diff --git a/raw-migrated-files/cloud/cloud/ec-monitoring-setup.md b/raw-migrated-files/cloud/cloud/ec-monitoring-setup.md index 5819719d6..2f2b33093 100644 --- a/raw-migrated-files/cloud/cloud/ec-monitoring-setup.md +++ b/raw-migrated-files/cloud/cloud/ec-monitoring-setup.md @@ -22,7 +22,7 @@ After you have created a new deployment, you should enable shipping logs and met 4. Choose where to send your logs and metrics. ::::{important} - Anything used for production should go to a separate deployment you create only for monitoring. For development or testing, you can send monitoring data to the same deployment. Check [Enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ec-logging-and-monitoring-production). + Anything used for production should go to a separate deployment you create only for monitoring. For development or testing, you can send monitoring data to the same deployment. Check [Enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-logging-and-monitoring-production). :::: 5. Select **Save**. diff --git a/raw-migrated-files/cloud/cloud/ec-monitoring.md b/raw-migrated-files/cloud/cloud/ec-monitoring.md index 278689b8d..76408e7f8 100644 --- a/raw-migrated-files/cloud/cloud/ec-monitoring.md +++ b/raw-migrated-files/cloud/cloud/ec-monitoring.md @@ -102,7 +102,7 @@ You have the option of sending logs and metrics to a separate, specialized monit As part of health monitoring, it’s also a best practice to [configure alerting](../../../deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md), so that you can be notified right away about any deployment health issues. -Check the guide on [how to set up monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) to learn more. +Check the guide on [how to set up monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) to learn more. ## Understanding deployment health [ec-health-best-practices] diff --git a/raw-migrated-files/cloud/cloud/ec-prepare-production.md b/raw-migrated-files/cloud/cloud/ec-prepare-production.md index 838d72f4d..00c9d4226 100644 --- a/raw-migrated-files/cloud/cloud/ec-prepare-production.md +++ b/raw-migrated-files/cloud/cloud/ec-prepare-production.md @@ -8,5 +8,5 @@ To make sure you’re all set for production, consider the following actions: * [Add extensions and plugins](../../../deploy-manage/deploy/elastic-cloud/add-plugins-extensions.md) to use Elastic supported extensions or add your own custom dictionaries and scripts. * [Edit settings and defaults](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md) to fine tune the performance of specific features. * [Manage your deployment](../../../deploy-manage/deploy/elastic-cloud/manage-deployments.md) as a whole to restart, upgrade, stop routing, or delete. -* [Set up monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) to learn how to configure your deployments for observability, which includes metric and log collection, troubleshooting views, and cluster alerts to automate performance monitoring. +* [Set up monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) to learn how to configure your deployments for observability, which includes metric and log collection, troubleshooting views, and cluster alerts to automate performance monitoring. diff --git a/raw-migrated-files/cloud/cloud/ec-saas-metrics-accessing.md b/raw-migrated-files/cloud/cloud/ec-saas-metrics-accessing.md index 3f47b0edb..8b5743c35 100644 --- a/raw-migrated-files/cloud/cloud/ec-saas-metrics-accessing.md +++ b/raw-migrated-files/cloud/cloud/ec-saas-metrics-accessing.md @@ -2,7 +2,7 @@ Cluster performance metrics are available directly in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). The graphs on this page include a subset of Elasticsearch Service-specific performance metrics. -For advanced views or production monitoring, [enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period. +For advanced views or production monitoring, [enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period. To access cluster performance metrics: @@ -25,7 +25,7 @@ The following metrics are available: Shows the maximum usage of the CPU resources assigned to your Elasticsearch cluster, as a percentage. CPU resources are relative to the size of your cluster, so that a cluster with 32GB of RAM gets assigned twice as many CPU resources as a cluster with 16GB of RAM. All clusters are guaranteed their share of CPU resources, as Elasticsearch Service infrastructure does not overcommit any resources. CPU credits permit boosting the performance of smaller clusters temporarily, so that CPU usage can exceed 100%. ::::{tip} -This chart reports the maximum CPU values over the sampling period. [Logs and Metrics](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) ingested into [Stack Monitoring](../../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md)'s "CPU Usage" instead reflects the average CPU over the sampling period. Therefore, you should not expect the two graphs to look exactly the same. When investigating [CPU-related performance issues](../../../troubleshoot/monitoring/performance.md), you should default to [Stack Monitoring](../../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md). +This chart reports the maximum CPU values over the sampling period. [Logs and Metrics](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) ingested into [Stack Monitoring](../../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md)'s "CPU Usage" instead reflects the average CPU over the sampling period. Therefore, you should not expect the two graphs to look exactly the same. When investigating [CPU-related performance issues](../../../troubleshoot/monitoring/performance.md), you should default to [Stack Monitoring](../../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md). :::: diff --git a/raw-migrated-files/cloud/cloud/ec-scenario_why_are_shards_unavailable.md b/raw-migrated-files/cloud/cloud/ec-scenario_why_are_shards_unavailable.md index 79bc791da..8873bd0a6 100644 --- a/raw-migrated-files/cloud/cloud/ec-scenario_why_are_shards_unavailable.md +++ b/raw-migrated-files/cloud/cloud/ec-scenario_why_are_shards_unavailable.md @@ -150,7 +150,7 @@ The response is as follows: #### Check {{es}} cluster logs [ec-check-es-cluster-logs] -To determine the allocation issue, you can [check the logs](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md#ec-check-logs). This is easier if you have set up a dedicated monitoring deployment. +To determine the allocation issue, you can [check the logs](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md#ec-check-logs). This is easier if you have set up a dedicated monitoring deployment. ## Analyze unassigned shards using the Kibana UI [ec-analyze_shards_with-kibana] diff --git a/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md b/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md index aed231d01..e252e360d 100644 --- a/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md +++ b/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md @@ -1,6 +1,6 @@ # Diagnose unavailable nodes [ec-scenario_why_is_my_node_unavailable] -This section provides a list of common symptoms and possible actions that you can take to resolve issues when one or more nodes become unhealthy or unavailable. This guide is particularly useful if you are not [shipping your logs and metrics](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md) to a dedicated monitoring cluster. +This section provides a list of common symptoms and possible actions that you can take to resolve issues when one or more nodes become unhealthy or unavailable. This guide is particularly useful if you are not [shipping your logs and metrics](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md) to a dedicated monitoring cluster. **What are the symptoms?** diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md index 4ba7a71b8..eca7ff05a 100644 --- a/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md +++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md @@ -17,7 +17,7 @@ To learn how to collect monitoring data, refer to: * [Collecting monitoring data with {{agent}}](../../../deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md): Uses a single agent to gather logs and metrics. Can be managed from a central location in {{fleet}}. * [Collecting monitoring data with {{metricbeat}}](../../../deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md): Uses a lightweight {{beats}} shipper to gather metrics. May be preferred if you have an existing investment in {{beats}} or are not yet ready to use {{agent}}. - * [Legacy collection methods](../../../deploy-manage/monitor/stack-monitoring/legacy-collection-methods.md): Uses internal exporters to gather metrics. Not recommended. If you have previously configured legacy collection methods, you should migrate to using {{agent}} or {{metricbeat}}. + * [Legacy collection methods](../../../deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md): Uses internal exporters to gather metrics. Not recommended. If you have previously configured legacy collection methods, you should migrate to using {{agent}} or {{metricbeat}}. * [Monitoring {{kib}}](../../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md) * [Monitoring {{ls}}](https://www.elastic.co/guide/en/logstash/current/configuring-logstash.html) diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/monitor-elasticsearch-cluster.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/monitor-elasticsearch-cluster.md index 7489d0a26..55247fd47 100644 --- a/raw-migrated-files/elasticsearch/elasticsearch-reference/monitor-elasticsearch-cluster.md +++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/monitor-elasticsearch-cluster.md @@ -10,6 +10,6 @@ The {{stack}} {monitor-features} provide a way to keep a pulse on the health and * [Collecting monitoring data with {{metricbeat}}](../../../deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md) * [Collecting log data with {{filebeat}}](../../../deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md) * [*Configuring data streams/indices for monitoring*](../../../deploy-manage/monitor/monitoring-data/configuring-data-streamsindices-for-monitoring.md) -* [Legacy collection methods](../../../deploy-manage/monitor/stack-monitoring/legacy-collection-methods.md) +* [Legacy collection methods](../../../deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md) * [*Troubleshooting monitoring*](../../../troubleshoot/elasticsearch/monitoring-troubleshooting.md) diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md index 614576d6e..32129be86 100644 --- a/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md +++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md @@ -66,7 +66,7 @@ To store monitoring data in a separate cluster: * [{{agent}} collection methods](../../../deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md) * [{{metricbeat}} collection methods](../../../deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md) - * [Legacy collection methods](../../../deploy-manage/monitor/stack-monitoring/legacy-collection-methods.md) + * [Legacy collection methods](../../../deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md) 3. (Optional) [Configure {{ls}} to collect data and send it to the monitoring cluster](https://www.elastic.co/guide/en/logstash/current/configuring-logstash.html). 4. (Optional) [Configure {{ents}} monitoring](https://www.elastic.co/guide/en/enterprise-search/current/monitoring.html). @@ -82,9 +82,9 @@ To store monitoring data in a separate cluster: 6. (Optional) [Configure APM Server monitoring](https://www.elastic.co/guide/en/apm/guide/current/monitor-apm.html) 7. (Optional) Configure {{kib}} to collect data and send it to the monitoring cluster: - * [{{agent}} collection methods](../../../deploy-manage/monitor/stack-monitoring/monitoring-elastic-agent.md) - * [{{metricbeat}} collection methods](../../../deploy-manage/monitor/stack-monitoring/monitoring-metricbeat.md) - * [Legacy collection methods](../../../deploy-manage/monitor/stack-monitoring/monitoring-kibana.md) + * [{{agent}} collection methods](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md) + * [{{metricbeat}} collection methods](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md) + * [Legacy collection methods](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md) 8. (Optional) Create a dedicated {{kib}} instance for monitoring, rather than using a single {{kib}} instance to access both your production cluster and monitoring cluster. @@ -95,5 +95,5 @@ To store monitoring data in a separate cluster: 1. (Optional) Disable the collection of monitoring data in this {{kib}} instance. Set the `xpack.monitoring.kibana.collection.enabled` setting to `false` in the `kibana.yml` file. For more information about this setting, see [Monitoring settings in {{kib}}](https://www.elastic.co/guide/en/kibana/current/monitoring-settings-kb.html). -9. [Configure {{kib}} to retrieve and display the monitoring data](../../../deploy-manage/monitor/stack-monitoring/monitoring-data.md). +9. [Configure {{kib}} to retrieve and display the monitoring data](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md). diff --git a/raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md b/raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md index a328fc015..62fe191df 100644 --- a/raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md +++ b/raw-migrated-files/stack-docs/elastic-stack/upgrade-elastic-stack-for-elastic-cloud.md @@ -6,7 +6,7 @@ Minor version upgrades, upgrades from 8.17 to 9.0.0-beta1, and cluster configura {{ess}} and {{ece}} do not support the ability to upgrade to or from release candidate builds, such as 8.0.0-rc1. -If you use a separate [monitoring deployment](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md), you should upgrade the monitoring deployment before the production deployment. In general, the monitoring deployment and the deployments being monitored should be running the same version of the Elastic Stack. A monitoring deployment cannot monitor production deployments running newer versions of the stack. If necessary, the monitoring deployment can monitor production deployments running the latest release of the previous major version. +If you use a separate [monitoring deployment](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md), you should upgrade the monitoring deployment before the production deployment. In general, the monitoring deployment and the deployments being monitored should be running the same version of the Elastic Stack. A monitoring deployment cannot monitor production deployments running newer versions of the stack. If necessary, the monitoring deployment can monitor production deployments running the latest release of the previous major version. ::::{important} Although it’s simple to upgrade an Elastic Cloud deployment, the new version might include breaking changes that affect your application. Make sure you review the deprecation logs, make any necessary changes, and test against the new version before upgrading your production deployment. diff --git a/solutions/observability/apps/monitor-apm-server.md b/solutions/observability/apps/monitor-apm-server.md index 25aaf3753..cbe40aa57 100644 --- a/solutions/observability/apps/monitor-apm-server.md +++ b/solutions/observability/apps/monitor-apm-server.md @@ -18,5 +18,5 @@ Select your deployment method to get started: {{ecloud}} manages the installation and configuration of a monitoring agent for you — so all you have to do is flip a switch and watch the data pour in. -* **{{ess}}** user? See [ESS: Enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). +* **{{ess}}** user? See [ESS: Enable logging and monitoring](../../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). * **{{ece}}** user? See [ECE: Enable logging and monitoring](https://www.elastic.co/guide/en/cloud-enterprise/{{ece-version-link}}/ece-enable-logging-and-monitoring.html). diff --git a/solutions/observability/apps/monitor-fleet-managed-apm-server.md b/solutions/observability/apps/monitor-fleet-managed-apm-server.md index 59a5d5f8b..fc11df528 100644 --- a/solutions/observability/apps/monitor-fleet-managed-apm-server.md +++ b/solutions/observability/apps/monitor-fleet-managed-apm-server.md @@ -166,4 +166,4 @@ See the [{{agent}} command reference](https://www.elastic.co/guide/en/fleet/curr For more information about these configuration options, see [Configure the {{es}} output](https://www.elastic.co/guide/en/beats/metricbeat/current/elasticsearch-output.html). 6. [Start {{metricbeat}}](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-starting.html) to begin collecting APM monitoring data. -7. [View the monitoring data in {{kib}}](../../../deploy-manage/monitor/stack-monitoring/monitoring-data.md). +7. [View the monitoring data in {{kib}}](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md). diff --git a/solutions/observability/apps/use-internal-collection-to-send-monitoring-data.md b/solutions/observability/apps/use-internal-collection-to-send-monitoring-data.md index f912e513f..37a2118a1 100644 --- a/solutions/observability/apps/use-internal-collection-to-send-monitoring-data.md +++ b/solutions/observability/apps/use-internal-collection-to-send-monitoring-data.md @@ -70,7 +70,7 @@ Use internal collectors to send {{beats}} monitoring data directly to your monit You must specify the `username` as `""` explicitly so that the username from the client certificate (`CN`) is used. See [SSL/TLS output settings](ssltls-output-settings.md) for more information about SSL settings. 3. Start APM Server. -4. [View the monitoring data in {{kib}}](../../../deploy-manage/monitor/stack-monitoring/monitoring-data.md). +4. [View the monitoring data in {{kib}}](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md). ## Settings for internal collection [apm-configuration-monitor] diff --git a/solutions/observability/apps/use-metricbeat-to-send-monitoring-data.md b/solutions/observability/apps/use-metricbeat-to-send-monitoring-data.md index 16f6c9888..d38a21ace 100644 --- a/solutions/observability/apps/use-metricbeat-to-send-monitoring-data.md +++ b/solutions/observability/apps/use-metricbeat-to-send-monitoring-data.md @@ -161,5 +161,5 @@ To collect and ship monitoring data: For more information about these configuration options, see [Configure the {{es}} output](https://www.elastic.co/guide/en/beats/metricbeat/current/elasticsearch-output.html). 6. [Start {{metricbeat}}](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-starting.html) to begin collecting monitoring data. -7. [View the monitoring data in {{kib}}](../../../deploy-manage/monitor/stack-monitoring/monitoring-data.md). +7. [View the monitoring data in {{kib}}](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-data.md). diff --git a/troubleshoot/elasticsearch/high-cpu-usage.md b/troubleshoot/elasticsearch/high-cpu-usage.md index 3c6f02aa1..1420ed7df 100644 --- a/troubleshoot/elasticsearch/high-cpu-usage.md +++ b/troubleshoot/elasticsearch/high-cpu-usage.md @@ -35,7 +35,7 @@ To track CPU usage over time, we recommend enabling monitoring: :::::::{tab-set} ::::::{tab-item} Elasticsearch Service -* (Recommended) Enable [logs and metrics](../../deploy-manage/monitor/stack-monitoring/stack-monitoring-on-elastic-cloud-deployments.md). When logs and metrics are enabled, monitoring information is visible on {{kib}}'s [Stack Monitoring](../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md) page. +* (Recommended) Enable [logs and metrics](../../deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md). When logs and metrics are enabled, monitoring information is visible on {{kib}}'s [Stack Monitoring](../../deploy-manage/monitor/monitoring-data/visualizing-monitoring-data.md) page. You can also enable the [CPU usage threshold alert](../../deploy-manage/monitor/monitoring-data/kibana-alerts.md) to be notified about potential issues through email. From 0c8e5f625b9bdec861c42a4ecc1b47052963fcdc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Tue, 4 Feb 2025 20:15:22 +0100 Subject: [PATCH 03/11] fixed frontmatter in two files --- .../monitor/stack-monitoring/es-legacy-collection-methods.md | 1 - .../monitor/stack-monitoring/kibana-monitoring-legacy.md | 1 - 2 files changed, 2 deletions(-) diff --git a/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md b/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md index ebc7019e6..8ec9f98e9 100644 --- a/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md +++ b/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md @@ -4,7 +4,6 @@ mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/collecting-monitoring-data.html applies: stack: deprecated 7.16.0 - stack: removed 9.0.0 --- diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md index a4f5a0ce9..289e25a12 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md @@ -4,7 +4,6 @@ mapped_pages: - https://www.elastic.co/guide/en/kibana/current/monitoring-kibana.html applies: stack: deprecated 7.16.0 - stack: removed 9.0.0 --- From 9196ea0c1a4cedc1ab00f823c4fd4c6dba1e4d4c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Tue, 4 Feb 2025 20:29:09 +0100 Subject: [PATCH 04/11] extra files renamed in monitoring --- deploy-manage/deploy/self-managed/access.md | 2 +- deploy-manage/deploy/self-managed/configure.md | 6 +++--- ...settings-examples.md => kibana-log-settings-examples.md} | 0 ...configuration.md => kibana-logging-cli-configuration.md} | 0 .../monitor/logging-configuration/kibana-logging.md | 2 +- .../monitor/stack-monitoring/ece-stack-monitoring.md | 4 ++-- deploy-manage/toc.yml | 4 ++-- raw-migrated-files/kibana/kibana/logging-settings.md | 6 +++--- troubleshoot/kibana/access.md | 2 +- troubleshoot/kibana/error-server-not-ready.md | 2 +- 10 files changed, 14 insertions(+), 14 deletions(-) rename deploy-manage/monitor/logging-configuration/{log-settings-examples.md => kibana-log-settings-examples.md} (100%) rename deploy-manage/monitor/logging-configuration/{_cli_configuration.md => kibana-logging-cli-configuration.md} (100%) diff --git a/deploy-manage/deploy/self-managed/access.md b/deploy-manage/deploy/self-managed/access.md index fe6bf6e92..a493ffe37 100644 --- a/deploy-manage/deploy/self-managed/access.md +++ b/deploy-manage/deploy/self-managed/access.md @@ -67,7 +67,7 @@ Troubleshoot the `Kibana Server is not Ready yet` error. These {{kib}}-backing indices must also not have [index settings](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-get-settings.html) flagging `read_only_allow_delete` or `write` [index blocks](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-blocks.html). 3. [Shut down all {{kib}} nodes](../../maintenance/start-stop-services/start-stop-kibana.md). -4. Choose any {{kib}} node, then update the config to set the [debug logging](../../monitor/logging-configuration/log-settings-examples.md#change-overall-log-level). +4. Choose any {{kib}} node, then update the config to set the [debug logging](../../monitor/logging-configuration/kibana-log-settings-examples.md#change-overall-log-level). 5. [Start the node](../../maintenance/start-stop-services/start-stop-kibana.md), then check the start-up debug logs for `ERROR` messages or other start-up issues. For example: diff --git a/deploy-manage/deploy/self-managed/configure.md b/deploy-manage/deploy/self-managed/configure.md index 501069c3a..0aa97dbc9 100644 --- a/deploy-manage/deploy/self-managed/configure.md +++ b/deploy-manage/deploy/self-managed/configure.md @@ -196,10 +196,10 @@ $$$logging-root-appenders$$$ `logging.root.appenders` : A list of logging appenders to forward the root level logger instance to. By default `root` is configured with the `default` appender that logs to stdout with a `pattern` layout. This is the configuration that all custom loggers will use unless they’re re-configured explicitly. You can override the default behavior by configuring a different [appender](../../monitor/logging-configuration/kibana-logging.md#logging-appenders) to apply to `root`. $$$logging-root-level$$$ `logging.root.level` ![logo cloud](https://doc-icons.s3.us-east-2.amazonaws.com/logo_cloud.svg "Supported on {{ess}}") -: Level at which a log record should be logged. Supported levels are: *all*, *fatal*, *error*, *warn*, *info*, *debug*, *trace*, *off*. Levels are ordered from *all* (highest) to *off* and a log record will be logged it its level is higher than or equal to the level of its logger, otherwise the log record is ignored. Use this value to [change the overall log level](../../monitor/logging-configuration/log-settings-examples.md#change-overall-log-level). **Default: `info`**. +: Level at which a log record should be logged. Supported levels are: *all*, *fatal*, *error*, *warn*, *info*, *debug*, *trace*, *off*. Levels are ordered from *all* (highest) to *off* and a log record will be logged it its level is higher than or equal to the level of its logger, otherwise the log record is ignored. Use this value to [change the overall log level](../../monitor/logging-configuration/kibana-log-settings-examples.md#change-overall-log-level). **Default: `info`**. ::::{tip} - Set to `all` to log all events, including system usage information and all requests. Set to `off` to silence all logs. You can also use the logging [cli commands](../../monitor/logging-configuration/_cli_configuration.md#logging-cli-migration) to set log level to `verbose` or silence all logs. + Set to `all` to log all events, including system usage information and all requests. Set to `off` to silence all logs. You can also use the logging [cli commands](../../monitor/logging-configuration/kibana-logging-cli-configuration.md#logging-cli-migration) to set log level to `verbose` or silence all logs. :::: @@ -220,7 +220,7 @@ $$$logging-root-level$$$ `logging.root.level` ![logo cloud](https://doc-icons.s3 $$$logging-loggers$$$ `logging.loggers[]` -: Allows you to [customize a specific logger instance](../../monitor/logging-configuration/log-settings-examples.md#customize-specific-log-records). +: Allows you to [customize a specific logger instance](../../monitor/logging-configuration/kibana-log-settings-examples.md#customize-specific-log-records). `logging.appenders[]` : [Appenders](../../monitor/logging-configuration/kibana-logging.md#logging-appenders) define how and where log messages are displayed (eg. **stdout** or console) and stored (eg. file on the disk). diff --git a/deploy-manage/monitor/logging-configuration/log-settings-examples.md b/deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md similarity index 100% rename from deploy-manage/monitor/logging-configuration/log-settings-examples.md rename to deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md diff --git a/deploy-manage/monitor/logging-configuration/_cli_configuration.md b/deploy-manage/monitor/logging-configuration/kibana-logging-cli-configuration.md similarity index 100% rename from deploy-manage/monitor/logging-configuration/_cli_configuration.md rename to deploy-manage/monitor/logging-configuration/kibana-logging-cli-configuration.md diff --git a/deploy-manage/monitor/logging-configuration/kibana-logging.md b/deploy-manage/monitor/logging-configuration/kibana-logging.md index 687e38e9b..8118fcab5 100644 --- a/deploy-manage/monitor/logging-configuration/kibana-logging.md +++ b/deploy-manage/monitor/logging-configuration/kibana-logging.md @@ -37,7 +37,7 @@ A log record will be logged by the logger if its level is higher than or equal t Logging set at a plugin level is always respected, regardless of the `root` logger level. In other words, if root logger is set to fatal and pluginA logging is set to `debug`, debug logs are only shown for pluginA, with other logs only reporting on `fatal`. -The *all* and *off* levels can only be used in configuration and are handy shortcuts that allow you to log every log record or disable logging entirely for a specific logger. These levels can also be specified using [cli arguments](_cli_configuration.md#logging-cli-migration). +The *all* and *off* levels can only be used in configuration and are handy shortcuts that allow you to log every log record or disable logging entirely for a specific logger. These levels can also be specified using [cli arguments](kibana-logging-cli-configuration.md#logging-cli-migration). ## Layouts [logging-layouts] diff --git a/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md index d88f253ef..c723bb29a 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md @@ -7,7 +7,7 @@ applies: # Enable stack monitoring on ECE deployments [ece-enable-logging-and-monitoring] -The deployment logging and monitoring feature lets you monitor your deployment in [Kibana](../../../get-started/the-stack.md) by shipping logs and metrics to a monitoring deployment. You can: +The deployment logging and monitoring feature lets you monitor your deployment in [Kibana](/get-started/the-stack.md) by shipping logs and metrics to a monitoring deployment. You can: * View your deployment’s health and performance in real time and analyze past cluster, index, and node metrics. * View your deployment’s logs to debug issues, discover slow queries, surface deprecations, and analyze access to your deployment. @@ -112,7 +112,7 @@ An ILM policy is pre-configured to manage log retention. The policy can be adjus ### Index management [ece-logging-and-monitoring-index-management-ilm] -When sending monitoring data to a deployment, you can configure [Index Lifecycle Management (ILM)](../manage-data/lifecycle/index-lifecycle-management.md) to manage retention of your monitoring and logging indices. When sending logs to a deployment, an ILM policy is pre-configured to manage log retention and the policy can be customized to your needs. +When sending monitoring data to a deployment, you can configure [Index Lifecycle Management (ILM)](/manage-data/lifecycle/index-lifecycle-management.md) to manage retention of your monitoring and logging indices. When sending logs to a deployment, an ILM policy is pre-configured to manage log retention and the policy can be customized to your needs. ### Enable logging and monitoring [ece-enable-logging-and-monitoring-steps] diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index db6933705..952178a7b 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -780,8 +780,8 @@ toc: - file: monitor/logging-configuration/elasticsearch-deprecation-logs.md - file: monitor/logging-configuration/kibana-logging.md children: - - file: monitor/logging-configuration/log-settings-examples.md - - file: monitor/logging-configuration/_cli_configuration.md + - file: monitor/logging-configuration/kibana-log-settings-examples.md + - file: monitor/logging-configuration/kibana-logging-cli-configuration.md - file: monitor/logging-configuration/security-event-audit-logging.md children: - file: monitor/logging-configuration/enabling-elasticsearch-audit-logs.md diff --git a/raw-migrated-files/kibana/kibana/logging-settings.md b/raw-migrated-files/kibana/kibana/logging-settings.md index e1bf51107..60237f131 100644 --- a/raw-migrated-files/kibana/kibana/logging-settings.md +++ b/raw-migrated-files/kibana/kibana/logging-settings.md @@ -20,13 +20,13 @@ The logging configuration is validated against the predefined schema and if ther * Loggers define what logging settings, such as the level of verbosity and the appenders, to apply to a particular context. Each log entry context provides information about the service or plugin that emits it and any of its sub-parts, for example, `metrics.ops` or `elasticsearch.query`. * Root is a logger that applies to all the log entries in {{kib}}. -The following table serves as a quick reference for different logging configuration keys. Note that these are not stand-alone settings and may require additional logging configuration. See the [Configure Logging in {{kib}}](../../../deploy-manage/monitor/logging-configuration/kibana-logging.md) guide and complete [examples](../../../deploy-manage/monitor/logging-configuration/log-settings-examples.md) for common configuration use cases. +The following table serves as a quick reference for different logging configuration keys. Note that these are not stand-alone settings and may require additional logging configuration. See the [Configure Logging in {{kib}}](../../../deploy-manage/monitor/logging-configuration/kibana-logging.md) guide and complete [examples](../../../deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md) for common configuration use cases. | | | | --- | --- | | `logging.appenders[].` | Unique appender identifier. | -| `logging.appenders[].console:` | Appender to use for logging records to **stdout**. By default, uses the `[%date][%level][%logger] %message` **pattern*** layout. To use a ***json**, set the [layout type to `json`](../../../deploy-manage/monitor/logging-configuration/log-settings-examples.md#log-in-json-ECS-example). | -| `logging.appenders[].file:` | Allows you to specify a fileName to write log records to disk. To write [all log records to file](../../../deploy-manage/monitor/logging-configuration/log-settings-examples.md#log-to-file-example), add the file appender to `root.appenders`. If configured, you also need to specify [`logging.appenders.file.pathName`](../../../deploy-manage/monitor/logging-configuration/log-settings-examples.md#log-to-file-example). | +| `logging.appenders[].console:` | Appender to use for logging records to **stdout**. By default, uses the `[%date][%level][%logger] %message` **pattern*** layout. To use a ***json**, set the [layout type to `json`](../../../deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md#log-in-json-ECS-example). | +| `logging.appenders[].file:` | Allows you to specify a fileName to write log records to disk. To write [all log records to file](../../../deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md#log-to-file-example), add the file appender to `root.appenders`. If configured, you also need to specify [`logging.appenders.file.pathName`](../../../deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md#log-to-file-example). | | `logging.appenders[].rolling-file:` | Similar to [Log4j’s](https://logging.apache.org/log4j/2.x/) `RollingFileAppender`, this appender will log to a file and rotate if following a rolling strategy when the configured policy triggers. There are currently two policies supported: [`size-limit`](../../../deploy-manage/monitor/logging-configuration/kibana-logging.md#size-limit-triggering-policy) and [`time-interval`](../../../deploy-manage/monitor/logging-configuration/kibana-logging.md#time-interval-triggering-policy). | | `logging.appenders[]..type` | The appender type determines where the log messages are sent. Options are `console`, `file`, `rewrite`, `rolling-file`. Required. | | `logging.appenders[]..fileName` | Determines the filepath where the log messages are written to for file and rolling-file appender types. Required for appenders that write to file. | diff --git a/troubleshoot/kibana/access.md b/troubleshoot/kibana/access.md index f6581c78c..daf4585e9 100644 --- a/troubleshoot/kibana/access.md +++ b/troubleshoot/kibana/access.md @@ -67,7 +67,7 @@ Troubleshoot the `Kibana Server is not Ready yet` error. These {{kib}}-backing indices must also not have [index settings](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-get-settings.html) flagging `read_only_allow_delete` or `write` [index blocks](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-blocks.html). 3. [Shut down all {{kib}} nodes](../../deploy-manage/maintenance/start-stop-services/start-stop-kibana.md). -4. Choose any {{kib}} node, then update the config to set the [debug logging](../../deploy-manage/monitor/logging-configuration/log-settings-examples.md#change-overall-log-level). +4. Choose any {{kib}} node, then update the config to set the [debug logging](../../deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md#change-overall-log-level). 5. [Start the node](../../deploy-manage/maintenance/start-stop-services/start-stop-kibana.md), then check the start-up debug logs for `ERROR` messages or other start-up issues. For example: diff --git a/troubleshoot/kibana/error-server-not-ready.md b/troubleshoot/kibana/error-server-not-ready.md index 42df91c89..2855617e5 100644 --- a/troubleshoot/kibana/error-server-not-ready.md +++ b/troubleshoot/kibana/error-server-not-ready.md @@ -67,7 +67,7 @@ Troubleshoot the `Kibana Server is not Ready yet` error. These {{kib}}-backing indices must also not have [index settings](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-get-settings.html) flagging `read_only_allow_delete` or `write` [index blocks](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-blocks.html). 3. [Shut down all {{kib}} nodes](../../deploy-manage/maintenance/start-stop-services/start-stop-kibana.md). -4. Choose any {{kib}} node, then update the config to set the [debug logging](../../deploy-manage/monitor/logging-configuration/log-settings-examples.md#change-overall-log-level). +4. Choose any {{kib}} node, then update the config to set the [debug logging](../../deploy-manage/monitor/logging-configuration/kibana-log-settings-examples.md#change-overall-log-level). 5. [Start the node](../../deploy-manage/maintenance/start-stop-services/start-stop-kibana.md), then check the start-up debug logs for `ERROR` messages or other start-up issues. For example: From c09c77bbaa50f64e5ca949a21e054520103e2a9d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Tue, 4 Feb 2025 20:33:10 +0100 Subject: [PATCH 05/11] heroku documents deleted --- .../monitoring-data/ech-memory-pressure.md | 37 ----- .../ech-saas-metrics-accessing.md | 129 ------------------ .../ech-vcpu-boost-instance.md | 53 ------- deploy-manage/toc.yml | 4 - 4 files changed, 223 deletions(-) delete mode 100644 deploy-manage/monitor/monitoring-data/ech-memory-pressure.md delete mode 100644 deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md delete mode 100644 deploy-manage/monitor/monitoring-data/ech-vcpu-boost-instance.md diff --git a/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md b/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md deleted file mode 100644 index e40859d1c..000000000 --- a/deploy-manage/monitor/monitoring-data/ech-memory-pressure.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/cloud-heroku/current/ech-memory-pressure.html ---- - -% FILE TO REMOVE (HEROKU IT COMES FROM A LIFT AND SHIFT WITH MULTIPLE URLS) - -# JVM memory pressure indicator [ech-memory-pressure] - -In addition to the more detailed [cluster performance metrics](../stack-monitoring/elastic-cloud-stack-monitoring.md), the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) also includes a JVM memory pressure indicator for each node in your cluster. This indicator can help you to determine when you need to upgrade to a larger cluster. - -The percentage number used in the JVM memory pressure indicator is actually the fill rate of the old generation pool. For a detailed explanation of why this metric is used, check [Understanding Memory Pressure](https://www.elastic.co/blog/found-understanding-memory-pressure-indicator/). - -:::{image} ../../../images/cloud-heroku-memory-pressure-indicator.png -:alt: Memory pressure indicator -::: - - -## JVM memory pressure levels [ech-memory-pressure-levels] - -When the JVM memory pressure reaches 75%, the indicator turns red. At this level, garbage collection becomes more frequent as the memory usage increases, potentially impacting the performance of your cluster. As long as the cluster performance suits your needs, JVM memory pressure above 75% is not a problem in itself, but there is not much spare memory capacity. Review the [common causes of high JVM memory usage](#ech-memory-pressure-causes) to determine your best course of action. - -When the JVM memory pressure indicator rises above 95%, {{es}}'s [real memory circuit breaker](https://www.elastic.co/guide/en/elasticsearch/reference/current/circuit-breaker.html#parent-circuit-breaker) triggers to prevent your instance from running out of memory. This situation can reduce the stability of your cluster and the integrity of your data. Unless you expect the load to drop soon, we recommend that you resize to a larger cluster before you reach this level of memory pressure. Even if you’re planning to optimize your memory usage, it is best to resize the cluster first. Resizing the cluster to increase capacity can give you more time to apply other changes, and also provides the cluster with more resource for when those changes are applied. - - -## Common causes of high JVM memory usage [ech-memory-pressure-causes] - -The two most common reasons for a high JVM memory pressure reading are: - -**1. Having too many shards per node** - -If JVM memory pressure above 75% is a frequent occurrence, the cause is often having too many shards per node relative to the amount of available memory. You can lower the JVM memory pressure by reducing the number of shards or upgrading to a larger cluster. For guidelines, check [How to size your shards](https://www.elastic.co/guide/en/elasticsearch/reference/current/size-your-shards.html). - -**2. Running expensive queries** - -If JVM memory pressure above 75% happens only occasionally, this is often due to expensive queries. Queries that have a very large request size, that involve aggregations with a large volume of buckets, or that involve sorting on a non-optimized field, can all cause temporary spikes in JVM memory usage. To resolve this problem, consider optimizing your queries or upgrading to a larger cluster. - diff --git a/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md b/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md deleted file mode 100644 index 850c8cf1c..000000000 --- a/deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/cloud-heroku/current/ech-saas-metrics-accessing.html ---- - -% FILE TO REMOVE (HEROKU IT COMES FROM A LIFT AND SHIFT WITH MULTIPLE URLS) - -# Access performance metrics [ech-saas-metrics-accessing] - -Cluster performance metrics are available directly in the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body). The graphs on this page include a subset of Elasticsearch Add-On for Heroku-specific performance metrics. - -For advanced views or production monitoring, [enable logging and monitoring](../stack-monitoring/elastic-cloud-stack-monitoring.md). The monitoring application provides more advanced views for Elasticsearch and JVM metrics, and includes a configurable retention period. - -To access cluster performance metrics: - -1. Log in to the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body). -2. On the deployments page, select your deployment. - - Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list. For example, you might want to select **Is unhealthy** and **Has master problems** to get a short list of deployments that need attention. - -3. From your deployment menu, go to the **Performance** page. - -The following metrics are available: - - -### CPU usage [echcpu_usage] - -:::{image} ../../../images/cloud-heroku-metrics-cpu-usage.png -:alt: Graph showing CPU usage -::: - -Shows the maximum usage of the CPU resources assigned to your Elasticsearch cluster, as a percentage. CPU resources are relative to the size of your cluster, so that a cluster with 32GB of RAM gets assigned twice as many CPU resources as a cluster with 16GB of RAM. All clusters are guaranteed their share of CPU resources, as Elasticsearch Add-On for Heroku infrastructure does not overcommit any resources. CPU credits permit boosting the performance of smaller clusters temporarily, so that CPU usage can exceed 100%. - - -### CPU credits [echcpu_credits] - -:::{image} ../../../images/cloud-heroku-metrics-cpu-credits.png -:alt: Graph showing available CPU credits -::: - -Shows your remaining CPU credits, measured in seconds of CPU time. CPU credits enable the boosting of CPU resources assigned to your cluster to improve performance temporarily when it is needed most. For more details check [How to use vCPU to boost your instance](ech-vcpu-boost-instance.md). - - -### Number of requests [echnumber_of_requests] - -:::{image} ../../../images/cloud-heroku-metrics-number-of-requests.png -:alt: Graph showing the number of requests -::: - -Shows the number of requests that your cluster receives per second, separated into search requests and requests to index documents. This metric provides a good indicator of the volume of work that your cluster typically handles over time which, together with other performance metrics, helps you determine if your cluster is sized correctly. Also lets you check if there is a sudden increase in the volume of user requests that might explain an increase in response times. - - -### Search response times [echsearch_response_times] - -:::{image} ../../../images/cloud-heroku-metrics-search-response-times.png -:alt: Graph showing search response times -::: - -Indicates the amount of time that it takes for your Elasticsearch cluster to complete a search query, in milliseconds. Response times won’t tell you about the cause of a performance issue, but they are often a first indicator that something is amiss with the performance of your Elasticsearch cluster. - - -### Index response times [echindex_response_times] - -:::{image} ../../../images/cloud-heroku-metrics-index-response-times.png -:alt: Graph showing index response times -::: - -Indicates the amount of time that it takes for your Elasticsearch cluster to complete an indexing operation, in milliseconds. Response times won’t tell you about the cause of a performance issue, but they are often a first indicator that something is amiss with the performance of your Elasticsearch cluster. - - -### Memory pressure per node [echmemory_pressure_per_node] - -:::{image} ../../../images/cloud-heroku-metrics-memory-pressure-per-node.png -:alt: Graph showing memory pressure per node -::: - -Indicates the total memory used by the JVM heap over time. We’ve configured {{es}}'s garbage collector to keep memory usage below 75% for heaps of 8GB or larger. For heaps smaller than 8GB, the threshold is 85%. If memory pressure consistently remains above this threshold, you might need to resize your cluster or reduce memory consumption. Check [how high memory pressure can cause performance issues](../../../troubleshoot/monitoring/high-memory-pressure.md). - - -### GC overhead per node [echgc_overhead_per_node] - -:::{image} ../../../images/cloud-heroku-metrics-gc-overhead-per-node.png -:alt: Graph showing the garbage collection overhead per node -::: - -Indicates the overhead involved in JVM garbage collection to reclaim memory. - - -## Tips for working with performance metrics [echtips_for_working_with_performance_metrics] - -Performance correlates directly with resources assigned to your cluster, and many of these metrics will show some sort of correlation with each other when you are trying to determine the cause of a performance issue. Take a look at some of the scenarios included in this section to learn how you can determine the cause of performance issues. - -It is not uncommon for performance issues on Elasticsearch Add-On for Heroku to be caused by an undersized cluster that cannot cope with the workload it is being asked to handle. If your cluster performance metrics often shows high CPU usage or excessive memory pressure, consider increasing the size of your cluster soon to improve performance. This is especially true for clusters that regularly reach 100% of CPU usage or that suffer out-of-memory failures; it is better to resize your cluster early when it is not yet maxed out than to have to resize a cluster that is already overwhelmed. [Changing the configuration of your cluster](../../deploy/elastic-cloud/cloud-hosted.md) may add some overhead if data needs to be migrated to the new nodes, which can increase the load on a cluster further and delay configuration changes. - -To help diagnose high CPU usage you can also use the Elasticsearch [nodes hot threads API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-hot-threads.html), which identifies the threads on each node that have the highest CPU usage or that have been executing for a longer than normal period of time. - -::::{tip} -Got an overwhelmed cluster that needs to be upsized? [Try enabling maintenance mode first](https://www.elastic.co/guide/en/cloud-heroku/current/ech-upgrading-v5.html#ech-maintenance-mode-routing). It will likely help with configuration changes. -:::: - - -Work with the metrics shown in **Cluster Performance Metrics** section to help you find the information you need: - -* Hover on any part of a graph to get additional information. For example, hovering on a section of a graph that shows response times reveals the percentile that responses fall into at that point in time: - - :::{image} ../../../images/cloud-heroku-metrics-hover.png - :alt: Hover over the metric graph - ::: - -* Zoom in on a graph by drawing a rectangle to select a specific time window. As you zoom in one metric, other performance metrics change to show data for the same time window. - - :::{image} ../../../images/cloud-heroku-metrics-zoom.png - :alt: Zoom the metric graph - ::: - -* Pan around with ![Pan in a metric graph](../../../images/cloud-heroku-metrics-pan.png "") to make sure that you can get the right parts of a metric graph as you zoom in. -* Reset the metric graph axes with ![Reset the metric graph](../../../images/cloud-heroku-metrics-reset.png ""), which returns the graphs to their original scale. - -Cluster performance metrics are shown per node and are color-coded to indicate which running Elasticsearch instance they belong to. - - -## Cluster restarts after out-of-memory failures [echcluster_restarts_after_out_of_memory_failures] - -For clusters that suffer out-of-memory failures, it can be difficult to determine whether the clusters are in a completely healthy state afterwards. For this reason, Elasticsearch Add-On for Heroku automatically reboots clusters that suffer out-of-memory failures. - -You will receive an email notification to let you know that a restart occurred. For repeated alerts, the emails are aggregated so that you do not receive an excessive number of notifications. Either [resizing your cluster to reduce memory pressure](../../deploy/elastic-cloud/ech-customize-deployment-components.md#ech-cluster-size) or reducing the workload that a cluster is being asked to handle can help avoid these cluster restarts. - - - diff --git a/deploy-manage/monitor/monitoring-data/ech-vcpu-boost-instance.md b/deploy-manage/monitor/monitoring-data/ech-vcpu-boost-instance.md deleted file mode 100644 index 9b8505e72..000000000 --- a/deploy-manage/monitor/monitoring-data/ech-vcpu-boost-instance.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/cloud-heroku/current/ech-vcpu-boost-instance.html -applies: - hosted: all ---- - -% FILE TO REMOVE (HEROKU IT COMES FROM A LIFT AND SHIFT WITH MULTIPLE URLS) - -# vCPU boosting and credits [ech-vcpu-boost-instance] - -Elastic Cloud allows smaller instance sizes to get temporarily boosted vCPU when under heavy load. vCPU boosting is governed by vCPU credits that instances can earn over time when vCPU usage is less than the assigned amount. - - -## How does vCPU boosting work? [echhow_does_vcpu_boosting_work] - -Based on the instance size, the vCPU resources assigned to your instance can be boosted to improve performance temporarily, by using vCPU credits. If credits are available, Elastic Cloud will automatically boost your instance when under heavy load. Boosting is available depending on the instance size: - -* Instance sizes up to and including 12 GB of RAM get boosted. The boosted vCPU value is `16 * vCPU ratio`, the vCPU ratios are dependent on the [hardware profile](../../deploy/elastic-cloud/ech-reference-hardware.md#ech-getting-started-configurations) selected. If an instance is eligible for boosting, the Elastic Cloud console will display **Up to 2.5 vCPU**, depending on the hardware profile selected. The baseline, or unboosted, vCPU value is calculated as: `RAM size * vCPU ratio`. -* Instance sizes bigger than 12 GB of RAM do not get boosted. The vCPU value is displayed in the Elastic Cloud console and calculated as follows: `RAM size * vCPU ratio`. - - -## What are vCPU credits? [echwhat_are_vcpu_credits] - -[vCPU](https://www.elastic.co/guide/en/elastic-stack-glossary/current/terms.html#glossary-vcpu) credits enable a smaller instance to perform as if it were assigned the vCPU resources of a larger instance, but only for a limited time. vCPU credits are available only on smaller instances up to and including 8 GB of RAM. - -vCPU credits persist through cluster restarts, but they are tied to your existing instance nodes. Operations that create new instance nodes will lose existing vCPU credits. This happens when you resize your instance, or if Elastic performs system maintenance on your nodes. - - -## How to earn vCPU credits? [echhow_to_earn_vcpu_credits] - -When you initially create an instance, you receive a credit of 60 seconds worth of vCPU time. You can accumulate additional credits when your vCPU usage is less than what your instance is assigned. At most, you can accumulate one hour worth of additional vCPU time per GB of RAM for your instance. - -For example: An instance with 4 GB of RAM, can at most accumulate four hours worth of additional vCPU time and can consume all of these vCPU credits within four hours when loaded heavily with requests. - -If you observe declining performance on a smaller instance over time, you might have depleted your vCPU credits. In this case, increase the size of your cluster to handle the workload with consistent performance. - -For more information, check [Elasticsearch Service default provider instance configurations](../../deploy/elastic-cloud/ech-reference-hardware.md#ech-getting-started-configurations). - - -## Where to check vCPU credits status? [echwhere_to_check_vcpu_credits_status] - -You can check the **Monitoring > Performance > CPU Credits** section of the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body), and find the related metrics: - -:::{image} ../../../images/cloud-heroku-metrics-credits.png -:alt: CPU usage versus CPU credits over time -::: - - -## What to do if my vCPU credits get depleted constantly? [echwhat_to_do_if_my_vcpu_credits_get_depleted_constantly] - -If you need your cluster to be able to sustain a certain level of performance, you cannot rely on CPU boosting to handle the workload except temporarily. To ensure that performance can be sustained, consider increasing the size of your cluster. Read [this page](../../../troubleshoot/monitoring/performance.md) for more guidance. - diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index 952178a7b..8017d4303 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -762,10 +762,6 @@ toc: children: - file: monitor/monitoring-data/ec-memory-pressure.md - file: monitor/monitoring-data/ec-vcpu-boost-instance.md - - file: monitor/monitoring-data/ech-saas-metrics-accessing.md - children: - - file: monitor/monitoring-data/ech-memory-pressure.md - - file: monitor/monitoring-data/ech-vcpu-boost-instance.md - file: monitor/monitoring-data/configure-stack-monitoring-alerts.md - file: monitor/monitoring-data/configuring-data-streamsindices-for-monitoring.md children: From 093e60efa4cb884b745805a0671bae3ec05a2a0e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Tue, 4 Feb 2025 20:36:46 +0100 Subject: [PATCH 06/11] heroku URLs added to relevant mappings --- deploy-manage/monitor/monitoring-data/ec-memory-pressure.md | 1 + .../monitor/monitoring-data/ec-saas-metrics-accessing.md | 1 + deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md | 1 + 3 files changed, 3 insertions(+) diff --git a/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md b/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md index 30e72025e..5e3d94bf0 100644 --- a/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md +++ b/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md @@ -1,6 +1,7 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-memory-pressure.html + - https://www.elastic.co/guide/en/cloud-heroku/current/ech-memory-pressure.html applies: hosted: all ece: all diff --git a/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md b/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md index 38cd37322..4990f942b 100644 --- a/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md +++ b/deploy-manage/monitor/monitoring-data/ec-saas-metrics-accessing.md @@ -1,6 +1,7 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-saas-metrics-accessing.html + - https://www.elastic.co/guide/en/cloud-heroku/current/ech-saas-metrics-accessing.html applies: hosted: all --- diff --git a/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md b/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md index f3f246db7..b72326108 100644 --- a/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md +++ b/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md @@ -1,6 +1,7 @@ --- mapped_pages: - https://www.elastic.co/guide/en/cloud/current/ec-vcpu-boost-instance.html + - https://www.elastic.co/guide/en/cloud-heroku/current/ech-vcpu-boost-instance.html applies: hosted: all --- From aeb9c015023cf11485f268a4c71f34d7c5f7b9c7 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Tue, 4 Feb 2025 17:34:39 -0500 Subject: [PATCH 07/11] cleanup --- .../stack-monitoring/kibana-monitoring-elastic-agent.md | 4 ++-- .../monitor/stack-monitoring/kibana-monitoring-metricbeat.md | 4 ++-- .../stack-monitoring/kibana-monitoring-self-managed.md | 2 +- .../cloud/cloud-heroku/ech-config-change-errors.md | 2 +- raw-migrated-files/cloud/cloud-heroku/ech-monitoring-setup.md | 2 +- raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md | 2 +- raw-migrated-files/cloud/cloud-heroku/ech-planning.md | 2 +- .../cloud/cloud-heroku/ech-saas-metrics-accessing.md | 2 +- 8 files changed, 10 insertions(+), 10 deletions(-) diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md index 7e2e61f3e..1f9212139 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md @@ -11,7 +11,7 @@ applies: # Collect monitoring data with Elastic Agent [monitoring-elastic-agent] -In 8.5 and later, you can use {{agent}} to collect data about {{kib}} and ship it to the monitoring cluster, rather than [using {{metricbeat}}](monitoring-metricbeat.md) or routing data through the production cluster as described in [Legacy collection methods](kibana-monitoring-legacy.md). +In 8.5 and later, you can use {{agent}} to collect data about {{kib}} and ship it to the monitoring cluster, rather than [using {{metricbeat}}](/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md) or routing data through the production cluster as described in [Legacy collection methods](/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md). To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). @@ -54,4 +54,4 @@ To collect {{kib}} monitoring data, add a {{kib}} integration to an {{agent}} an 2. Follow the steps in the **Add agent** flyout to download, install, and enroll the {{agent}}. Make sure you choose the agent policy you created earlier. 9. Wait a minute or two until incoming data is confirmed. -10. [View the monitoring data in {{kib}}](monitoring-data.md). +10. [View the monitoring data in {{kib}}](/deploy-manage/monitor/monitoring-data.md). diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md index 18cdaabf9..51302754d 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md @@ -11,7 +11,7 @@ applies: # Collect monitoring data with Metricbeat [monitoring-metricbeat] -In 6.4 and later, you can use {{metricbeat}} to collect data about {{kib}} and ship it to the monitoring cluster, rather than routing it through the production cluster as described in [Legacy collection methods](kibana-monitoring-legacy.md). +In 6.4 and later, you can use {{metricbeat}} to collect data about {{kib}} and ship it to the monitoring cluster, rather than routing it through the production cluster as described in [Legacy collection methods](/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md). :::{image} ../../../images/kibana-metricbeat.png :alt: Example monitoring architecture @@ -144,5 +144,5 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md). For more information about these configuration options, see [Configure the {{es}} output](https://www.elastic.co/guide/en/beats/metricbeat/current/elasticsearch-output.html). 9. [Start {{metricbeat}}](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-starting.html). -10. [View the monitoring data in {{kib}}](monitoring-data.md). +10. [View the monitoring data in {{kib}}](/deploy-manage/monitor/monitoring-data.md). diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md index fb34b6135..7860161cb 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md @@ -15,7 +15,7 @@ If you enable the {{monitor-features}} in your cluster, there are a few methods * [{{agent}} collection](kibana-monitoring-elastic-agent.md): Uses a single agent to gather logs and metrics. Can be managed from a central location in {{fleet}}. * [{{metricbeat}} collection](kibana-monitoring-metricbeat.md): Uses a lightweight {{beats}} shipper to gather metrics. May be preferred if you have an existing investment in {{beats}} or are not yet ready to use {{agent}}. -* [Legacy collection](kibana-monitoring-legacy.md): Uses internal collectors to gather metrics. Not recommended. If you have previously configured legacy collection methods, you should migrate to using {{agent}} or {{metricbeat}}. +* [Legacy collection](/deploy-manage/monitor/stack-monitoring/kibana-monitoring-legacy.md): Uses internal collectors to gather metrics. Not recommended. If you have previously configured legacy collection methods, you should migrate to using {{agent}} or {{metricbeat}}. You can also use {{kib}} to [visualize monitoring data from across the {{stack}}](kibana-monitoring-data.md). diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-config-change-errors.md b/raw-migrated-files/cloud/cloud-heroku/ech-config-change-errors.md index f76354758..c07453399 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-config-change-errors.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-config-change-errors.md @@ -114,7 +114,7 @@ To view any added plugins or bundles: Configuration change errors can occur when there is insufficient RAM configured for a data tier. In this case, the cluster typically also shows OOM (out of memory) errors. To resolve these, you need to increase the amount of heap memory, which is half of the amount of memory allocated to a cluster. You might also detect OOM in plan changes via their [related exit codes](https://www.elastic.co/guide/en/elasticsearch/reference/current/stopping-elasticsearch.html#fatal-errors) `127`, `137`, and `158`. -Check the [{{es}} cluster size](../../../deploy-manage/deploy/elastic-cloud/ech-customize-deployment-components.md#ech-cluster-size) and the [JVM memory pressure indicator](../../../deploy-manage/monitor/monitoring-data/ech-memory-pressure.md) documentation to learn more. +Check the [{{es}} cluster size](../../../deploy-manage/deploy/elastic-cloud/ech-customize-deployment-components.md#ech-cluster-size) and the [JVM memory pressure indicator](/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md) documentation to learn more. As well, you can read our detailed blog [Managing and troubleshooting {{es}} memory](https://www.elastic.co/blog/managing-and-troubleshooting-elasticsearch-memory). diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring-setup.md b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring-setup.md index 45e26e29a..6012ad4ec 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring-setup.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring-setup.md @@ -59,7 +59,7 @@ To learn more about what [Elasticsearch monitoring metrics](https://www.elastic. :alt: Node tab in Kibana under Stack Monitoring ::: -Some [performance metrics](../../../deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md) are also available directly in the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) and don’t require looking at your monitoring deployment. If you’re ever in a rush to determine if there is a performance problem, you can get a quick overview by going to the **Performance** page from your deployment menu: +Some [performance metrics](/deploy-manage/monitor/monitoring-data/access-performance-metrics-on-elastic-cloud.md) are also available directly in the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) and don’t require looking at your monitoring deployment. If you’re ever in a rush to determine if there is a performance problem, you can get a quick overview by going to the **Performance** page from your deployment menu: :::{image} ../../../images/cloud-heroku-ec-ce-monitoring-performance.png :alt: Performance page of the Elastic Cloud console diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md index b727868df..db670c559 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md @@ -75,7 +75,7 @@ Configuration change failures Out of memory errors : Out of memory errors (OOMs) may occur during your deployment’s normal operations, and these can have a very negative impact on performance. Common causes of memory shortages are oversharding, data retention oversights, and the overall request volume. - On your deployment page, you can check the [JVM memory pressure indicator](../../../deploy-manage/monitor/monitoring-data/ech-memory-pressure.md) to get the current memory usage of each node of your deployment. You can also review the [common causes of high JVM memory usage](../../../deploy-manage/monitor/monitoring-data/ech-memory-pressure.md#ech-memory-pressure-causes) to help diagnose the source of unexpectedly high memory pressure levels. To learn more, check [How does high memory pressure affect performance?](../../../troubleshoot/monitoring/high-memory-pressure.md). + On your deployment page, you can check the [JVM memory pressure indicator]/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md) to get the current memory usage of each node of your deployment. You can also review the [common causes of high JVM memory usage](/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md#ech-memory-pressure-causes) to help diagnose the source of unexpectedly high memory pressure levels. To learn more, check [How does high memory pressure affect performance?](../../../troubleshoot/monitoring/high-memory-pressure.md). diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-planning.md b/raw-migrated-files/cloud/cloud-heroku/ech-planning.md index 1ced65ff9..c55030dec 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-planning.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-planning.md @@ -44,7 +44,7 @@ Clusters that only have one master node are not highly available and are at risk ## Do you know when to scale? [ech-workloads] -Knowing how to scale your deployment is critical, especially when unexpected workloads hits. Don’t forget to [check your performance metrics](../../../deploy-manage/monitor/monitoring-data/ech-saas-metrics-accessing.md) to make sure your deployments are healthy and can cope with your workloads. +Knowing how to scale your deployment is critical, especially when unexpected workloads hits. Don’t forget to [check your performance metrics](/deploy-manage/monitor/monitoring-data/access-performance-metrics-on-elastic-cloud.md) to make sure your deployments are healthy and can cope with your workloads. Scaling with Elasticsearch Add-On for Heroku is easy: diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md b/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md index 57d0f3f5c..44d91f857 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-saas-metrics-accessing.md @@ -31,7 +31,7 @@ Shows the maximum usage of the CPU resources assigned to your Elasticsearch clus :alt: Graph showing available CPU credits ::: -Shows your remaining CPU credits, measured in seconds of CPU time. CPU credits enable the boosting of CPU resources assigned to your cluster to improve performance temporarily when it is needed most. For more details check [How to use vCPU to boost your instance](../../../deploy-manage/monitor/monitoring-data/ech-vcpu-boost-instance.md). +Shows your remaining CPU credits, measured in seconds of CPU time. CPU credits enable the boosting of CPU resources assigned to your cluster to improve performance temporarily when it is needed most. For more details check [How to use vCPU to boost your instance](/deploy-manage/monitor/monitoring-data/ec-vcpu-boost-instance.md). ### Number of requests [echnumber_of_requests] From 263048267fd56b64bd0179948cda81c2814902b5 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Tue, 4 Feb 2025 17:36:10 -0500 Subject: [PATCH 08/11] fix anchor --- raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md index db670c559..5672d0de2 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-monitoring.md @@ -75,7 +75,7 @@ Configuration change failures Out of memory errors : Out of memory errors (OOMs) may occur during your deployment’s normal operations, and these can have a very negative impact on performance. Common causes of memory shortages are oversharding, data retention oversights, and the overall request volume. - On your deployment page, you can check the [JVM memory pressure indicator]/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md) to get the current memory usage of each node of your deployment. You can also review the [common causes of high JVM memory usage](/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md#ech-memory-pressure-causes) to help diagnose the source of unexpectedly high memory pressure levels. To learn more, check [How does high memory pressure affect performance?](../../../troubleshoot/monitoring/high-memory-pressure.md). + On your deployment page, you can check the [JVM memory pressure indicator]/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md) to get the current memory usage of each node of your deployment. You can also review the [common causes of high JVM memory usage](/deploy-manage/monitor/monitoring-data/ec-memory-pressure.md#ec-memory-pressure-causes) to help diagnose the source of unexpectedly high memory pressure levels. To learn more, check [How does high memory pressure affect performance?](../../../troubleshoot/monitoring/high-memory-pressure.md). From 1163a157c8f300f3fa9cadbbca69a960fb42ad78 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Wed, 5 Feb 2025 10:54:02 +0100 Subject: [PATCH 09/11] ga identifiers for versions pre 9.x removed --- .../collecting-monitoring-data-with-elastic-agent.md | 2 +- .../collecting-monitoring-data-with-metricbeat.md | 2 +- .../monitor/stack-monitoring/kibana-monitoring-elastic-agent.md | 2 +- .../monitor/stack-monitoring/kibana-monitoring-metricbeat.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md index 0e4eb14bc..d84d877df 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md @@ -3,7 +3,7 @@ navigation_title: "Collecting monitoring data with {{agent}}" mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-elastic-agent.html applies: - stack: ga 8.5.0 + stack: all --- diff --git a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md index 169cb0125..753fefcfe 100644 --- a/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md @@ -3,7 +3,7 @@ navigation_title: "Collecting monitoring data with {{metricbeat}}" mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-metricbeat.html applies: - stack: ga 6.5.0 + stack: all --- diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md index 1f9212139..83264edff 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md @@ -3,7 +3,7 @@ navigation_title: "Collect monitoring data with {{agent}}" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/monitoring-elastic-agent.html applies: - stack: ga 8.5.0 + stack: all --- diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md index 51302754d..ec6840dbc 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-metricbeat.md @@ -3,7 +3,7 @@ navigation_title: "Collect monitoring data with {{metricbeat}}" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/monitoring-metricbeat.html applies: - stack: ga 6.5.0 + stack: all --- From bee5b4bcbb1dcad6a66dc2e3fbe3181bde3a5c2c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Wed, 5 Feb 2025 10:56:22 +0100 Subject: [PATCH 10/11] duplicate overview resolved --- deploy-manage/monitor/monitoring-overview.md | 14 -------------- deploy-manage/toc.yml | 1 - 2 files changed, 15 deletions(-) delete mode 100644 deploy-manage/monitor/monitoring-overview.md diff --git a/deploy-manage/monitor/monitoring-overview.md b/deploy-manage/monitor/monitoring-overview.md deleted file mode 100644 index eab8b2690..000000000 --- a/deploy-manage/monitor/monitoring-overview.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -applies: - hosted: all - ece: all - eck: all - stack: all ---- -# Monitoring overview - -% What needs to be done: Write from scratch - -% GitHub issue: https://github.com/elastic/docs-projects/issues/350 - -% Scope notes: Write an overview about monitoring (maybe this is similar than the landing page). \ No newline at end of file diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index 8017d4303..610287092 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -687,7 +687,6 @@ toc: - file: manage-connectors.md - file: monitor.md children: - - file: monitor/monitoring-overview.md - file: monitor/autoops.md children: - file: monitor/autoops/ec-autoops-how-to-access.md From 161511812b391e759826b3e87ccdabc46b44c214 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Wed, 5 Feb 2025 11:20:18 +0100 Subject: [PATCH 11/11] some navigation titles updated --- .../elasticsearch-log4j-configuration-self-managed.md | 2 +- deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md | 1 + deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md | 1 + .../monitor/stack-monitoring/elastic-cloud-stack-monitoring.md | 1 + .../stack-monitoring/elasticsearch-monitoring-self-managed.md | 1 + ...s_connect_to_an_external_monitoring_elasticsearch_cluster.md | 1 + .../monitor/stack-monitoring/kibana-monitoring-self-managed.md | 2 +- 7 files changed, 7 insertions(+), 2 deletions(-) diff --git a/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md b/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md index 0842231f9..bafe2b82c 100644 --- a/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md +++ b/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md @@ -5,7 +5,7 @@ applies: stack: all --- -# Elasticsearch log4j configuration (self-managed) [logging] +# Elasticsearch log4j configuration [logging] You can use {{es}}'s application logs to monitor your cluster and diagnose issues. If you run {{es}} as a service, the default location of the logs varies based on your platform and installation method: diff --git a/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md index c723bb29a..5aa4f0c63 100644 --- a/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/ece-stack-monitoring.md @@ -1,4 +1,5 @@ --- +navigation_title: "Elastic Cloud Enterprise (ECE)" mapped_pages: - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-enable-logging-and-monitoring.html applies: diff --git a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md index 12eeabee2..5bbeafacd 100644 --- a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md @@ -1,4 +1,5 @@ --- +navigation_title: "Elastic Cloud on Kubernetes (ECK)" mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-stack-monitoring.html applies: diff --git a/deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md index ac8929def..d75c8fff2 100644 --- a/deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/elastic-cloud-stack-monitoring.md @@ -1,4 +1,5 @@ --- +navigation_title: "Elastic Cloud Hosted (ECH)" mapped_urls: - https://www.elastic.co/guide/en/cloud-heroku/current/ech-monitoring.html - https://www.elastic.co/guide/en/cloud/current/ec-monitoring-setup.html diff --git a/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md b/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md index 56238289a..5d7c38ad5 100644 --- a/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md +++ b/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md @@ -1,4 +1,5 @@ --- +navigation_title: "Elasticsearch self-managed" mapped_urls: - https://www.elastic.co/guide/en/elasticsearch/reference/current/monitoring-production.html - https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-monitoring.html diff --git a/deploy-manage/monitor/stack-monitoring/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.md b/deploy-manage/monitor/stack-monitoring/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.md index 9fe2e4398..a730bb4a7 100644 --- a/deploy-manage/monitor/stack-monitoring/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.md +++ b/deploy-manage/monitor/stack-monitoring/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.md @@ -1,4 +1,5 @@ --- +navigation_title: "Connect to an external cluster" mapped_pages: - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s_connect_to_an_external_monitoring_elasticsearch_cluster.html applies: diff --git a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md index 7860161cb..62b1e8e93 100644 --- a/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md +++ b/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md @@ -1,5 +1,5 @@ --- -navigation_title: "Kibana monitoring self-managed" +navigation_title: "Kibana self-managed" mapped_pages: - https://www.elastic.co/guide/en/kibana/current/configuring-monitoring.html applies: