Monitoring Nautobot Instances

You can monitor the performance and usage of your Nautobot Instances through the Event History and Trends tabs located under the Data Insights heading in the left-hand navigation pane.

Event History

The Event History tab provides a log of events and actions related to all your Nautobot Instances. This includes instance creation, updates, restarts, and other significant actions. This log shows you when each event occurred, the type of event, and which instance it pertains to, the initiator, the interface used (e.g. API, Web UI), and the status of the event (Started, Completed, or Failed).

Filters (top right) can be applied to narrow down the events shown based on criteria such as event type, instance name, initiator, and date range.

Trends

While the Event History tab tracks events related to your instances, the Trends tab provides provide a view inside your instances, showing performance metrics, device statistics, regional breakdowns, and more.

There are eight dashboards available to choose from, each available from the "Dashboard" dropdown menu at the top of the page.

Dashboards

The dropdown input labeled "Dashboard" at the top of the Trends page allows you to select from eight dashboards, each providing different insights into your Nautobot Instances.

Dashboard Name	Description
1. Nautobot (Instance overview)	High-level overview of your Nautobot Instances, breaking down the distribution of objects by type
2. Device Inventory Overview	Overview of devices broken down by location, status, and manufacturer
3. Golden Config	Status of configuration compliance for devices
4. Device Lifecycle	Tracking of devices at the end of their lifecycle
5. Nautobot Circuits	Status of circuits in Nautobot broken down by provider
6. Nautobot BGP Modules	Tracking of Border Gateway Protocol pairings and statistics
7. Nautobot Firewall Modules	Tracking of firewall rules and statistics
8. Nautobot Logs	Log streams from Nautobot instances and Jobs

Syslog Forwarding

Syslog forwarding allows your Nautobot Cloud instance to send application logs (such as errors, login events, and other runtime activity) to a remote Syslog collector. This enables centralized logging and integration with external monitoring or SIEM systems.

Info

Syslog forwarding is disabled by default.

Requirements

Before enabling Syslog forwarding, ensure the following:

• Nautobot version:
  • 2.4.24 or higher (for Nautobot v2)
  • 3.0.3 or higher (for Nautobot v3)
• A reachable Syslog collector that supports standard Syslog over UDP (default port 514), with network connectivity from the Nautobot Cloud instance

Public Syslog Destinations

By default, Nautobot Cloud supports forwarding logs only to private IP addresses.

If you need to forward logs to a public IP address:

1. Open a support ticket with Nautobot Cloud Operations.
2. Wait for confirmation before enabling the configuration.

Do not configure public IP forwarding until approval has been granted.

Syslog forwarding is configured using environment variables on your Nautobot Cloud instance.

Step 1: Navigate to Your Instance

1. Log in to the Nautobot Cloud Console.
2. Navigate to your Instance.
3. Open the Settings tab.

Step 2: Add Environment Variables

Add the following environment variables:

Environment Variable	Description
NAUTOBOT_CLOUD_REMOTE_LOGGING_ENABLE	Set to True to enable Syslog forwarding. Default is disabled.
NAUTOBOT_CLOUD_REMOTE_LOGGING_SYSLOG_HOST	Hostname or IP address of your Syslog collector.
NAUTOBOT_CLOUD_REMOTE_LOGGING_SYSLOG_PORT	Port of your Syslog collector. Default: 514.

Example configuration:

NAUTOBOT_CLOUD_REMOTE_LOGGING_ENABLE=True
NAUTOBOT_CLOUD_REMOTE_LOGGING_SYSLOG_HOST=192.0.2.10
NAUTOBOT_CLOUD_REMOTE_LOGGING_SYSLOG_PORT=514

Click Save after adding the variables.

Step 3: Update the Instance

After saving the configuration:

1. Trigger an Instance Update.
2. Wait for the update to complete.

The new environment variables will be applied during the restart process.

Important Notes

• Only standard Syslog formatting is supported (custom formatting is not supported).
• Syslog forwarding uses UDP only.
• If network connectivity to the collector is unavailable, logs will not be delivered.