Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Health API returns details and diagnosis in non-verbose mode #108175

Open
consulthys opened this issue May 2, 2024 · 1 comment · May be fixed by #108233
Open

Health API returns details and diagnosis in non-verbose mode #108175

consulthys opened this issue May 2, 2024 · 1 comment · May be fixed by #108233
Labels

Comments

@consulthys
Copy link
Contributor

Elasticsearch Version

8.13.2

Installed Plugins

Java Version

bundled

OS Version

ES Cloud

Problem Description

According to the official documentation of the Health API, when hitting the _health_report API endpoint with ?verbose=false, there should be no details or diagnosis included in the response.

However, it's not the case as depicted below:

  • shards_capacity has the same output whether verbose is true or false
  • ilm returns diagnosis whether verbose is true or false
GET _health_report?verbose=false&filter_path=**.details,**.diagnosis
=>
{
  "indicators": {
    "shards_capacity": {
      "details": {
        "data": {
          "max_shards_in_cluster": 3000
        },
        "frozen": {
          "max_shards_in_cluster": 0
        }
      }
    },
    "ilm": {
      "diagnosis": [
        {
          "id": "elasticsearch:health:ilm:diagnosis:stagnating_action:migrate",
          "cause": "Some indices have been stagnated on the action [migrate] longer than the expected time.",
          "action": "Check the current status of the Index Lifecycle Management for every affected index using the [GET /<affected_index_name>/_ilm/explain] API. Please replace the <affected_index_name> in the API with the actual index name.",
          "help_url": "https://ela.st/ilm-explain",
          "affected_resources": {
            "ilm_policies": [
              "elastic-cloud-logs",
              "metricbeat"
            ],
            "indices": [
              ".ds-elastic-cloud-logs-8-2024.04.17-000005",
              ".ds-elastic-cloud-logs-8-2024.04.26-000011",
              ".ds-metricbeat-8.11.1-2023.12.19-000001",
              ".ds-metricbeat-8.11.1-2024.01.18-000002",
              ".ds-metricbeat-8.12.0-2024.01.18-000001",
              ".ds-metricbeat-8.12.0-2024.02.17-000002",
              ".ds-metricbeat-8.12.2-2024.03.11-000001",
              ".ds-metricbeat-8.13.0-2024.03.26-000001",
              ".ds-metricbeat-8.13.0-2024.04.26-000003",
              ".ds-metricbeat-8.13.2-2024.04.10-000001",
              ".ds-metricbeat-8.13.2-2024.04.26-000003"
            ]
          }
        }
      ]
    }
  }
}

Steps to Reproduce

  1. Hit GET _health_report?verbose=false&filter_path=**.details,**.diagnosis
  2. The response should be empty

Logs (if relevant)

No response

@consulthys consulthys added >bug needs:triage Requires assignment of a team area label labels May 2, 2024
@dakrone dakrone added :Data Management/Health and removed needs:triage Requires assignment of a team area label labels May 2, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Data Management Meta label for data/management team label May 2, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants