[
https://issues.apache.org/jira/browse/UIMA-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-5047:
--------------------------------
Description:
Currently agent fetches metrics from different sources including /proc file
system, top, ps, etc. The files found in /proc file system don't have fixed
structure across Linux platforms causing some metrics to be missing or be
wrong. Also scrapping lnx commands may not be 100% reliable as well
Change the code to fetch metrics from cgroups. Where to get metrics not
available in cgroups is an open question.
For reporting the CPU, the agent needs to look at cgroups cpuacct.stat file and
use the values for reporting. The agent should keep previous reading and use it
to compute delta for the "current" CPU. Agent should not scrape top to get the
current CPU use.
In case cgroups are not available, the agent will provide 0 or N/A for metrics
which should come from cgroups.
was:
Currently agent fetches metrics from different sources including /proc file
system. The files found in /proc file system don't have fixed structure across
Linux platforms causing some metrics to be missing or be wrong.
Change the code to find an alternate way to get needed metrics from sources
that are more reliable.
Use cgroups cpu and memory accounting when cgroups are enabled. In case when
cgroups are not enabled provide 0 or N/A as values.
> UIMA-DUCC: refactor agent code which gathers node and process metrics
> ---------------------------------------------------------------------
>
> Key: UIMA-5047
> URL: https://issues.apache.org/jira/browse/UIMA-5047
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.2.0-Ducc
>
>
> Currently agent fetches metrics from different sources including /proc file
> system, top, ps, etc. The files found in /proc file system don't have fixed
> structure across Linux platforms causing some metrics to be missing or be
> wrong. Also scrapping lnx commands may not be 100% reliable as well
> Change the code to fetch metrics from cgroups. Where to get metrics not
> available in cgroups is an open question.
> For reporting the CPU, the agent needs to look at cgroups cpuacct.stat file
> and use the values for reporting. The agent should keep previous reading and
> use it to compute delta for the "current" CPU. Agent should not scrape top to
> get the current CPU use.
> In case cgroups are not available, the agent will provide 0 or N/A for
> metrics which should come from cgroups.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
