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.
88 lines
3.4 KiB
TypeScript
88 lines
3.4 KiB
TypeScript
import { OnboardingComponentsContext, createInstallation } from 'scenes/onboarding/shared/OnboardingDocsContentWrapper'
|
|
|
|
import { StepDefinition } from '../steps'
|
|
|
|
export const getTraceloopSteps = (ctx: OnboardingComponentsContext): StepDefinition[] => {
|
|
const { CodeBlock, Markdown, dedent } = ctx
|
|
|
|
return [
|
|
{
|
|
title: 'Access the integrations page',
|
|
badge: 'required',
|
|
content: (
|
|
<>
|
|
<Markdown>
|
|
Traceloop supports most popular LLM models and you can bring your Traceloop data into Insights
|
|
for analysis.
|
|
</Markdown>
|
|
<Markdown>
|
|
Go to the [integrations page](https://app.traceloop.com/settings/integrations) in your Traceloop
|
|
dashboard and click on the Insights card.
|
|
</Markdown>
|
|
</>
|
|
),
|
|
},
|
|
{
|
|
title: 'Configure the integration',
|
|
badge: 'required',
|
|
content: (
|
|
<>
|
|
<Markdown>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>Select the environment you want to connect to Insights and click **Enable**.</Markdown>
|
|
<Markdown>
|
|
Traceloop events will now be exported into Insights as soon as they're available.
|
|
</Markdown>
|
|
</>
|
|
),
|
|
},
|
|
{
|
|
title: 'Send custom properties (optional)',
|
|
badge: 'optional',
|
|
content: (
|
|
<>
|
|
<Markdown>
|
|
Prefix any Traceloop association property with `insights_` to attach it to the exported event as
|
|
a custom property. The prefix is stripped, so `insights_environment` becomes an `environment`
|
|
property you can filter and break down by in Insights.
|
|
</Markdown>
|
|
<CodeBlock
|
|
language="typescript"
|
|
code={dedent`
|
|
import { withAssociationProperties } from '@traceloop/node-server-sdk'
|
|
|
|
withAssociationProperties({ insights_environment: 'production' }, () => {
|
|
// your LLM calls here
|
|
})
|
|
`}
|
|
/>
|
|
</>
|
|
),
|
|
},
|
|
]
|
|
}
|
|
|
|
export const TraceloopInstallation = createInstallation(getTraceloopSteps)
|