Documentation Grafana Cloud AI and machine learning Grafana Agent Observability Guides Migrate to agento11y

Migrate from sigil-sdk to agento11y

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.

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.

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.

Update the module name in your imports:

Python Copy

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.

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.

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.

The wildcard row covers provider and framework packages.

Update .NET packages

Replace the NuGet package names in your project.

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.

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.

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
• Browse conversations