Update Logs
Updates multiple logs with the provided entries. Each entry will be either added or overridden in the specified logs.
The logs
parameter can be either:
- A list of log IDs to update
- A filter dictionary to select logs matching specific criteria (requires
project
orcontext
)
A dictionary of “explicit_types” can be passed as part of the entries
.
If present, it will override the inferred type of any matching key in all logs.
Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Body
List of log IDs or a dict of filter arguments to select logs. Filter dicts are passed as key:value pairs (e.g. {"status": "done", "user_id": 12}
).
Name of the project. Required when using filter dict in logs
. Omit when passing a list of IDs.
Optional context path to update for the logs. Can use ’/’ for nested contexts (e.g. ‘training/batch1’). Can be a string (which will be interpreted with description=None and is_versioned=False) or a ContextCreateRequest object. Required when using filter dict in logs
if project is not provided.
Dictionary or list of dictionaries of key-value parameter pairs to add or update in the logs.
Dictionary or list of dictionaries of key-value entry pairs to add or update in the logs. Supports nested path syntax using dot notation for object properties (e.g., ‘metadata.author’) and bracket notation for array indices (e.g., ‘results[0]’). Complex paths like ‘results[0].scores.accuracy’ are also supported for deep updates.
Whether to overwrite existing logs