Graylog: Configure email notifications
This documentation is part of the Alerting guide. View the full guide here: How to send Graylog alerts by email, Slack, or Mattermost.
👋 Welcome to the Stackhero documentation!
Stackhero offers a ready-to-use Graylog cloud solution that provides a host of benefits, including:
- Unlimited and dedicated SMTP email server included.
- Effortless updates with just a click.
- Customizable domain name secured with HTTPS (for example, https://logs.your-company.com).
- Optimal performance and robust security powered by a private and dedicated VM.
Save time and simplify your life: it only takes 5 minutes to try Stackhero's Graylog cloud hosting solution!
Every Graylog instance provided by Stackhero includes a built-in email server, allowing you to send unlimited emails directly from your instance at no additional cost.
To set up an email notification, you might consider following these steps:
-
Access your Graylog service, navigate to
Alerts>Notifications, and click theGet started!button or opt forCreate notification. -
Enter a title for your notification and choose
Email NotificationunderNotification type. -
In the
Senderfield, inputnoreply@<yourGraylogDomain>. Remember to replace<yourGraylogDomain>with your actual Graylog domain name, typically formatted as<XXXXXX>.stackhero-network.com.Important: Ensure you use your Graylog domain to avoid errors when sending emails.
-
Specify the email address where you would like to receive alerts in the
Email recipientfield.
Example of email configuration -
Click the
Execute test notificationbutton to verify that everything functions correctly. Once confirmed, complete the setup by clickingCreate.
Congratulations! Your email notification is now established and operational!
Handling the error: "Sending the email to the following server failed: postfix:25"
Should you encounter the error Error: Notification has email recipients and is triggered, but sending emails failed. Sending the email to the following server failed: postfix:25, it is likely because the sender input is not correctly formatted. It should follow the pattern <something>@<yourGraylogDomain>. "Something" is flexible (like "noreply"), but "yourGraylogDomain" must reflect your Graylog service domain, usually presented as <XXXXXX>.stackhero-network.com.