Logs are essential to monitor and improve your LLM app in production. Literal AI provides flexible and composable SDKs to log your LLM app at different levels of granularity.
Log Hierarchy on Literal AI
type
s are: tool
, embedding
, retrieval
, rerank
, undefined
, etc. Steps can be considered as Spans.A `Thread` with runs & intermediate steps
wrap
function.
gpt-4o
Attachment
in the Literal AI platform, which can be accessed and downloaded via a Step
.Example of a logged multimodal LLM call
Example of attachments
Step
class. You can learn more about the Step API in the following references:
Thread
to a User
Thread
to a User
to track their activity: quite handy for chatbots and conversational AIs!
Simply provide a unique User
identifier, such as an email.
User
at any time with the create_user API.User
already exists, you may update its metadata
with the update_user API.The Literal AI client method thread()
takes a participant_id
(participantId
in TypeScript) argument which accepts any of:User.id
: the unique ID of your User
— it’s a UUIDUser.identifier
: the unique identifier of your User
— it can be an email, a username, etc.identifier
!dev
, staging
, prod
.
This is particularly useful for managing your LLM application lifecycle.
To specify an environment when initializing the LiteralClient, you can use the environment
parameter:
release
parameter:
release
in the metadata.
Filter on logs
Replay a logged LLM generation in the Playground
Add a Tag to a Thread