The newer cloud event-sending path is now the default when the server has no opinion.
tengu_ccr_v2_send_events_cli Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.247: off
Read once, for one account on one subscription tier, against v2.1.247. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The setting tengu_ccr_v2_send_events_cli, which selects the newer path for sending cloud session events, now falls back to enabled when the server expresses no opinion. It previously fell back to disabled. The real value still comes from remote config.
- Nothing else in the bundle references the local name of the check, so which send path this default now turns on cannot be pinned down from the build alone.
- Related churn in the cloud sessions client in the same change threads a per-call timeout through event posts and control responses, consistent with the v2 path being prepared for real traffic.
tengu_ccr_v2_send_events_cli
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
conversation_resetevents are no longer forwardedBoth mention event