Relay status (healthcheck failed)

Overview

Devo Relay contains a mechanism that keeps the relay status in sync between the relay machine and the Devo application. The relay status can be checked both from the Devo app and from the relay machine using the command line interface.

Open

Relay statuses

Devo Relay can be in any of the following statuses. After accessing the Devo app, Admin users can check the relay list of the domain and their status in Administration → Relays and ELBs → Relays.

Status	Description

Status	Description
Pending	The setup process is completed but the validation from the web app is still pending. Click the Activate button in the ellipsis menu of the relay to activate it. Learn how to set up a new relay and validate it on the app in Set up your relay. Open
Applying config	The system is applying changes to the relay configuration. New relays will keep this status for a few minutes after being activated on the Devo app.
Active	The relay is active and working correctly.
Healthcheck failed	The relay health-check process failed to send data to Devo and read it afterwards. Please make sure that your relay fits the network requirements.
Inactive	The certificate of the relay has been revoked. In the Devo app, you can do this in Administration → Relays and ELBs → Relays, by clicking the ellipsis menu in a relay row and selecting Deactivate. Open
Stopped	The relay process is stopped.
Deleted	The relay is deleted and will no longer appear on the Devo app relay list.

The following diagram summarizes the relay status workflow and the actions required to move through the different statuses:

Open

Configuration updater

The Config updater process checks every 2 minutes if the relay config has been updated in the Devo application. In case it has, it downloads the new configuration to the relay machine and applies the changes. The relay status will change accordingly. 

Health check

Every two minutes, the health checker will:

1. Send an event to syslog.relay.monitor in Devo.

2. Query syslog.relay.monitor.

After three failed attempts, the relay status will be Error/Healthcheck failed. It will go back to Active after the first successful attempt.

Health check failures indicate one of the two steps was unsuccessful. If a firewall is allowing the relay to send events but blocking queries, then the health check will change the relay to Error. In this scenario, the firewall will allow the relay to forward data normally.

To function, the relay’s network connection must meet the network requirements. To diagnose the problem, check syslog.relay.monitor in Devo.

• If there are events in syslog.relay.monitor with a matching Relay ID, then the relay is unable to reach the query API. In this case, the main relay functionality is working. To resolve the problem, ensure no firewalls block the relay from reaching the query API.

• If there are no events in syslog.relay.monitor but the relay is running, then the relay is unable to reach the event load balancer. In this case, the relay is unable to perform its core functions.

Example of logs every two minutes:

Open