| Info |
|---|
Eyer will work on any time-series data (metric + timestamp). You can connect open source agents like Influx Telegraf or Prometheus to support your technologies and applications, and you can also create custom agents / scripts that feed time-series data to Eyer. To connect your custom data, you need to create a mapping from your source data to the Eyer internal format. |
Requirements
Your data (from open source agent / custom agent / script) output must be in JSON format
Eyer currently only support metrics, not logs. If you work on logs, you can convert information of interest to metrics (e.g. number of errors matching a certain regex condition).
The metrics must have a timestamp in UNIX format (typically the time of metric collection)
The data must be mapped to the Eyer internal data structure (Node/metrics)
Input data example (coming from Influx Telegraf)
The example below uses Influx Telegraf to collect some database metrics, and send them over HTTPS to the Eyer API. What you see below is the JSON sent from Influx Telegraf. The “fields” section can repeat, so a request can contain metrics from multiple database servers.
| Code Block | ||
|---|---|---|
| ||
{
"metrics":
[
{
"fields":
{
"disk_reads_mean": 1.0121461361787716,
"disk_writes_per_sec_mean": 0.8571885607181682,
"last_Run_mean": 1740047577489,
"log_bytes_flushed_mean": 3.9596305549082618,
"logical_reads_mean": 914.9966524003087,
"total_sessions_mean": 14,
"waits_total": 0,
"waits_total_mean": 7.3
},
"name": "dbwatch",
"tags":
{
"host": "testmachine1",
"instance": "Database1",
"url": "http://localhost:8080/dashboard/dbWatch%2001/data/HkRmUaLz0Z.telegraf.json"
},
"timestamp": 1740047760
}
]
} |
Mapping example with explanation
We take the example above, and map it to the Eyer internal format. Below you see the mapping (in JSON) , and then the mapping explained with functions in a table.
...