netra-troubleshooting
Netra Troubleshooting
Use this skill to resolve common integration issues quickly and systematically.
Common Problems
ModuleNotFoundErrorfornetra.- Missing extras for Presidio or prompt-injection scanner.
Netra.init()called multiple times.- Traces or metrics not visible in dashboard.
- Async or streaming flow not appearing as expected.
Triage Flow
- Confirm package installation and Python version compatibility.
- Confirm one-time initialization happens before provider imports.
- Verify API key/header and OTLP endpoint configuration.
- Verify enabled instruments match runtime libraries.
- Confirm network egress and collector compatibility.
- Confirm shutdown flush path for final telemetry.
More from keyvaluesoftwaresystems/netra-skills
netra-best-practices
Code-first Netra best-practices playbook covering setup, instrumentation, context tracking, custom spans/metrics, integration patterns, evaluation, simulation, and troubleshooting.
34netra-mcp-usage
Netra MCP trace-debugging workflow focused on query_traces, get_trace_by_id, and get_session_details, including exact input parameters, filter schema, operators, sorting, and pagination patterns.
19netra-simulation-setup
Set up Netra multi-turn simulations with scenario definitions, personas, fact checkers, evaluator configuration, and test-run analysis. Use to validate agent behavior before production.
4netra-evaluation-setup
Set up high-quality Netra evaluations with datasets, evaluator design, variable mapping, and repeatable test runs. Use for regression detection and quality benchmarking.
4netra-decorator-instrumentation
Create custom Netra tracing instrumentation using decorators. Use when choosing between auto-instrumentation, decorators, and manual tracing in Python or TypeScript, with clear semantic span design.
3netra-setup
Install and initialize the Netra SDK with environment-safe defaults, instrument selection, and shutdown handling.
2