[ https://issues.apache.org/jira/browse/IGNITE-18183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Pochatkin updated IGNITE-18183: --------------------------------------- Component/s: rest > Rest endpoint for all node metrics > ---------------------------------- > > Key: IGNITE-18183 > URL: https://issues.apache.org/jira/browse/IGNITE-18183 > Project: Ignite > Issue Type: Task > Components: ignite-3, rest > Reporter: Stepachev Maksim > Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > *The problem:* > The ignite 3 rest of clusters will usually be hided behind a load balancer, > as result we aren't able to get a particular node metrics. In this task is > required to develop an endpoint at your discretion that will extract metrics > from all nodes by one call. > *Possible path at your wish:* > * /all-nodes/metrics > * {{/node/all/metrics}} - query all nodes (like {{all-nodes}} above) > * {{/node/12345678-1234-1234-1234-12345678/metrics}} - query that particular > node even if we happen to connect to a different one{{{}{}}} > * {{/node/local/metrics}} - query the node we connected to > *Please look at these examples of other databases:* > * > [https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-stats.html] > * > [https://docs.spring.io/spring-boot/docs/current/actuator-api/htmlsingle/#metrics] > * [https://micronaut-projects.github.io/micronaut-micrometer/latest/guide/] > * Etc. > It would be good if we could add filters to get specific sets of metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)