> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/bmc-user-guide/configuration/alerts-and-notifications.md).
# Alerts and Notifications
A server that can report its own problems is a massive advantage in any IT environment. Instead of discovering an issue only after a service has failed, the BMC can proactively send you an alert the moment a hardware fault is detected.
This chapter shows you how to set up email alerts via SMTP and how to define which specific hardware events should trigger those alerts.
## **Setting up SMTP for email alerts**
Simple Mail Transfer Protocol (SMTP) is the standard method for sending emails. By configuring the BMC to use your organization's mail server, you can have it send detailed alert messages directly to your inbox or a team distribution list. The BMC supports both a primary and a secondary (backup) SMTP server for redundancy.
1. In the sidebar menu, navigate to **Settings** > **SMTP Settings**.
2. Enable the **Primary Configuration** toggle.
3. Fill in the server details:
* **Server Address**: The IP address or hostname of your mail server.
* **Port**: The port your mail server uses (e.g., 25 for standard SMTP, 465 for SMTPS, or 587 for submission).
* **Sender Email Address**: The "From" address that alerts will be sent from.(e.g., `bmc-alerts@yourcompany.com`).
* **Recipient Email Address**: The destination inbox. You can add up to four recipients.
4. If your mail server requires a login, enable **Authentication** and enter the **Username** and **Password**.
5. If your server uses encryption, enable **TLS Enable** and upload the required certificate files (`Cacert.pem`, `Server.crt`, `Server.key`).
6. Click **Save settings**.
{% hint style="info" %}
**Pro Tip: Use a dedicated service account**
For security and manageability, it's a best practice to create a dedicated service account (e.g., `srv-bmc-alerts@yourcompany.com`) for the BMC to use. Avoid using personal email accounts for authentication, as this can create a security risk if the person leaves the organization.
{% endhint %}
After saving, click the **Send Test Alert** button to verify that the configuration is working correctly.
## **Configuring platform event filters**
Once SMTP is set up, you need to tell the BMC *which* events are important enough to trigger an email alert. This is done using Platform Event Filters.
1. In the sidebar menu, navigate to **Platform Event Filter**.
2. You will see a list of hardware-level event triggers.
3. Enable the toggles for the events you want to be notified about.
Available filters typically include:
* **Temperature Sensor Out of Range**: Get an alert if the server is overheating. (Highly Recommended)
* **Voltage Sensor Out of Range**: Be notified of potential power supply or motherboard issues. (Highly Recommended)
* **Processor Presence**: Detects if a CPU has failed or is missing.
* **Watchdog Timer**: Triggers an alert if the operating system freezes and fails to reset the watchdog timer. This is a strong indicator of a system hang.
Click **Save settings** to apply your choices.
---
# 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://doc.engenius.ai/bmc-user-guide/configuration/alerts-and-notifications.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.
