msg: ingested duplicate ingestion log

[vikram-sinha-DN]

Diode version

v2.0.0

Deployment type

docker compose

Deployment type version

docker v29.6.1

Diode SDK type

diode-sdk-python

Diode SDK version

v1.12.0

Diode NetBox Plugin version

v1.13.0

NetBox version

v4.6.1

Steps to reproduce

I was trying to test ingest one value to the netbox using mentioned diode version. I am using diode sdk for this ingestion. I am getting mutiple logs as shown in the screenshot I have attached here for just single ingestion saying the "msg: ingested duplicate ingestion log" with all different id. I am sure, I am not making any duplicate ingestion, it's a new value.

Expected behavior

Expected should be clear error of what's missing field expected if there are any.

Observed behavior

Observed is multiple log "saying duplicate ingestion log" just for a single value ingestion in the netbox.

[leoparente]

Hi @vikram-sinha-DN,

That message is informational rather than an error. The reconciler fingerprints every ingested entity by content, and logs that line (at debug level, which your deployment has enabled) whenever the content matches something it already received earlier. The different ids are expected, each received entity gets its own ingestion log row. In practice this almost always means the same test script was run more than once: the value is new to NetBox, but the reconciler already saw identical entity content from your earlier attempts.

The important part is what happened to your first attempt. On diode v2.0.0, deduplicated entities are skipped without being re-planned, so if the first ingestion failed to apply (for example a missing required field), re-running the script will not surface that error again or fix anything. Two suggestions:

1. Check the ingestion logs / deviations view for your first attempt: a failed apply carries the exact validation error you were expecting to see, including missing fields. Feel free to paste it here and we can help interpret it.
2. Upgrade to diode v2.1.0 or newer. Since v2.1.0 the reconciler requeues deduplicated entities for re-plan and apply, so re-ingesting the same content converges instead of being silently skipped.

Could you share what the first attempt's ingestion log shows and confirm whether v2.1.0 changes the behavior for you?

[vikram-sinha-DN]

Hi Leoparente,
Thank you for your reply and time on this one. Unfortunetly, I do not have the logs for 1st attempt. We already have moved back to previous working version that is v1.13.0. The same behavior has been not observed in that version, It don't mind if we are ingesting the same data again or new data If all the field are correct. It update whatever we give.

As per your recommendation we will test the diode v2.1.0.

Thank You !