Logging Workflows
No matter how you’re orchestrating your workflows, we have an interface to help you upload them to Galileo.
To log your runs with Galileo, you’d start with the same typical flow of logging into Galileo:
Next you can construct your EvaluateRun object:
Then you can generate your workflows. One workflow represents one end to end interaction. Each input in your evaluation dataset corresponds to one workflow, which can have multiple steps. Each evaluate run will consist of multiple workflows. Here’s an example of how you can log your workflows using your llm app:
Finally, log your Evaluate run to Galileo:
Logging RAG Workflows
If you’re looking to log RAG workflows it’s easy to add a retriever step. Here’s an example with RAG:
Logging Agent Workflows
We also support logging Agent workflows. Here’s an example of how you can log an Agent workflow:
Logging Retriever and LLM Metadata
If you want to log more complex inputs and outputs to your nodes, we provide support for that as well. For retriever outputs we support the Document object.
For LLM inputs and outputs we support the Message object.
Often times an llm interaction consists of multiple messages. You can log these as well.
Logging Nested Workflows
If you have more complex workflows that involve nesting workflows within workflows, we support that too. Here’s an example of how you can log nested workflow using conclude to step out of the nested workflow, back into the base workflow: