> For the complete documentation index, see [llms.txt](https://truweathersolutions.gitbook.io/info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://truweathersolutions.gitbook.io/info/documentation/web-based-user-interface/alerts.md).
# Alerts
The Alerts section provides automated notifications when weather conditions meet user-defined thresholds. Alerts can be configured from gridded datasets, which monitor conditions across a user-defined area, and sensor-based observations, which track conditions at specific selected sensors. This provides users with hands-off monitoring of critical weather data and situational awareness changing conditions.
### Area Based Alerts
{% stepper %}
{% step %}
Expand the **Alerts menu** by clicking on it on the left side of the screen.
{% endstep %}
{% step %}
Select **Create an Alert** under the expansion.
{% endstep %}
{% step %}
Utilize the **Alert creation menu** at the top of the map denoted by a downward facing arrow. This menu will go through the 4 steps to create an area-based alert
1. Name and Event Timeline
1. Use the **Event Name field** to give the event a name desired by the user
2. Use the **Start Time field** to identify the desired start of notifications
3. Use the **End Time field** to identify the desired end time of notifications
4. Select **Next**
2. Location Selection
1. Option 1: Select **Map Area**, then utilize the polygon tool as utilized in the RouteCast section. Once drawn, go back to the **Alert creation menu**, then select **Next**
2. Option 2: Use **Selected Location**, then select **Next**. This will allow the user to later define a radius ring around the current location selected.
3. Notification Selection
1. Fill in **available fields** with email addresses the user wishes to receive notifications.
2. Select **Next**
4. Hazard Selection
1. Use the **check boxes** on the left side of the Alert creation menu to add weather parameters that will be included in the alerts
2. For each weather parameter **identify** a threshold value, comparison (<, =, >, etc.), and threshold units
3. If Selected location was used in step 2, set distance and distance units for the radius around the selected location
4. Select **Submit**
{% endstep %}
{% step %}
All emails identified on the notification list will receive an alert activation email and subsequent emails notifying thresholds that are crossed.
{% endstep %}
{% endstepper %}
### Sensor Alerts
{% stepper %}
{% step %}
Expand the **observations menu** by clicking on it on the left side of the screen.
{% endstep %}
{% step %}
Toggle on **Surface Observations** or **Elevated Sensors**.
{% endstep %}
{% step %}
Click on any sensor on the map where sensor details appear.
{% endstep %}
{% step %}
Click the Alert button in the top right corner to turn on/off alerts for that sensor.
{% endstep %}
{% step %}
All sensor alert thresholds will be based off the high-risk category of the customer thresholds set under the user profile.
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://truweathersolutions.gitbook.io/info/documentation/web-based-user-interface/alerts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
as utilized in the RouteCast section. Once drawn, go back to the **Alert creation menu**, then select **Next**
2. Option 2: Use **Selected Location**, then select **Next**. This will allow the user to later define a radius ring around the current location selected.
3. Notification Selection
in the top right corner to turn on/off alerts for that sensor.
