Session log upload

DataMind Oda keeps each chat as a session log on your computer. The same log travels to your company's DataMind server inside the requests the chat makes, and the company records it in its Observability log. This page covers what the upload carries, how it keeps its place, and how to stop it. For a copy you keep yourself, see Download a chat log; the files on your computer are described in Chat logs on disk.

What the upload carries

• The chat's record. Your messages and Oda's answers, what Oda's steps ran and returned, any feedback you leave, and the instructions and settings the chat works under, plus the folder it works in.
• The record travels whole. The upload carries the log's own entries as they were recorded, not a summary; nothing is filtered out of the copy before it travels.
• No route of its own. The log is not sent on its own: it travels inside the requests the chat already makes, and it goes only to the server you signed in to.
• Credentials are not part of it. Oda's own stored model credentials do not travel with the log. Anything that appears in the chat itself, such as a password typed into a message, is part of it.

For the log's contents in full, see Chat log format.

How the upload keeps its place

• Incremental. The first request carries the log from its start; after that, each request carries only the part newer than the last point the server accepted.
• Forward only. Oda continues from a later point only after the server accepts what it sent, and the point never moves backwards.
• Repeated rather than skipped. If a request fails, the point stays where it was, so the same part is carried again by a later request. If a sudden stop leaves it unclear whether a part arrived, Oda sends that part again rather than risk a gap.
• No size limit of its own. Each request carries the new part whole. A request the server refuses is retried later rather than shortened, so the log is never cut to fit.
• Each chat tracks its own place. A chat forked from another does not take on that chat's place; its upload starts from the beginning rather than from where the parent had reached.

Stopping the upload

• On by default. A chat's requests carry the log unless the installation is set up to stop the upload.
• For a whole installation. Oda can be set up so that its requests carry no log copy at all. That is an installation setting; ask your administrator.
• For your own requests. If you have the Disable DataMind Oda Content Logging permission, you can turn content logging off for your own requests in your DataMind OS profile. The company log then keeps only who made each request, when, with which model and how many tokens it used. Manage DataMind Oda for your company covers the permission.

Questions, answered

Where does the uploaded log go?

To your company's DataMind server: the log travels inside the requests the chat makes, and the company records it in its Observability log. It has no route of its own, and nothing is sent separately. Chat logging has the full account, and Manage DataMind Oda for your company describes the company side.

How much of the log travels with each request?

The first request carries the log from its start; after that, each request carries only the part newer than the last point the server accepted.

What happens when a request fails?

The point Oda continues from does not move, so the same part is carried again by a later request. A failed request never causes a gap in what the server has.

Why might the same part of the log be uploaded twice?

If a sudden stop leaves it unclear whether a part arrived, Oda sends that part again rather than risk a gap. Delivery can repeat; it never skips.

Does the upload have a size limit?

Not of its own. Each request carries the new part whole; a request the server refuses is retried later, and the log is never shortened to fit a request.

Does a branch inherit the upload place of the chat it came from?

No. A chat forked from another tracks its own place; its upload starts from the beginning, not from where the parent chat had reached.

Is the uploaded log the same as the upload my feedback releases?

No; they are two channels. The log on this page travels with the requests the chat makes. The upload that feedback releases is separate; Feedback and privacy covers it.

Does the upload include my model credentials?

No. Oda's own stored model credentials are not part of a session log. Anything that appears in the chat itself, such as a password typed into a message, is part of it and travels with the log.

Can I keep the content of my chats out of the company log?

Yes, if you have the Disable DataMind Oda Content Logging permission: turn content logging off in your DataMind OS profile, and the company log keeps only who made each request, when, with which model and how many tokens it used. It covers your requests as a whole, not one chat. Your requests still reach the server so they can be answered; only what is recorded changes. Manage DataMind Oda for your company covers the permission.

Can the upload be turned off for everyone at my company?

Yes. Oda can be set up so that its requests carry no log copy at all. That is an installation setting; ask your administrator.