We have updated our Terms of Service, Code of Conduct, and Addendum.

Clibl_route field added but not configured in the system fields destination settings


I noticed yesterday that the cribl_route system field is always added to all events even if deactivated in the system fields post processing settings of my destination (Splunk).
I am running a Stream cloud instance since more than a year and never had this issue before.

Anyone else has the issue ?