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

Report elasticcloud data tiers nodes roles #651

Closed
christophemorio opened this issue Nov 17, 2022 · 0 comments · Fixed by #652
Closed

Report elasticcloud data tiers nodes roles #651

christophemorio opened this issue Nov 17, 2022 · 0 comments · Fixed by #652

Comments

@christophemorio
Copy link
Contributor

Hello,

On ElasticCloud clusters, nodes have specific roles regarding data tier leveling:

  • data_hot
  • data_warm
  • data_cold
  • data_frozen
GET /_nodes/stats
...
      "roles": [
        "master",
        "remote_cluster_client"
      ],
...
      "roles": [
        "data_frozen"
      ],
...
      "roles": [
        "data_content",
        "data_hot",
        "ingest",
        "remote_cluster_client",
        "transform"
      ],
...
      "roles": [
        "data_warm",
        "remote_cluster_client"
      ],
 ...
      "roles": [
        "data_cold",
        "remote_cluster_client"
      ],

In ElasticCloud setup, metrics elasticsearch_nodes_roles reports only master, client and ingest.

$ curl -s http://localhost:9108/metrics | grep 'elasticsearch_nodes_roles'
# HELP elasticsearch_nodes_roles Node roles
# TYPE elasticsearch_nodes_roles gauge
elasticsearch_nodes_roles{cluster="xxxx",host="172.22.138.46",name="instance-0000000016",role="client"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.22.138.46",name="instance-0000000016",role="ingest"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.22.143.78",name="instance-0000000015",role="client"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.22.143.78",name="instance-0000000015",role="ingest"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.236.46",name="instance-0000000003",role="client"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.238.200",name="instance-0000000019",role="client"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.238.200",name="instance-0000000019",role="master"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.241.205",name="instance-0000000021",role="client"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.241.47",name="instance-0000000022",role="client"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.242.154",name="instance-0000000018",role="client"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.242.154",name="instance-0000000018",role="master"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.242.162",name="instance-0000000007",role="client"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.245.96",name="instance-0000000020",role="client"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.245.96",name="instance-0000000020",role="master"} 1
elasticsearch_nodes_roles{cluster="xxxx",host="172.25.246.94",name="instance-0000000010",role="client"} 1

Roles data_* are required to set proper alerts.
e.g. data_frozen reporting full disk usage is likely to less critical since it's only for caching.

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

Successfully merging a pull request may close this issue.

1 participant