mirror of
https://github.com/hanzoai/insights.git
synced 2026-10-30 16:15:31 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
68 lines
2.7 KiB
TypeScript
68 lines
2.7 KiB
TypeScript
import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
|
|
|
|
import { StepDefinition } from '../steps'
|
|
|
|
export const getLangfuseSteps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
|
|
const { CodeBlock, Markdown, CalloutBox, dedent } = ctx
|
|
|
|
return [
|
|
{
|
|
title: 'Add Langfuse Tracing',
|
|
badge: 'required',
|
|
content: (
|
|
<>
|
|
<Markdown>
|
|
Langfuse supports most popular LLM models and you can bring your Langfuse data into Insights for
|
|
analysis.
|
|
</Markdown>
|
|
<Markdown>
|
|
{`1. First add [Langfuse Tracing](https://langfuse.com/docs/tracing) to your LLM app.
|
|
2. In your [Langfuse dashboard](https://cloud.langfuse.com/), click on **Settings** and scroll down to the **Integrations** section to find the Insights integration.`}
|
|
</Markdown>
|
|
</>
|
|
),
|
|
},
|
|
{
|
|
title: 'Configure the integration',
|
|
badge: 'required',
|
|
content: (
|
|
<>
|
|
<Markdown>Click **Configure** and paste in your Insights project token:</Markdown>
|
|
<CodeBlock
|
|
blocks={[
|
|
{
|
|
language: 'text',
|
|
file: 'API Key',
|
|
code: dedent`
|
|
<ph_project_token>
|
|
`,
|
|
},
|
|
]}
|
|
/>
|
|
<Markdown>Paste in your Insights host:</Markdown>
|
|
<CodeBlock
|
|
blocks={[
|
|
{
|
|
language: 'text',
|
|
file: 'Host',
|
|
code: dedent`
|
|
<ph_client_api_host>
|
|
`,
|
|
},
|
|
]}
|
|
/>
|
|
<Markdown>Click **Enable** and then **Save**.</Markdown>
|
|
<CalloutBox type="fyi" title="Data sync timing">
|
|
<Markdown>
|
|
Langfuse batch exports your data into Insights once a day, so it can take up to 24 hours for
|
|
your Langfuse data to appear in Insights.
|
|
</Markdown>
|
|
</CalloutBox>
|
|
</>
|
|
),
|
|
},
|
|
]
|
|
}
|
|
|
|
export const LangfuseInstallation = createInstallation(getLangfuseSteps)
|