Monitor alerts history

Within the Redox dashboard, you can monitor the alerts we send about an endpoint not receiving the expected patient data. Monitoring alerts can help you track where or how the issue happened. You can also see alerts sent to your connection's systems about endpoints you're sending to.

If you opt in for email notifications, you can also check your inbox, but the Monitoring page allows you to view historical alerts without having to worry about missing an email or digging through your inbox. Currently, we support viewing alerts for issues with a VPN heartbeat or log failure for up to 60 days in the past.

You can also view these alerts as they happen real-time by checking an endpoint's status.

To monitor your alerts in a production environment, follow these instructions.

  1. Log in to the Redox dashboard.
  2. From the navigation menu, click the Monitoring page.
  3. By default, the Alerts History tab opens and any alerts from the last 60 days display.
    Navigate to the Alerts History tab
    Navigate to the Alerts History tab

    Only for production environments

    Keep in mind that alert history is only available for production environments. If you navigate to the Monitoring page in a development or staging environment, this warning appears.

  4. If you want to narrow down the displayed alerts, use the filters at the top of the page.
    1. Alerting organization: By default, this is set to Any. To filter alerts for a particular organization, click the drop-down field and select the desired organization name. In the drop-down list, your organization appears as the first option and any organizations you're connected to display below. You can only select one organization if you're using filters.
    2. Alert type: Set to Any by default. To filter by alert type, click the drop-down field and select either Log Failure (read about message failures and retries) or VPN Heartbeat Failure (read about VPN tests and failures)
    3. Date range: By default, the date range filter is empty. To filter by the timestamp that the alert was triggered (not resolved), select a start date up to 60 days prior and end date.
    4. Status: Set to Any by default. To filter by alert status, click the drop-down field and select either Resolved (the issue was fixed) or Triggered (the issue is active and ongoing).
      Alerts filters
      Alerts filters
  5. The filtered alerts display with their details.
    1. Alerting organization: Displays the name of the organization where the alert was triggered. This is also the organization that would've received the alert notification via email. The alert type displays below the organization name.
    2. Related links: Displays links to logs or other related information for more details. Currently, links are only provided for log failures.
    3. Data flow: Provides links to the relevant traffic details based on the alert type. Log Failure links take you to the Data Flow page while VPN Heartbeat Failure links take you to the related Endpoint page.
    4. Error status: Displays the current alert status, which is either triggered (active alert) or resolved.
    5. Timestamp: Displays the date/time that the alert was triggered.


If you want to troubleshoot any active alerts, check out our troubleshooting recommendations.