If you can control the output format of the metrics you want to monitor, you can use the generic Eyer format described below without mapping.

  1. All fields are mandatory

  2. Node type should not contain spaces. Make sure it is in the format shown in the example

  3. Timestamp should be in UNIX format

  4. Aggreations allowed

    1. avg

    2. max

    3. sum

In the example below, we have

  1. A server (“Server 1”)

    1. where we monitor a hard drive (“HD 1”) with two metrics

      1. I/O

      2. Utilization

    2. we monitor CPU (“CPU 1”) with a single metric

      1. Usage

We output the metrics in the format below

{
    "metrics":
    [
        {
            "Generic": "HD 1",
            "Time": 1742548364.3714607,
            "Timestamp": 1742548364,
            "NodeType": "server.disk",
            "StatType": "I/O",
            "System": "Server 1",
            "Value": 10,
            "Aggregation": "avg"
        },
        {
            "Generic": "HD 1",
            "Time": 1742548364.3714607,
            "Timestamp": 1742548364,
            "NodeType": "server.disk",
            "StatType": "Utilization",
            "System": "Server 1",
            "Value": 12976534,
            "Aggregation": "avg"
        },
        {
            "Generic": "CPU 1",
            "Time": 1742548364.3714607,
            "Timestamp": 1742548364,
            "NodeType": "server.cpu",
            "StatType": "Usage",
            "System": "Server 1",
            "Value": 34,
            "Aggregation": "avg"
        }
    ]
}

You can of course add additional HDs by replacing HD 1 with HD 2 etc. Same with CPU or other sections connected to a server (network cards, memory and more).

Once you have the output ready, ship an example to us (contact us via the support email or on Discord) and we will enable your endpoint