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

Elasticsearch indexing_pressure metric not in the monitoring mapping #40907

Closed
sachin-frayne opened this issue Sep 19, 2024 · 0 comments · Fixed by elastic/elasticsearch#113175

Comments

@sachin-frayne
Copy link
Contributor

Describe the enhancement:

Add the missing fields related to indexing_pressure into the mapping located in the Elasticsearch repo: https://github.com/elastic/elasticsearch/blob/main/x-pack/plugin/core/template-resources/src/main/resources/monitoring-es-mb.json

Example values:

...
                "indexing_pressure": {
                  "memory": {
                    "total": {
                      "primary": {
                        "rejections": 0,
                        "bytes": 239335086
                      },
                      "coordinating": {
                        "rejections": 0,
                        "bytes": 220495904
                      },
                      "replica": {
                        "rejections": 0,
                        "bytes": 0
                      },
                      "combined_coordinating_and_primary": {
                        "bytes": 220495904
                      },
                      "all": {
                        "bytes": 220495904
                      }
                    },
                    "limit_in_bytes": 27682406,
                    "current": {
                      "coordinating": {
                        "bytes": 0
                      },
                      "replica": {
                        "bytes": 0
                      },
                      "combined_coordinating_and_primary": {
                        "bytes": 0
                      },
                      "all": {
                        "bytes": 0
                      },
                      "primary": {
                        "bytes": 0
                      }
                    }
                  }
                },
...

Since they are all bytes, the field type, long should work.

Describe a specific use case for the enhancement or feature:

To search through the fields they need to be in the mapping.

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