-
Notifications
You must be signed in to change notification settings - Fork 1
docs(falcon-ai): add Imagine feature page #641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,131 @@ | ||
| --- | ||
| title: "Imagine" | ||
| description: "AI-powered trace visualization builder. Chat with Falcon AI to turn any trace into an interactive dashboard, then save the view to replay on every future trace." | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. replay on every future trace? |
||
| --- | ||
|
|
||
| ## About | ||
|
|
||
| Imagine is a custom dashboard builder for traces. You describe what you want to see in plain English, Falcon AI assembles the widgets against the current trace, and the resulting dashboard can be saved as a template that applies to any future trace. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It is not only dashboard builder its custom view builder There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. applies to any traces (future or existing traces) in the respective project |
||
|
|
||
| A dashboard is a layout of widgets: charts, tables, metric cards, span trees, markdown summaries. Building one by hand means writing custom code or running queries one at a time. Imagine replaces that with chat, then makes the result reusable so the same trace investigation can run on every trace your team opens later. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. View can be a it not necessarily "is layout" |
||
|
|
||
| --- | ||
|
|
||
| ## Opening Imagine | ||
|
|
||
| Open any trace from the Tracing dashboard, then click the **Imagine** tab in the trace detail drawer. The toolbar shows **Save View** for persisting dashboards and a **Falcon** toggle that hides or shows the chat panel. | ||
|
|
||
|  | ||
|
|
||
| On a fresh trace, suggested prompt chips appear on the empty canvas: *"Show me where the latency is"*, *"Visualize token usage by span"*, *"Show the agent execution flow"*, *"What's the cost breakdown?"*, *"Compare the LLM calls"*, *"Summarize this trace"*. Click a chip to send it to the chat panel, or type your own request. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "Show me where the latency is" show or filter no? |
||
|
|
||
| --- | ||
|
|
||
| ## Building widgets with chat | ||
|
|
||
| Type a request in the Falcon chat panel and Imagine renders widgets in response. Each widget is placed on a 12-column CSS grid, so multiple widgets can sit side by side or stack across rows. | ||
|
|
||
| > "Show p95 latency per span as a bar chart, then render the agent execution flow." | ||
|
|
||
| > "Group LLM calls by model, put total token usage on top, and the cost breakdown on the right." | ||
|
|
||
| Falcon AI runs in **imagine** mode for these conversations, with tracing and visualization tools loaded automatically. Tool calls and responses stream into the chat panel; widgets appear on the canvas as they are emitted. | ||
|
|
||
| --- | ||
|
|
||
| ## Widget types | ||
|
|
||
| Imagine ships with 17 widget types. Falcon AI picks them based on your request, and you can also ask for a specific type by name. | ||
|
|
||
| | Category | Widgets | | ||
| |----------|---------| | ||
| | **Charts** | Line, bar, area, pie, donut, radar | | ||
| | **Tables** | Data table, key-value list | | ||
| | **Metrics** | Metric card, heatmap | | ||
| | **Trace structure** | Span tree, timeline, agent graph | | ||
| | **Data inspection** | JSON tree, code block | | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you verify if this works? I doubt that is it this way |
||
| | **Annotations** | Markdown, screenshot | | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I dont think it works for this also |
||
|
|
||
| Each widget either binds directly to live trace data or captures the output of a Falcon analysis. Live-data widgets re-render against any trace without a new LLM call. Analysis-backed widgets re-run on demand (see [Dynamic analysis](#dynamic-analysis)). | ||
|
|
||
| --- | ||
|
|
||
| ## Saving views | ||
|
|
||
| A canvas built for one trace becomes more valuable when it can replay on any trace. Save it as a view to make it reusable. | ||
|
|
||
| <Steps> | ||
| <Step title="Build the dashboard"> | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. its a view no or canvas? |
||
| Use the chat panel to assemble the widgets you want. | ||
|
|
||
|  | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You already have dashboard feature so let's not use that here.. |
||
| </Step> | ||
|
|
||
| <Step title="Save the view"> | ||
| Click **Save View** in the Imagine toolbar. A small popover appears with a suggested name pre-filled from your conversation. Edit the name if needed and confirm. | ||
|
|
||
|  | ||
| </Step> | ||
|
|
||
| <Step title="Reopen on any trace"> | ||
| The saved view appears as a tab next to the default Imagine tab. Open any trace, click the saved view's tab, and the same widgets render against that trace's data. | ||
| </Step> | ||
| </Steps> | ||
|
|
||
| Saved views are scoped to the project. Anyone in the project with access to the trace can open the view. | ||
|
|
||
| <Note> | ||
| The **Save View** button is disabled until at least one widget is on the canvas. | ||
| </Note> | ||
|
|
||
| --- | ||
|
|
||
| ## Dynamic analysis | ||
|
|
||
| Charts, tables, and metric widgets bind to trace data through field paths, so they update on a new trace without any LLM call. Narrative widgets like markdown summaries cannot do this; they need fresh analysis each time. Imagine handles them with **dynamic analysis**. | ||
|
|
||
| When you open a saved view on a new trace: | ||
|
|
||
| - Widgets with live bindings render immediately. | ||
| - Widgets marked for dynamic analysis show a skeleton loader and the message *"Falcon is analyzing this trace..."* while the analysis runs. | ||
| - Each completed widget is cached against the trace ID, so reopening the view on the same trace skips the LLM call. | ||
|
|
||
|  | ||
|
|
||
| A **Rerun** button appears in each dynamic widget's title bar once analysis completes. Click it to discard the cached result and run the analysis again. | ||
|
|
||
| --- | ||
|
|
||
| ## Reliability | ||
|
|
||
| Dynamic analysis runs through a Temporal workflow with built-in retries, so transient failures from the model provider do not surface in the UI. | ||
|
|
||
| | Step | Timeout | Retry policy | | ||
| |------|---------|--------------| | ||
| | Fetch trace data | 30 s | Up to 2 attempts | | ||
| | LLM analysis | 90 s | Up to 5 attempts with exponential backoff (5 s to 30 s) | | ||
| | Save result | 10 s | Default | | ||
|
|
||
| If the LLM step exhausts its retries, the widget records a failure state in the database. Click **Rerun** to try again once the model provider recovers. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. why do you want to say LLM? we are in no way saying its LLM right? we claim its our agent that does the fetching etc. right? |
||
|
|
||
| --- | ||
|
|
||
| ## Rate limits | ||
|
|
||
| The chat panel shares Falcon AI's rate limit of 10 messages per 60 seconds per user. Dynamic analysis re-runs do not count against this limit; they go through a dedicated single-shot endpoint with a 45-second timeout. | ||
|
|
||
| --- | ||
|
|
||
| ## Next Steps | ||
|
|
||
| <CardGroup cols={2}> | ||
| <Card title="Using Falcon AI" icon="message-circle" href="/docs/falcon-ai/features/chat"> | ||
| Open the chat, ask questions, upload files, and follow responses. | ||
| </Card> | ||
| <Card title="Skills" icon="zap" href="/docs/falcon-ai/features/skills"> | ||
| Use built-in workflows or create custom slash commands. | ||
| </Card> | ||
| <Card title="MCP Connectors" icon="plug" href="/docs/falcon-ai/features/mcp-connectors"> | ||
| Connect external tools like Linear, Slack, and GitHub. | ||
| </Card> | ||
| </CardGroup> | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you take image of something more challenging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
showing flow is like already there can you try like show me latency split or some metric split or some new analytics page view?