Graylog: Configuring email notifications

This documentation is part of the Alerting guide. You can view the complete 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 comes with a built-in email server, allowing you to send unlimited emails directly from your instance at no extra cost.

To set up an email notification, you can follow these steps:

  1. Access your Graylog service, go to Alerts > Notifications, and click the Get started! button or select Create notification.

  2. Enter a title for your notification and select Email Notification under Notification type.

  3. In the Sender field, enter noreply@<yourGraylogDomain>. Make sure to replace <yourGraylogDomain> with your actual Graylog domain name, which is usually in the format <XXXXXX>.stackhero-network.com.

    Important: Be sure to use your Graylog domain to avoid errors when sending emails.

  4. Enter the email address where you want to receive alerts in the Email recipient field.

    Example of email configurationExample of email configuration

  5. Click the Execute test notification button to check that everything is working properly. Once the test is successful, complete the setup by clicking Create.

Congratulations! Your email notification is now configured and operational!

If 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 likely means the sender field is not properly formatted. It should follow the pattern <something>@<yourGraylogDomain>. "Something" can be anything (for example, "noreply"), but "yourGraylogDomain" must match your Graylog service domain, usually in the form <XXXXXX>.stackhero-network.com.