FlorianLautenschlager
commented
7 years ago So i found some time to dig into it using the latest beta release (0.5). Well there is some work to do (documentation, etc.). But the good message is, it works.
With 0.5 we renamed the metric field to name as in Chronix' a time series could be anything.
So let's add some points:
curl -v -H 'Content-Type: application/json' -d '
[
{
"metric":"cablemodem.receive.modem",
"timestamp":1492613453,
"value":"1.6",
"tags":{
"cmts":"192.168.0.254",
"downstream":"cable-downstream-12/1/14",
"hashKey":"57d076563a856e2ad4342a94d59d340ba31c7b8b",
"nodeKey":"9a40b1104cca6375627af9b222898328993de5dd"
}
},
{
"metric":"cablemodem.receive.modem",
"timestamp":1492613853,
"value":"3.2",
"tags":{
"cmts":"192.168.0.254",
"downstream":"cable-downstream-12/1/14",
"hashKey":"57d076563a856e2ad4342a94d59d340ba31c7b8b",
"nodeKey":"9a40b1104cca6375627af9b222898328993de5dd"
}
},
{
"metric":"cablemodem.snr.modem",
"timestamp":1492613453,
"value":"36.8",
"tags":{
"cmts":"192.168.0.254",
"downstream":"cable-downstream-12/1/14",
"hashKey":"57d076563a856e2ad4342a94d59d340ba31c7b8b",
"nodeKey":"9a40b1104cca6375627af9b222898328993de5dd"
}
},
{
"metric":"cablemodem.snr.modem",
"timestamp":1492613853,
"value":"39.8",
"tags":{
"cmts":"192.168.0.254",
"downstream":"cable-downstream-12/1/14",
"hashKey":"57d076563a856e2ad4342a94d59d340ba31c7b8b",
"nodeKey":"9a40b1104cca6375627af9b222898328993de5dd"
}
}
]' http://localhost:8983/solr/chronix/ingest/opentsdb/http/api/putShould end up like this:
{"responseHeader":{"status":0,"QTime":113}}Its important to compact documents in order to increase the performance and storage efficiency.
curl 'http://localhost:8983/solr/chronix/compact?joinKey=name,downstream'Note the joinKey that is used to combine documents. In the example above all documents having the same values in the fields name and downstream are joined into one document. You can add more fields separated by ,.
Important: Currently the IngestionHandler does a commit per request. If you want to import lots of data, you should do large request. I will create an issue to make the commit optional.
With the chronix-timeseries-exploration-0.5-beta we can now ask for data
downstream:"cable-downstream-12/1/14"and apply some functions like
metric{max;count;min}
devaudio
So i am attempting to setup Chronix to ingest mostly opentsdb feeds while waiting to update our legacy applications to use chronix libs natively for imports. One thing i noticed is opentsdb.ingest doesn't support gzipped data incoming (Actual opentsdb api does) but that's not a deal breaker or anything - can prolly have a pull request to remedy that.
My issue is actually having it store/retrieve data --> i've tried several schema for metric tags
previously, i had tried to set it up like your promethus example - have opentsdb 'tags' stored in dynamic field.. but that did not work. Also, the example schema.xml that comes with 0.5.zip did not have the metric/string field.
The grafana plugin just hangs forever, and the java app for exploring doesn't return back info
The opentsdb PUT data looks like this: