You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2022/11/01 16:50:00 UTC
[jira] [Commented] (IGNITE-17989) JVM memory usage metric source
[ https://issues.apache.org/jira/browse/IGNITE-17989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627247#comment-17627247 ]
Vyacheslav Koptilin commented on IGNITE-17989:
----------------------------------------------
LGTM
> 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
>
> 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)