Device Profiles

Device Profiles in rConfig V8.2.0+

Device Profiles provide a reusable, versionable baseline for device defaults used by both manual/device CRUD and integration sync workflows. Instead of repeating full legacy mapping tags on every upstream host, you can define a profile once and reference it during sync.

The initial release of Device Profiles in V8.2.0 supports profile-aware sync in legacy Zabbix and NetBox/Nautobot flows, with broader integration and enhanced features planned for future releases.

Feature Phases

Device Profile Feature Phase 1 - Legacy Zbx and Netbox Integration and use (V8.2.0+)

Phase 1 introduces production support for Device Profiles in legacy Zabbix and legacy NetBox/Nautobot sync flows.

Scope delivered in this phase:

Device Profile CRUD in rConfig UI/API
Profile-aware validation and staging materialization in legacy Zabbix and NetBox ETL
Profile reference tag support in upstream systems
Additive tag behavior in profile mode
Profile-mode metadata persisted in staging and applied on load to devices

Device Profile Feature Phase 2 - RCO-704 New Intergrations

Phase 2 expands Device Profile support into the new integration flows covered by RCO-704, aligning profile behavior with the newer ETL architecture and preserving profile precedence/validation guarantees.

Planned scope:

Profile mode in new integration pipelines
Consistent profile conflict validation rules across new connectors
Regression coverage parity with phase 1 behavior

Device Profile Feature Phase 3 - Broad support for Device Profiles.

Phase 3 broadens Device Profile usage across additional sync and import paths, with stronger standardization and migration tooling.

Planned scope:

Broader connector and workflow coverage
Enhanced migration utilities from legacy mapping tags
Extended operational controls and observability

CRUD Usage

You can manage profiles from Device Management in the UI and through API endpoints.

Core operations:

Create: define baseline credential/template/vendor/category/model/prompts/tags
Read/List: search/filter by name, slug, status, and profile attributes
Update: update profile fields except slug
Toggle status: activate/deactivate profile for sync eligibility

Important behavior:

Slug is immutable after profile creation
Inactive profiles cannot be resolved during sync
Profile must reference valid related records (credentials/template/vendor/category/tags)

Current Support in V8.2.0

In V8.2.0, profile mode is supported for:

Legacy Zabbix sync flow
Legacy NetBox sync flow
Legacy Nautobot sync flow (NetBox variant path)

Profile reference tag support:

Zabbix: rconfig::device_profile with value set to profile slug
NetBox/Nautobot: rconfig::device_profile::{slug}

Profile Mode Semantics (Current)

When a host/device references a Device Profile:

Profile is authoritative for credential/template/vendor/category/model/prompt/enable prompt/snmp/agent baseline
rconfig::tag remains additive where supported by the integration path
Final tags are profile baseline tags plus extra upstream rconfig::tag values (deduplicated)

Recommended Adoption Pattern

Create profiles for major platform roles (for example Core Router, Access Switch, Firewall).
Validate profile references in a non-production sync run (extract/transform/load-to-staging).
Migrate upstream hosts in batches from legacy mapping tags to profile reference tags.
Verify staging output and load-to-devices behavior before broad rollout.

For migration details and exact tag formats, see Device Sync docs: