Pre-built Reports¶
The app bundles eleven ready-made report templates covering common operational, capacity, compliance, and lifecycle reporting needs. They are created automatically when the app is installed. They serve two purposes: each one is an immediately useful document you can publish, schedule, and email as-is, and each one is a working example of the block types and Jinja patterns described in Building Reports with Jinja Templates that you can clone and adapt.
Pre-built templates are read-only for everyone, including superusers. To customize one, clone it from its detail page — the clone is a private, fully editable copy owned by you. See Template visibility and sharing.
The reports at a glance¶
| Report | Question it answers | Data sources |
|---|---|---|
| Device Inventory | What is in the network? | Nautobot core |
| Active Devices Report | What does the active fleet look like this week? | Nautobot core |
| IP Utilization & Capacity | Where is IP space running short? | Nautobot core |
| Recent Change Activity | What changed recently, and who changed it? | Nautobot core |
| Job Activity | Are our automation jobs healthy? | Nautobot core |
| SSoT Sync Activity | Are our data syncs running and succeeding? | SSoT framework |
| Data Quality | How trustworthy is our data? | Data Validation Engine |
| Discovery & Onboarding | What has been discovered but not yet onboarded? | Device Discovery app |
| Hardware & Software Lifecycle | What is at end-of-life or running unapproved software? | Device Lifecycle Management app |
| Configuration Compliance Audit | Are device configurations compliant, control by control? | Golden Configuration app |
| Executive Network Assessment | How healthy is the network overall? | All of the above |
Some reports depend on other Nautobot apps
Six of the reports draw only on Nautobot core data and work on any installation. The rest read from other Nautobot apps — Golden Configuration, Device Lifecycle Management, Device Discovery — or from data populated by SSoT integrations and Data Validation rules. Each report's section below lists what it needs. A report whose data source is not installed will render, but its tables and statistics will be empty.
Reports built on Nautobot core data¶
Device Inventory¶
A baseline asset report: device totals broken down by role, manufacturer, device type, and status.
Every network team is eventually asked "what do we actually have?" — by auditors, by procurement, by leadership, or by a new team member getting oriented. This report answers that question from Nautobot's source-of-truth data in a single shareable document, so the answer is always current rather than a stale spreadsheet.
Active Devices Report¶
A weekly operational snapshot of the active fleet: an inventory table of active devices, an instance summary, the roles represented, the most common device types, the locations with the most devices, and the racks with the highest space utilization.
Where Device Inventory is a full census, this report is the recurring status document — the one you schedule weekly and email to stakeholders. Comparing issues week over week surfaces fleet drift (devices appearing, disappearing, or changing state) and early capacity signals such as racks filling up.
IP Utilization & Capacity¶
IP prefix utilization and remaining capacity, summarized by namespace and by prefix role, with a Top-25 list of the most-utilized prefixes.
Address exhaustion is the kind of problem that is trivial to fix a month early and painful to fix a day late. This report makes utilization visible on a schedule, so the prefixes trending toward full are flagged while there is still time to re-plan allocations.
Recent Change Activity¶
Object-change activity in Nautobot over a rolling window, summarized by action (created, updated, deleted) and by object type, with a list of the most recent individual changes. Data comes from Nautobot's change log via a bundled GraphQL saved query.
This is the report for change review and audit trails: a periodic digest of who changed what, useful in change-advisory meetings, post-incident reviews, and any environment where data modifications need regular human eyes on them.
Job Activity¶
Background job runs and outcomes over a rolling window: totals by outcome, a breakdown by job, the most recent runs, and a dedicated failures section.
As more operations move into Nautobot Jobs, the Jobs framework becomes infrastructure in its own right. This report gives it a health check — recurring failures and silently-stopped schedules show up in the failures section instead of being noticed weeks later.
SSoT Sync Activity¶
Data synchronization (SSoT) runs and outcomes over a rolling window: totals by outcome, records synced per integration, recent runs, and failures. Populated by whatever SSoT integrations your installation runs.
Nautobot is only as good as the data flowing into it. If a sync from an upstream system quietly starts failing, the data ages without anyone noticing. This report makes sync health a routinely reviewed artifact, so a broken integration is caught from the report rather than from the stale data it caused.
Reports built on other Nautobot apps¶
Data Quality¶
Data quality posture from the Data Validation Engine: objects violating your configured validation rules, summarized by object type and by rule, with a Top-25 list of offending objects. Requires Data Validation Engine rules to be configured and audited.
Validation rules identify bad data; this report turns those results into a trackable metric. Publishing it on a schedule gives the team a violations-over-time record and a concrete worklist (the Top-25 offenders) for driving the number down — which directly protects everything else that consumes Nautobot as a source of truth.
Discovery & Onboarding¶
The current state of network discovery: the onboarding backlog (devices discovered but not yet onboarded), a breakdown by status, and recently discovered devices. Requires the Device Discovery app.
Discovery without follow-through just produces a growing list of unknown devices. This report keeps the backlog visible and measurable — how big it is, whether it is shrinking, and what has shown up on the network recently that nobody has claimed yet.
Hardware & Software Lifecycle¶
Lifecycle risk in two halves. Hardware: devices past end-of-support and those approaching it in the next 12 months, from Device Lifecycle Management hardware notices. Software: conformance against your approved (validated) software versions, by platform, with a Top-25 list of devices running non-validated software. Requires the Device Lifecycle Management app.
End-of-support hardware and unapproved software are risks that accumulate silently until an outage, a vulnerability, or a budget cycle exposes them. This report keeps both on the table — the 12-month lookahead feeds refresh planning and budget requests, and the software section gives the standardization effort a concrete target list.
Configuration Compliance Audit¶
An in-depth, audit-ready configuration compliance document built from Golden Configuration compliance results: an executive summary, a scope-and-methodology section, per-control compliance against Golden Configuration features, findings by location, a detailed listing of non-compliant devices, and a remediation appendix. Requires the Golden Configuration app with compliance features configured.
This report is written for a CISO or an external auditor rather than for the engineer who ran the compliance job. Assembling that evidence by hand before an audit typically costs days; here the same document is generated on demand from live compliance data, in a structure an auditor expects, with remediation guidance attached so findings turn into actions.
Executive Network Assessment¶
The widest-angle report in the set: a cross-subsystem network assessment covering inventory, IP capacity, configuration compliance and data quality, hardware/software lifecycle risk, operations activity (change log, job runs, SSoT syncs), and connectivity with circuits by provider. It draws on everything the other reports use — Nautobot core data plus Golden Configuration, Data Validation, and Device Lifecycle Management — and degrades gracefully when a source is absent (that section simply has no data).
This is the leadership-level document: the periodic "state of the network" for management, the health-check baseline at the start of an engagement, or the handover document for a new owner of the environment. Instead of stitching together excerpts from five tools, one report presents the whole picture with an executive summary up front.
Customizing a pre-built report¶
Pre-built templates cannot be edited, but you can look at how they're built and even clone them:
- Clone the template from its detail page to get an editable private copy, then adjust it in the report builder — reorder or remove blocks, change headings, or point data blocks at your own Saved Views.
- Read the Jinja blocks. Most of the pre-built reports are assembled from Custom Jinja blocks; opening them in the builder is the fastest way to learn the patterns in the Jinja template guide from working examples.
- Publish, schedule, and email a pre-built report exactly like any other template — see Emailing a report and Scheduling a report. Cloning is only needed to change what the report contains, not to run it.