Leonardo Rodoni

Hi Sean, I'm guessing you need to enable **forward** schema compatibiliy for the relevant subjects in the schema registry. If I remember correctly by default it is only backwards compatible,...

Example Telemetry Message for a push-change-update message with related subscription started information: ```json { "timestamp": "2025-05-15T13:54:53.218670811Z", "session-protocol": "yp-push", "network-node-manifest": {}, "data-collection-manifest": { "name": "netgauze-collector@leo-rocky", "vendor": "NetGauze", "software-version": "0.6.2 (02ced5ad)", "software-flavor":...

New example message (validated with yanglint): ```json { "ietf-telemetry-message:message": { "data-collection-manifest": { "name": "netgauze-collector@leo-rocky", "os-type": "Rocky Linux", "os-version": "8.10", "software-flavor": "debug", "software-version": "0.6.2 (cbd74215)", "vendor": "NetGauze" }, "data-collection-metadata": { "labels":...

I'm done, addressed the comments and split the PR: - PR #224 for shadow-rs - PR #225 for actor shutdown fixes

Also for complex prints might be better to wrap those in if tracing::enabled!(tracing::Level::TRACE) { tracing::trace!(""); }

https://github.com/gklijs/schema_registry_converter/pull/149 is needed as well for being able to parse features from metadata in schema reg response

Hey @gklijs good point, not sure these are standard responses or confluent specific. Adding the whole response json to the error is safer. I can try to have a look...