[jira] [Updated] (IGNITE-17989) JVM memory usage metric source
[ https://issues.apache.org/jira/browse/IGNITE-17989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey N. Gura updated IGNITE-17989: Epic Link: (was: IGNITE-17353) > JVM memory usage metric source > -- > > Key: IGNITE-17989 > URL: https://issues.apache.org/jira/browse/IGNITE-17989 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta1 > > Time Spent: 10m > Remaining Estimate: 0h > > h3. Motivation > It will be useful to have builtin metric source with jvm memory usage stats. > h3. Definition of Done > It must expose the following metrics as a separate gauge metric each: > * heap memory usage (init/used/commited/max) > * non-heap memory usage (init/used/commited/max) > * name of metrics should have the general prefix "jvm." to group all future > jvm metrics together > Also, it needs to check, if calculation of these stats is heavy and we need > to cache it for some time windows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17989) JVM memory usage metric source
[ https://issues.apache.org/jira/browse/IGNITE-17989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Lukyanov updated IGNITE-17989: Fix Version/s: 3.0.0-beta1 (was: 3.0.0-beta2) > JVM memory usage metric source > -- > > Key: IGNITE-17989 > URL: https://issues.apache.org/jira/browse/IGNITE-17989 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta1 > > Time Spent: 10m > Remaining Estimate: 0h > > h3. Motivation > It will be useful to have builtin metric source with jvm memory usage stats. > h3. Definition of Done > It must expose the following metrics as a separate gauge metric each: > * heap memory usage (init/used/commited/max) > * non-heap memory usage (init/used/commited/max) > * name of metrics should have the general prefix "jvm." to group all future > jvm metrics together > Also, it needs to check, if calculation of these stats is heavy and we need > to cache it for some time windows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17989) JVM memory usage metric source
[ https://issues.apache.org/jira/browse/IGNITE-17989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-17989: - Reviewer: Vyacheslav Koptilin > JVM memory usage metric source > -- > > Key: IGNITE-17989 > URL: https://issues.apache.org/jira/browse/IGNITE-17989 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > h3. Motivation > It will be useful to have builtin metric source with jvm memory usage stats. > h3. Definition of Done > It must expose the following metrics as a separate gauge metric each: > * heap memory usage (init/used/commited/max) > * non-heap memory usage (init/used/commited/max) > * name of metrics should have the general prefix "jvm." to group all future > jvm metrics together > Also, it needs to check, if calculation of these stats is heavy and we need > to cache it for some time windows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17989) JVM memory usage metric source
[ https://issues.apache.org/jira/browse/IGNITE-17989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-17989: - Fix Version/s: 3.0.0-beta2 > JVM memory usage metric source > -- > > Key: IGNITE-17989 > URL: https://issues.apache.org/jira/browse/IGNITE-17989 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > h3. Motivation > It will be useful to have builtin metric source with jvm memory usage stats. > h3. Definition of Done > It must expose the following metrics as a separate gauge metric each: > * heap memory usage (init/used/commited/max) > * non-heap memory usage (init/used/commited/max) > * name of metrics should have the general prefix "jvm." to group all future > jvm metrics together > Also, it needs to check, if calculation of these stats is heavy and we need > to cache it for some time windows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17989) JVM memory usage metric source
[ https://issues.apache.org/jira/browse/IGNITE-17989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov updated IGNITE-17989: Epic Link: IGNITE-17353 > JVM memory usage metric source > -- > > Key: IGNITE-17989 > URL: https://issues.apache.org/jira/browse/IGNITE-17989 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > h3. Motivation > It will be useful to have builtin metric source with jvm memory usage stats. > h3. Definition of Done > It must expose the following metrics as a separate gauge metric each: > * heap memory usage (init/used/commited/max) > * non-heap memory usage (init/used/commited/max) > * name of metrics should have the general prefix "jvm." to group all future > jvm metrics together > Also, it needs to check, if calculation of these stats is heavy and we need > to cache it for some time windows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17989) JVM memory usage metric source
[ https://issues.apache.org/jira/browse/IGNITE-17989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-17989: - Description: h3. Motivation It will be useful to have builtin metric source with jvm memory usage stats. h3. Definition of Done It must expose the following metrics as a separate gauge metric each: * heap memory usage (init/used/commited/max) * non-heap memory usage (init/used/commited/max) * name of metrics should have the general prefix "jvm." to group all future jvm metrics together Also, it needs to check, if calculation of these stats is heavy and we need to cache it for some time windows. was: It will be useful to have builtin metric source with jvm memory usage stats. It must expose the following metrics as a separate gauge metric each: * heap memory usage (init/used/commited/max) * non-heap memory usage (init/used/commited/max) * name of metrics should have the general prefix "jvm." to group all future jvm metrics together Also, it needs to check, if calculation of these stats is heavy and we need to cache it for some time windows. > JVM memory usage metric source > -- > > Key: IGNITE-17989 > URL: https://issues.apache.org/jira/browse/IGNITE-17989 > Project: Ignite > Issue Type: Task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > h3. Motivation > It will be useful to have builtin metric source with jvm memory usage stats. > h3. Definition of Done > It must expose the following metrics as a separate gauge metric each: > * heap memory usage (init/used/commited/max) > * non-heap memory usage (init/used/commited/max) > * name of metrics should have the general prefix "jvm." to group all future > jvm metrics together > Also, it needs to check, if calculation of these stats is heavy and we need > to cache it for some time windows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
