Feedback and telemetry

When you leave feedback in a chat, DataMind Oda can send a copy of that chat's record to your company's collector, and only new feedback releases that copy. This page covers the uploading settings, what a released copy carries, and how Oda sends it. How to leave feedback, from reply ratings to the /feedback command, is on Feedback.

What uploading can share

• Two settings. Uploading is set for this installation: off, or feedback-only, which is the usual setting. It is not set per chat.
• Feedback is what releases it. Even with uploading on, a copy is released only when you leave new feedback in the chat; there is no setting that shares a chat without feedback.
• When uploading is off. Nothing is sent, and Oda notes it locally when you record feedback: OpenTelemetry session upload is DISABLED; this feedback is not uploaded through OpenTelemetry.

What releases a copy

• New feedback. A remark, a dialog submission, a rating or its note that you add or change, or a rating you remove: each counts as new feedback and can release a copy.
• Everything not yet sent. A release covers the part of the record that has not left yet, up to and including the feedback itself. What comes after it waits for the next feedback.
• Branched chats. Feedback a chat inherited from the chat it branched from does not release it; a new feedback left in the branch does, and it also covers what the branch inherited. See Conversation branches.
• Nothing else. Asking questions, opening or restoring a chat, or reloading a part of Oda does not release a copy on its own.

What a released copy carries

A released copy is the chat's record as it is:

• Your messages and Oda's answers.
• What Oda's steps ran and returned. The arguments and results of its tool calls.
• The instructions it works under and the definitions of its tools.
• Its to-do list and the summaries Oda writes when a long chat is shortened.
• The feedback text itself.
• The folder the chat works in.

Oda's own stored model credentials are never part of a copy. Anything that appears in the conversation itself is included, such as a password typed into a message.

Before a record leaves, it passes through any sharing rules set up for this Oda, and a rule can withhold a record from leaving. Rules act on the copy only: the chat saved on your computer is never changed by them.

How copies are sent

• In the background. A release does not block the chat: records wait their turn and are sent while the chat runs.
• Best effort. A record that is still waiting when Oda stops can be lost.
• Counted once. If the same record arrives twice, the receiving side counts it once.
• Straight to the collector. A released copy goes to the collector your company set up for DataMind Oda, and it does not ride in the requests your chats make.

Questions, answered

Can uploading send more than my feedback releases?

No. Uploading is set either off or to feedback-only, the usual setting, and even with it on, a copy leaves only when you leave new feedback. There is no setting that shares a chat without feedback.

Do ratings release copies too, or only remarks?

All feedback counts: a remark, a dialog submission, a rating or its note that you add or change, and a rating you remove. Each one can release the part of the record that had not left yet.

If I keep chatting after leaving feedback, does the new part follow?

No. A release stops at the feedback that triggered it: it covers everything up to and including that feedback, and what comes after it waits for the next feedback.

I branched a chat. Does the feedback it already has release it?

No. A copy is released only by new feedback left in the chat itself; feedback a chat inherited from the chat it branched from does not release it. A new feedback you leave in the branch does, and it also covers what the branch inherited.

Where does a released copy go?

To the collector your company set up for DataMind Oda. That is separate from the log part that rides the chat's requests (Session log upload) and from the request log your company keeps in DataMind OS (Manage DataMind Oda for your company).

Can a released copy be lost on the way?

It can. Sending is best effort: a record that is still waiting when Oda stops can be lost. If the same record arrives twice, the receiving side counts it once.

Does removing a rating undo what has left?

No. Removing a rating counts as new feedback, so it can release the part not yet sent, and it does not erase a copy that has already left.

Does it matter which model the chat uses?

No. A release works the same whichever model and provider the chat uses.

Does Oda clean the copy before sending it?

Oda itself adds no cleaning rules. A copy passes through any sharing rules set up for this Oda on its way out, and a rule can withhold a record from leaving; nothing in the rules changes the chat saved on your computer.