It has been observed that when Item Prototypes Discover a new Item, they do not initially populate a value per their specified Item Key, until the next Interval.

For most cases, (persistent network interfaces, bonds, filesystems, etc) this is acceptable, but for highly transient discoveries in a network, discovered items may no longer exist even as soon as 1m (or less) later, which means they do get discovered but the specified data is never able to be populated (so Latest Data reflects the Item exists, but graph or recent values show [no data] ).

Preprocessing allows you to specify a value for when an item becomes unsupported (ie, "0"), but not for the very first value upon discovery. In our use-case, we end up only seeing "0" until the unsupported item is cleared per retention settings.

The feature request, then, is to either:

1.) (Ideally) Capture the specified data value at the same time of the initial Item Discovery, or

2.) (Alternatively) Allow a preprocessing rule to specify a static value upon initial discovery, of "1" or otherwise as desired for that particular Item