---
title: "Migrate from sigil-sdk to agento11y | Grafana Cloud documentation"
description: "Update Agent Observability SDK packages, imports, environment variables, telemetry names, and Grafana app permissions from sigil-sdk to agento11y."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Migrate from `sigil-sdk` to `agento11y`

> Note
> 
> Grafana Agent Observability is currently in [public preview](/docs/release-life-cycle/). Grafana Labs offers limited support, and breaking changes might occur prior to the feature being made generally available.

The Grafana Agent Observability SDK is being renamed from `sigil-sdk` to `agento11y`. SDK APIs and behavior are unchanged. Update package names and imports first, then update environment variables and metric and attribute names during the transition period.

> Note
> 
> Thank you for adopting Grafana Agent Observability early, before general availability. We’ve kept this change name-only, made it backwards-compatible wherever possible, and left the old names working during a transition period so you can migrate on your own schedule. If this change causes friction, [contact Grafana Support](/profile/org/tickets/new).

## Migrate at a glance

Update your dependency names and imports before rebuilding your application. You can update environment variables and telemetry names separately during the transition period.

1. Replace the old package names with the new names in your dependency manifest.
2. Update Python module names and Go import paths.
3. Rename `SIGIL_*` environment variables to `AGENTO11Y_*` when convenient.
4. Update alerts, recording rules, and dashboards that use evaluator or guard scores, or `sigil.*` labels.
5. Reinstall dependencies and rebuild your application.

No other code changes to SDK usage are required, except for renamed imports, including imported classes and functions.

## Plan for the transition

New packages are published under the `agento11y` name starting in calendar week 30. Existing `sigil-sdk` packages and `SIGIL_*` environment variables continue to work during the transition period.

The old packages emit deprecation warnings that point to the new names. Both the `SIGIL_*` and `AGENTO11Y_*` environment variable prefixes are accepted during the transition. Migrate before the old names are retired at the end of October.

## Update alerts and dashboards

Sigil-branded telemetry names change from `sigil.*` to `agento11y.*`. Update queries in alerts, recording rules, and dashboards that use these names so that they continue to match data.

> Warning
> 
> Alerts created from evaluators expect the old metric names and stop working until you update them to the corresponding `agento11y` names.

Update the following telemetry names:

- Sigil-branded attributes and labels, including `sigil.tag.<key>`, `sigil.conversation.title`, `sigil.generation.id`, `sigil.sdk.name`, and `sigil.gen_ai.request.*`, change to the corresponding `agento11y.*` names.
- Evaluator and guard score metrics change from `sigil` names to `agento11y` names.

Standard OpenTelemetry `gen_ai.*` metrics and attributes aren’t affected. Alerts based on latency (`gen_ai.client.operation.duration`), token usage (`gen_ai.client.token.usage`), time to first token, tool calls per operation, and `gen_ai.*` span attributes continue to work unchanged.

## Update package names

Package names change for each supported language. SDK APIs remain the same after you update dependencies and imports.

### Update Python packages

Replace the PyPI package names in your dependency manifest.

Expand table

| Old                          | New                          |
|------------------------------|------------------------------|
| `sigil-sdk`                  | `agento11y`                  |
| `sigil-sdk-openai`           | `agento11y-openai`           |
| `sigil-sdk-anthropic`        | `agento11y-anthropic`        |
| `sigil-sdk-gemini`           | `agento11y-gemini`           |
| `sigil-sdk-langchain`        | `agento11y-langchain`        |
| `sigil-sdk-langgraph`        | `agento11y-langgraph`        |
| `sigil-sdk-llamaindex`       | `agento11y-llamaindex`       |
| `sigil-sdk-openai-agents`    | `agento11y-openai-agents`    |
| `sigil-sdk-pydantic-ai`      | `agento11y-pydantic-ai`      |
| `sigil-sdk-litellm`          | `agento11y-litellm`          |
| `sigil-sdk-google-adk`       | `agento11y-google-adk`       |
| `sigil-sdk-strands`          | `agento11y-strands`          |
| `sigil-sdk-claude-agent-sdk` | `agento11y-claude-agent-sdk` |

Update the module name in your imports:

Python ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```python
from agento11y import Client
```

This replaces `from sigil_sdk import Client`.

### Update JavaScript and TypeScript packages

Replace the npm package name in your dependency manifest.

Expand table

| Old                     | New                  |
|-------------------------|----------------------|
| `@grafana/sigil-sdk-js` | `@grafana/agento11y` |

Framework subpath exports are unchanged. For example, continue to use `/langgraph`, `/openai-agents`, or `/vercel-ai-sdk` after the new package name.

### Update Go modules

Replace the Go module and import paths in your application.

Expand table

| Old                                            | New                                            |
|------------------------------------------------|------------------------------------------------|
| `github.com/grafana/sigil-sdk/go`              | `github.com/grafana/agento11y/go`              |
| `github.com/grafana/sigil-sdk/go-providers/*`  | `github.com/grafana/agento11y/go-providers/*`  |
| `github.com/grafana/sigil-sdk/go-frameworks/*` | `github.com/grafana/agento11y/go-frameworks/*` |

The repository moves from `grafana/sigil-sdk` to `grafana/agento11y`. GitHub redirects the old import paths, so existing builds continue to work while you update them.

### Update Java packages

Replace the Maven coordinates in your build configuration.

Expand table

| Old                                | New                                    |
|------------------------------------|----------------------------------------|
| `com.grafana.sigil:sigil-sdk-core` | `com.grafana.agento11y:agento11y-core` |
| `com.grafana.sigil:sigil-sdk-*`    | `com.grafana.agento11y:agento11y-*`    |

The wildcard row covers provider and framework packages.

### Update .NET packages

Replace the NuGet package names in your project.

Expand table

| Old                       | New                           |
|---------------------------|-------------------------------|
| `Grafana.Sigil`           | `Grafana.Agento11y`           |
| `Grafana.Sigil.OpenAI`    | `Grafana.Agento11y.OpenAI`    |
| `Grafana.Sigil.Anthropic` | `Grafana.Agento11y.Anthropic` |
| `Grafana.Sigil.Gemini`    | `Grafana.Agento11y.Gemini`    |

## Update environment variables

Rename the `SIGIL_*` prefix to `AGENTO11Y_*`. Both prefixes work during the transition, so you can update configuration separately from your package upgrade.

For example, rename `SIGIL_ENDPOINT` to `AGENTO11Y_ENDPOINT` and `SIGIL_AUTH_TOKEN` to `AGENTO11Y_AUTH_TOKEN`. Apply the same change to variables for authentication tenant ID, authentication mode, protocol, tags, user ID, guards, and other SDK configuration.

The `SIGIL_*` names will be removed in a future release.

## Reapply Grafana app permissions

The Grafana app plugin ID changes from `grafana-sigil-app` to `grafana-agento11y-app`. Grafana scopes role-based access control (RBAC) permissions to the plugin ID, so access-control changes for the old app don’t carry over to the new app.

> Warning
> 
> If you customized RBAC for the app, reapply it to `grafana-agento11y-app`. Otherwise, users might lose access or gain access that you didn’t intend.

Recreate role assignments and custom roles that grant permissions on `grafana-sigil-app`, including `plugins.app:access` and plugin-scoped actions. If you provision RBAC with Terraform, provisioning YAML, or the RBAC API, update the plugin identifier.

Expand table

| Sigil role            | Sigil slug                                        | Agento11y role            | Agento11y slug                                            |
|-----------------------|---------------------------------------------------|---------------------------|-----------------------------------------------------------|
| Sigil Viewer          | `plugins:grafana-sigil-app:sigil-viewer`          | Agento11y Viewer          | `plugins:grafana-agento11y-app:agento11y-viewer`          |
| Sigil Data Reader     | `plugins:grafana-sigil-app:sigil-data-reader`     | Agento11y Data Reader     | `plugins:grafana-agento11y-app:agento11y-data-reader`     |
| Sigil Reader          | `plugins:grafana-sigil-app:sigil-reader`          | Agento11y Reader          | `plugins:grafana-agento11y-app:agento11y-reader`          |
| Sigil Feedback Writer | `plugins:grafana-sigil-app:sigil-feedback-writer` | Agento11y Feedback Writer | `plugins:grafana-agento11y-app:agento11y-feedback-writer` |
| Sigil Admin           | `plugins:grafana-sigil-app:sigil-admin`           | Agento11y Admin           | `plugins:grafana-agento11y-app:agento11y-admin`           |

Update deep links, bookmarks, and dashboard links from `/a/grafana-sigil-app/...` to `/a/grafana-agento11y-app/...`.

## Next steps

After rebuilding your application, verify that generations appear in Agent Observability and confirm that updated alerts and dashboards return data.

- [Configure the Agent Observability SDK](/docs/grafana-cloud/machine-learning/agent-observability/configure/sdk)
- [Browse conversations](/docs/grafana-cloud/machine-learning/agent-observability/guides/conversations)
