forked from Dark0096/graphene
-
Notifications
You must be signed in to change notification settings - Fork 4
Metric Key
dark edited this page Jan 1, 2020
·
9 revisions
In the following article, you can find out how each open source metric expresses metric which is server1's CPU Usage and how it indexes to graphene key store handler:
Graphite 9.x or 1.x : servers.server1.cpu.usage
{
"_id" : "NONE_servers.server1.cpu.usage",
"0" : "servers",
"1" : "server1",
"2" : "cpu",
"3" : "usage",
"depth" : 4,
"leaf": true
}
Graphite 1.1.x Tag : cpu.usage;servers=server1
{
"_id": "cpu.usage;servers=server1",
"servers" : "server1",
"name" : "cpu.usage"
}
Prometheus : cpu_usage{servers="server1"} 10
{
"_id": "cpu_usage;servers=server1",
"servers" : "server1",
"metric" : "cpu_usage"
}
InfluxDB : cpu,servers=server1, usage=10 => TagBasedKeyStoreHandler
{
"_id": "cpu.usage;servers=server1",
"@name": "cpu.usage",
"servers": "server1"
}
How to search both of them which were influxDB, graphite and prometheus metric: If you want to use graphite tag metric with influxDB, add the measurement tag key.
Graphite Tag : usage;servers=server1;measurement=cpu
{
"_id": "NONE;cpu;servers=server1",
"@source" : "graphite",
"@measurement": "cpu",
"server" : "server1",
"cpu": [{
"metric" : "usage"
}]
}