Whether you're a developer or a fleet operator, you're likely to run into unexpected problems. Generating an alert captures the time, data, and description of the issue so you and your team can figure out how to fix it.
Choosing appropriate alert levels is important to help your team prioritize issues and avoid being overwhelmed with unnecessary notifications. Here are some rules of thumb:
Something unrecoverable has happened, requiring immediate attention of the team.
Something unrecoverable has happened, but does not require escalation to the full team.
Information that the user may find alarming, and may affect the output of the application.
Interesting information to track, but does not require immediate operator intervention.
Bottom line: Use
ERROR sparingly to avoid generating unnecessary alerts that are forwarded to email, Slack, and other integrated services.
Let's manually generate an alert for your robot. Navigate to your device and click + Incident in the left sidebar.
For this example, we'll report a BATTERY ISSUE with a title of BATTERY FAILURE. Write a brief description, then choose a severity level of FATAL to indicate that the robot is not functional.
Click REPORT. That's it! You've now generated your first alert.
By default, we enable email notifications to the address associated with your account for alerts of level
INFO and higher. You'll receive a message in your inbox shortly describing the alert!
In the Integrations section of this guide, we'll walk through how to customize these settings and connect other services.
Updated almost 2 years ago