[
https://issues.apache.org/jira/browse/EAGLE-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hao Chen updated EAGLE-928:
---------------------------
Description:
Refine system metric schema design and fix system metric collector
h1. Principle
Any metric (no mater jmx/sys metric) should at least have three fields:
"metric", "group", "timestamp", "value",
"group" is the metric category path separated with slash, for example "FIRST
CATEGORY/SECOND CATEGORY", which will be commonly used for well organizing
metric groups in customized metric dashboard.
h1. Stream Schema for System metric
* *metric*: [STRING] metric name string
* *group*: [STRING] metric group/type
* *timestamp*: [LONG] metric generation time
* *site*: [STRING] siteId
* *host*: [STRING] source host name
* *device*: [STRING] device name, like cpu
h1. Sample CPU Metric
{code}
{
"timestamp": 1487918913569,
"metric": "system.cpu.usage",
"group": "system.cpu",
"site": "sandbox",
"value": 0.058,
"host": "sandbox.hortonworks.com",
"device": "cpu7"
}
{code}
h1. Sample Network Metrics
{code}
{
"timestamp": 1487918913569,
"metric": "system.nic.transmitdrop",
"group": "system.network",
"site": "sandbox",
"value": 7724.0,
"host": "sandbox.hortonworks.com",
"device": "eth0"
}
{code}
h1. Metric Schema
{code}
{
"tags": {
"site": "sandbox",
"name": "system.memory.nfs_unstable.kb",
"group": "system.memory"
},
"dimensionFields": [
"host",
"group",
"site",
"device"
],
"metricFields": [
"value"
],
"granularity": "MINUTE",
"modifiedTimestamp": 1488190388479
}
{code}
was:
Refine system metric schema design and fix system metric collector
h1. Principle
Any metric (no mater jmx/sys metric) should at least have three fields:
"metric", "group", "timestamp", "value",
"group" is the metric category path separated with slash, for example "FIRST
CATEGORY/SECOND CATEGORY", which will be commonly used for well organizing
metric groups in customized metric dashboard.
h1. Stream Schema for System metric
* *metric*: [STRING] metric name string
* *group*: [STRING] metric group/type
* *timestamp*: [LONG] metric generation time
* *site*: [STRING] siteId
* *host*: [STRING] source host name
* *device*: [STRING] device name, like cpu
h1. Sample CPU Metric
{code}
{
"timestamp": 1487918913569,
"metric": "system.cpu.usage",
"group": "system.cpu",
"site": "sandbox",
"value": 0.058,
"host": "sandbox.hortonworks.com",
"device": "cpu7"
}
{code}
h1. Sample Network Metrics
{code}
{
"timestamp": 1487918913569,
"metric": "system.nic.transmitdrop",
"group": "system.network",
"site": "sandbox",
"value": 7724.0,
"host": "sandbox.hortonworks.com",
"device": "eth0"
}
{code}
Hadoop Namenode Metric
{code}
{
"timestamp": 1487918913569,
"metric": "hadoop.namenode.capacity",
"group": "hadoop.namenode",
"site": "sandbox",
"value": 7724.0,
"host": "sandbox.hortonworks.com"
}
{code}
> Refine system metric schema design and fix system metric collector
> ------------------------------------------------------------------
>
> Key: EAGLE-928
> URL: https://issues.apache.org/jira/browse/EAGLE-928
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.5.0
> Reporter: Hao Chen
> Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> Refine system metric schema design and fix system metric collector
> h1. Principle
> Any metric (no mater jmx/sys metric) should at least have three fields:
> "metric", "group", "timestamp", "value",
> "group" is the metric category path separated with slash, for example "FIRST
> CATEGORY/SECOND CATEGORY", which will be commonly used for well organizing
> metric groups in customized metric dashboard.
> h1. Stream Schema for System metric
>
> * *metric*: [STRING] metric name string
> * *group*: [STRING] metric group/type
> * *timestamp*: [LONG] metric generation time
> * *site*: [STRING] siteId
> * *host*: [STRING] source host name
> * *device*: [STRING] device name, like cpu
> h1. Sample CPU Metric
> {code}
> {
> "timestamp": 1487918913569,
> "metric": "system.cpu.usage",
> "group": "system.cpu",
> "site": "sandbox",
> "value": 0.058,
> "host": "sandbox.hortonworks.com",
> "device": "cpu7"
> }
> {code}
> h1. Sample Network Metrics
> {code}
> {
> "timestamp": 1487918913569,
> "metric": "system.nic.transmitdrop",
> "group": "system.network",
> "site": "sandbox",
> "value": 7724.0,
> "host": "sandbox.hortonworks.com",
> "device": "eth0"
> }
> {code}
> h1. Metric Schema
> {code}
> {
> "tags": {
> "site": "sandbox",
> "name": "system.memory.nfs_unstable.kb",
> "group": "system.memory"
> },
> "dimensionFields": [
> "host",
> "group",
> "site",
> "device"
> ],
> "metricFields": [
> "value"
> ],
> "granularity": "MINUTE",
> "modifiedTimestamp": 1488190388479
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)