Monitor value retry_interval does not propogate to retryInterval

[instantdreams]

Using the static configuration and a json file with the following entry:

    {
        "name": "edge1.node-exporter-1",
        "parent_name": "static/groups[0]",
        "type": "http",
        "url": "http://192.168.1.91:9100",
        "interval": 240,
        "max_retries": 2,
        "retry_interval": 240,
        "tag_names":
        [
            {
                "name": "static/tags[5]",
                "value": ""
            },
            {
                "name": "static/tags[1]",
                "value": ""
            }
        ]
    }

The following is created and returned by kuma cli:

  "128": {
    "type": "http",
    "id": 128,
    "name": "edge1.node-exporter-1",
    "interval": 240,
    "active": true,
    "maxretries": 2,
    "retryInterval": 60,
    "upsideDown": false,
    "parent": 4,
    "tags": [
      {
        "tag_id": 4,
        "name": "direct",
        "color": "#FF00FF",
        "value": ""
      },
      {
        "tag_id": 8,
        "name": "internal",
        "color": "#DE2348",
        "value": ""
      }
    ],
    "notificationIDList": {},
    "accepted_statuscodes": [
      "200-299"
    ],
    "url": "http://192.168.1.91:9100",
    "timeout": 48,
    "resendInterval": 0,
    "expiryNotification": true,
    "ignoreTls": false,
    "maxredirects": 10,
    "method": "GET"
  },

Input Key: retry_interval
Input Value: 240

Output Key: retryInterval
Output Value: 60 (default)

[BigBoot]

Btw you can always use the uptime-kuma "native" property names (i.e. what kuma cli returns), the snake case names are a manually curated mapping because the original names are a wild mix of different casings and sometimes even completely wrong.