You can find full details in the following documentation:

• Monitoring Proxmox VE with Nagios XI

You can find full details in the following documentation:

• Using the Nutanix CE Wizard in Nagios XI

You can learn more in the following documentation:

• Monitoring XCP-ng with Nagios XI 2026

This article provides an overview of key event types which can be used to generate notifications, along with links to related documentation.

Host and Service Event Types

Nagios XI can send you notifications on the following occurrences and state changes:

Host Settings

• Host Acknowledgement – this indicates that a user has acknowledged the current problem with the host, which will either suppress further notifications until the object changes state, or until the object recovers if “Sticky Acknowledgement” is chosen.
• Host Recovery – the host has returned to an OK state from a problem state.
• Host Down – the host is not responding.
• Host Unreachable – the host cannot be reached, because an intermediary parent host which must be routed through to check it is down.
• Host Flapping – this indicates that the state of the host object has fluctuated significantly over the last 21 checks run by Nagios. You can find additional details on the related logic here.
• Host Downtime – the host has been placed in administrative downtime by a user, suppressing notifications.

Service Settings

• Service Acknowledgement – this indicates that a user has acknowledged the current problem with the service, which will either suppress further notifications until the object changes state, or until the object recovers if “Sticky Acknowledgement” is chosen.
• Service Recovery – the service has recovered back to an OK state.
• Service Warning – the service has exceeded your Warning threshold.
• Service Unknown – this typically indicates an issue with the check plugin being used to check the status.
• Service Critical – the service has exceeded your Critical alert thresholds.
• Service Flapping – this indicates that the state of the service object has fluctuated significantly over the last 21 checks run by Nagios. You can find additional details here.
• Service Downtime – the service has been placed in administrative downtime by a user, suppressing notifications.

Documentation

You can learn more about setting up notifications here:

• Configuring Email and Text Notifications in Nagios XI

Full details on managing and configuring Nagios XI can be found in the Admin Guide:

• Nagios XI Admin Guide

The updated Network Switch/Router Wizard in Nagios XI 2026R1.4+ uses a new
plugin and greatly reduces the number of walks performed on the target machine, improving
information stability and response time. The new plugin is written in C, significantly improving
performance. This Wizard also creates throughput checks compatible with Nagios Mod–Gearman.

You can refer to the documentation for full details on using the Wizard:

Monitoring Switches and Routers With Nagios XI 2026

• Using the OpenShift Wizard in Nagios XI 2026R1.2+

Prerequisites

• Admin access to Nagios XI.
• Provider account ready (mailbox or SMTP relay access). For Microsoft 365 OAuth, you’ll need an App registration with Client ID/Secret and Tenant ID.
• Time sync: The XI host is NTP‑synchronized (avoids TLS handshake and token issues).
• Firewall/NAT: Allow outbound TCP on 587 (preferred) and/or 465 to the provider host. Port 25 should be used only when your relay policy explicitly allows it.
• Deliverability: Your sending domain publishes SPF, signs with DKIM, and enforces DMARC. If you run your own relay, ensure valid PTR (reverse DNS) and matching HELO name.
• From address policy: Use a dedicated sender like alerts@your-domain. Keep From and Envelope-From (Return‑Path) aligned to a domain you control.

Where to configure in XI

Nagios XI makes email setup straightforward. Navigate to these paths:

• Admin → System Config → Email Settings → SMTP with Basic Auth
• Admin → System Config → Email Settings → Gmail with OAuth2 (optional Gmail OAuth)
• Admin → System Config → Email Settings → Microsoft with OAuth2 (for Microsoft 365)

Quick Start for Any Provider

For a fast setup:

1. Navigate to Admin → System Config → Email Settings → SMTP with Basic Auth.

2. Fill in these key fields:

• SMTP Host: Your provider’s server, like smtp.gmail.com.
• Port: 587 for TLS/STARTTLS or 465 for SSL/TLS, depending on what’s required.
• Security: Choose TLS (STARTTLS) or SSL/TLS to match.
• Username: Typically your full email address (skip this for IP-allowlisted relays).
• Password: Your account password or an App Password—switch to OAuth tabs if supported.
• Send Mail From: Something clear like Nagios Alerts <alerts@your-domain.com>.

3. Hit Test Settings to send a quick email and check if it lands.

Quick tip: If you’re sending on behalf of a shared mailbox or different address, verify “Send As” permissions with your provider to avoid bounces.

Provider-Specific Setups

Email providers keep updating their rules, especially in 2025 with a big shift toward OAuth over basic auth for better security. We’ve pulled these configs from official sources and tested them to ensure they’re solid.

Gmail (Personal @gmail.com Accounts)

For personal Gmail, the easiest secure option is an App Password, paired with two-step verification.

1. Enable two-step verification in your Google account settings.

2. Generate an App Password called “Nagios XI” and copy that 16-character code.

3. In Nagios XI’s SMTP section:

• Host: smtp.gmail.com
• Port/Security: 587 with TLS (STARTTLS) or 465 with SSL/TLS.
• Username: Your full Gmail address.
• Password: The App Password (Generated 16-character code).
• From: Your Gmail address or a verified alias.

Run Test Settings to confirm.

If your organization insists on OAuth, use the Gmail with OAuth2 tab and follow the prompts with your Google Cloud Client ID and Secret.

Common hiccups: “535 5.7.8 Username and Password not accepted” usually means double-check two-step verification is on and you’re using the App Password. “Must issue a STARTTLS command first”? Switch to 587/TLS.

This video walks through setting up email notifications with Gmail.

Google Workspace (Business Accounts)

Business users get the best results with Google Workspace’s SMTP relay, especially if you can set up IP allow listing for no-fuss auth.

• Server: smtp-relay.gmail.com
• Port: 587 (recommended with STARTTLS), 465 (SSL/TLS), or 25 (opportunistic TLS).
• Security: Matches the port—opportunistic on 25, STARTTLS on 587, SSL/TLS on 465.
• Authentication: Skip username/password if IP allowlisting is in play; just align your “From” with the policy.

Microsoft 365

Microsoft 365 is all about OAuth these days for top-notch security via the Microsoft Graph API.

1. In Microsoft Entra ID (formerly Azure AD):

• Set up an app registration and grab the Tenant ID and Client ID.
• Create a Client Secret and keep it safe.
• Add the “Mail.Send” permission under Microsoft Graph (Application type) and grant admin consent.

2. Back in Nagios XI’s Microsoft with OAuth2 tab:

• Plug in the Tenant ID, Client ID, and Secret.
• Set a valid “Send From” mailbox or alias.
• Click Test Credentials, then Test Settings.

Stick to modern TLS (1.2 or higher) and keep the “From” address in line with what’s authorized.

As a temporary bridge, you can fall back to SMTP AUTH on smtp.office365.com with port 587 and STARTTLS (no 465 here). Use a licensed mailbox’s UPN and password, but enable SMTP AUTH at both the org and mailbox levels, and grant “Send As” if needed. Heads up: Basic Auth for SMTP is getting the axe permanently in September 2025, so shift to OAuth ASAP.

Typical errors: “5.7.139 Authentication unsuccessful” or “5.7.0 Authentication required” points to enabling SMTP AUTH (if using it), checking UPN/password, and sticking to 587/STARTTLS. “5.7.60 Client does not have permissions to send as this sender”? Grant “Send As” or tweak the “From”.

Outlook.com

For personal Microsoft accounts like Outlook.com, Hotmail, or Live, keep it simple:

• Server: smtp-mail.outlook.com
• Port/Security: 587 with STARTTLS.
• Authentication: Your full address and password; switch to an App Password if two-step verification is on.

Read this article to learn more:

Yahoo Mail

Yahoo keeps third-party access secure with App Passwords.

1. Head to Yahoo Account Security and generate one named “Nagios XI”.

2. In Nagios XI SMTP:

• Host: smtp.mail.yahoo.com
• Port/Security: 465 with SSL/TLS or 587 with TLS.
• Username: Your full Yahoo address.
• Password: The App Password.
• From: Your Yahoo address.

Read this article to learn more:

Zoho Mail

Zoho’s setup varies by region and account type.

For standard accounts:

• Server: smtp.zoho.com for (US), smtp.zoho.eu for (EU), smtp.zoho.in for (IN).
• Port/Security: 465 with SSL/TLS or 587 with TLS.
• Authentication: Email and password; use a Zoho App Password if MFA is enabled.
• From: Your Zoho address or allowed alias.

Organizations on paid plans might use smtppro.zoho.com with the same ports and security.

Read this article to learn more:

Custom SMTP / Internal Relay

For custom setups, loop in your mail team to get:

• The hostname (FQDN), port, TLS mode, and auth method.
• Policies for allowed From/Return-Path.
• IP allowlisting or certificate rules.
• Limits on rates and message sizes.

To nail deliverability, publish SPF, sign with DKIM, enforce DMARC, and ensure PTR and HELO match up.

Testing and Validation

Once configured, don’t skip testing; it’s the best way to catch issues early.

1. In the SMTP settings, click Test Settings and send to an email you can access.
2. Check both the Inbox and Spam/Junk folders.
3. If it flops, dive into the logs: /usr/local/nagiosxi/tmp/phpmailer.log for XI, or OS-specific ones.
4. For OAuth, head to the provider portal to validate tokens and credentials.

Handy CLI tools for extra checks:

# Probe STARTTLS for Microsoft 365
openssl s_client -starttls smtp -connect smtp.office365.com:587 -brief

# Test Gmail SMTP auth with App Password
swaks --to you@domain --server smtp.gmail.com --port 587 --auth LOGIN \
  --auth-user your@gmail.com --auth-password 'your-app-password' --tls

# Generic STARTTLS check
openssl s_client -starttls smtp -connect host.example.com:587 -showcerts

# Probe STARTTLS for Microsoft 365
openssl s_client -starttls smtp -connect smtp.office365.com:587 -brief

# Test Gmail SMTP auth with App Password
swaks --to you@domain --server smtp.gmail.com --port 587 --auth LOGIN \
  --auth-user your@gmail.com --auth-password 'your-app-password' --tls

# Generic STARTTLS check
openssl s_client -starttls smtp -connect host.example.com:587 -showcerts

Troubleshooting

Most Common Issues and Fixes

• Authentication Failures: Stick to the right App Password (for Gmail, Yahoo, Zoho) or OAuth (Microsoft 365, Gmail). For Microsoft 365’s SMTP AUTH fallback, enable it at org and mailbox levels, use 587/STARTTLS, and verify UPN/password. Sending as another address? Grant “Send As” permissions.
• TLS or Connection Errors: Ensure ports 587 and/or 465 are open outbound. Your XI host needs TLS 1.2+ and fresh CA certs. Remember, no port 465 for Microsoft 365 client submission.
• Relaying Denied: Auth properly with username/password or OAuth, or lean on an IP-allowlisted relay. Align the “From” with policy rules.
• Google Workspace Relay: Prompted for a password? Your policy likely wants IP allowlisting; drop credentials and fix the “From” domain.
• Gmail: “535 5.7.8 Username and Password not accepted” → Confirm two-step is enabled and use the App Password.

Quick Reference Table

Conclusion

Reliable email notifications prevent minor issues from becoming outages in Nagios XI. Configure SMTP and OAuth using the provider-validated settings in this guide, prioritize OAuth 2.0 as Microsoft retires legacy methods in 2025, and maintain SPF/DKIM/DMARC alignment to safeguard deliverability. If tests fail, use the logging, CLI checks, and quick-fix steps here to diagnose and resolve issues quickly.

The test email is sent using SMTP, and the verification and deletion are done via IMAP.

This document provides step-by-step instructions and usage notes:

Here is a direct link to the PDF as well:

How to Use the Email Delivery Wizard in Nagios XI

This video provides a guided walk-through covering each step of how to use configuration Wizards:

You can also refer to this documentation for full details:

Here is a direct link to the PDF as well:

How to Use Configuration Wizards in Nagios XI

This quick start guide walks you through adding log sources, searching logs, creating dashboards, configuring alerts, managing users, and more.

1. Add a Log Source

To begin collecting logs, navigate to the green “+” icon on the left sidebar. From there, select the type of log source you’d like to start receiving from.

Once selected, each source type provides a guided configuration that explains how to send logs to your Nagios Log Server.

Best Practices:

• Use consistent port numbers and formats across all devices.
• Verify log flow after adding each source.
• Tag each host for easy identification in dashboards.

The video below provides a guided walk-through that covers how to add and verify log sources in Nagios Log Server.

2. Simple Mode vs. Advanced Mode Homepage

Simple Layout
The Simple layout focuses on quick, everyday searches.
It includes:

• A central search bar.
• One-click filters such as Sendmail, 300, 401, 500, MySQL Errors, and Network Outages.
• Fast query results with minimal setup.

Use Simple layout when you need to quickly check logs, validate incoming sources, or perform basic troubleshooting.

Advanced Layout

The Advanced layout displays a detailed system overview and full search functionality.
It includes:

• Log volume graphs and performance charts.
• System Health metrics like Unique Hosts, Active Alerts, and Disk Usage.
• Historical statistics and trend visualizations.

You can switch between layouts by selecting Simple Search or Advanced Search in the top right corner by clicking on the profile icon.

How to Switch

• Switch between layouts by clicking your profile icon in the top right corner and selecting Simple or Advanced. This instantly changes the home page layout.
• Tip: this is also where you can change your theme.

3. Creating Custom Queries in Log Server

Custom queries let you quickly filter and analyze logs for faster troubleshooting. Access them under Dashboards > Custom Queries to view templates like 404 Errors or SSH and create your own for targeted searches.

Queries can be saved, edited, or removed at any time for flexible log analysis and also form the basis for alerts.

Best Practices:

• Create queries for frequent or critical issues.
• Use Global queries for team visibility.
• Remove outdated or unused queries regularly.

The video below provides a guided walk-through that covers how to create and manage custom queries in Nagios Log Server.

Here is documentation for analyzing logs:

How To Analyze Logs in Nagios Log Server 2024R2

4. Configuring Alerts in Log Server

Alerts in Nagios Log Server are triggered when specific log patterns or thresholds are detected. Access them from the Alerting tab to view, create, or manage alerts.

You can choose from Query, Real-Time, or Host Freshness alert types, each designed to monitor different conditions. When an alert is triggered, notifications can be sent via email, SNMP traps, or custom scripts depending on your configuration.

Best Practices:

• Use Query alerts for recurring issues like SSH or HTTP errors.
• Set appropriate check intervals to balance accuracy and performance.
• Regularly review alert results and update thresholds as needed.

The video below provides a guided walk-through that covers how to create and manage alerts in Nagios Log Server.

Here is documentation for alerting on events:

Alerting on Log Events in Nagios Log Server 2024R2 and 2026

5. Configuring Email Notifications in Log Server

Email notifications inform you when alerts are triggered in Nagios Log Server.
Go to Profile to set your notification email, then open Admin > General > Mail Settings to configure SMTP details.

You can configure SMTP details for Gmail, Outlook, or other mail providers to receive alert notifications directly in your inbox.

The video below provides a guided walk-through that covers how to set up email notifications in Nagios Log Server.

6. Managing Users in Log Server

User management in Nagios Log Server R2 enhances security by controlling access and permissions across your environment. Access this feature by going to Admin > Management > User Management.

From here, you can create new users or import existing ones from LDAP or Active Directory. Roles and permissions determine whether a user can view, edit, or delete alerts, notifications, contacts, and configuration settings. Admins have full access to all system functions, while standard users are limited to the permissions assigned to them.

You can also restrict host visibility for specific users, ensuring they only see the hosts relevant to their role, and enable or disable external API access as needed.

Best Practices:

• Assign the lowest level of access necessary for each role.
• Use LDAP or AD for centralized authentication.
• Regularly audit user accounts and permissions.
• Limit host visibility for non-admin users.

The video below provides a guided walk-through that covers how to create, import, and manage users in Nagios Log Server.

Conclusion

Nagios Log Server provides centralized log collection, powerful search capabilities, and customizable dashboards to help you monitor and analyze system events with ease.
This quick start guide equips you to add log sources, create queries, configure alerts, set up notifications, and manage users efficiently.

Start simple, scale as needed, and refer to the Nagios Log Server Admin Guide or schedule a Quickstart session to get professional assistance with setup and configuration.

For additional help, visit the Nagios Support Forum or visit Nagios Library