Error gatus exec /gatus: argument list too long

[babreu-technisys]

Good day.

I am implementing Gatus in a company I work with and we have a large number of services, but it seems that there is a limit, because I am experiencing the following error when I try to add more endpoints in the config.xml

exec /gatus: argument list too long

Could someone help me?

metrics: true
alerting:
  slack:
    webhook-url: "xxxxx"

endpoints:
  - name: Informacion del ID Cliente
    alerts:
    - type: slack
      enabled: true
      failure-threshold: 1
      success-threshold: 2
      description: "healthcheck failed 1 times in a row"
      send-on-resolved: true
    conditions:
    - "[STATUS] == any(200, 400)"
    - "[RESPONSE_TIME] < 2000"
    group: servicios-banesco.general
    interval: 20s
    name: Informacion del ID Cliente - xxxxx
    method: GET
    url: xxxx
    headers:
      Authorization: secret

[TwiN]

You mentioned config.xml - did you mean config.yaml?

And how many endpoints do you have in your file? Or how large is your file if there's too many to count?

Have you tried removing a few to see when it stopped working?

Have you tried using separate config files?

[babreu-technisys]

This, config.yaml

I have 50 endpoints, I noticed that when the error occurs, I remove half of the file, gatus starts working again, then I put what I removed back in, and it works normally, but every time I add a new endpoint, I have to do this procedure.

Have you tried using separate config files? - I didn't try.
Have you tried removing a few to see when it stopped working? --- if i remove some it works again
And how many endpoints do you have in your file? Or how large is your file if there's too many to count? -- file has 1220 lines

[TwiN]

I'd suggest you try creating multiple separate config files to start off.

From the docs:

By default, the configuration file is expected to be at config/config.yaml.

You can specify a custom path by setting the GATUS_CONFIG_PATH environment variable.

If GATUS_CONFIG_PATH points to a directory, all *.yaml and *.yml files inside said directory and its subdirectories are merged like so:

• All maps/objects are deep merged (i.e. you could define alerting.slack in one file and alerting.pagerduty in another file)
• All slices/arrays are appended (i.e. you can define endpoints in multiple files and each endpoint will be added to the final list of endpoints)
• Parameters with a primitive value (e.g. metrics, alerting.slack.webhook-url, etc.) may only be defined once to forcefully avoid any ambiguity
  • To clarify, this also means that you could not define alerting.slack.webhook-url in two files with different values. All files are merged into one before they are processed. This is by design.