Why is a rewalk required after adding or modifying custom data types (CDTs)?

A rewalk is required after adding or modifying Custom Data Types (CDTs) because the CDT definitions are applied during the SNMP discovery/walk process, not during normal polling.

When Statseeker performs a walk, it:

1. Retrieves the device's SNMP MIB tree.
2. Evaluates the Custom Data Type rules against the discovered OIDs.
3. Creates the required objects, metadata, and polling configuration for any matching OIDs.
4. Stores those definitions in the database for ongoing polling.

If you add a new CDT, existing devices have already been discovered and their OID trees have already been processed. Statseeker will not automatically revisit those devices and check the new CDT against previously discovered OIDs.

A rewalk forces Statseeker to:

• Re-examine the device's SNMP tree.
• Apply the new CDT definitions.
• Create any new monitored objects and data series.
• Update polling configuration as needed.

Without a rewalk:

• The CDT may appear correctly configured.
• Newly discovered devices may use it.
• Existing devices typically will not start collecting the new data because the CDT was never applied to their discovered SNMP inventory.

When a rewalk is usually required

In Statseeker 25.x

After creating or importing a CDT, you can:

• Rewalk a single device from Device Management if only a few devices need updating.
• Allow the next scheduled nightly rewalk to pick up the changes.
• Trigger a manual bulk rewalk if the CDT should apply across many devices.

If the CDT is not appearing after a rewalk, check:

• The CDT's OID actually exists on the target device (the SNMP Walk Tool is useful here).
• The CDT's networkPattern or device matching rules match the device.
• The CDT is enabled.
• Discovery logs show the CDT being evaluated and applied.