netra-context-tracking
Netra Context Tracking
Use this skill to apply consistent identity and conversation context in Netra traces.
When To Use
- You need per-request identity (
user_id,session_id,tenant_id) in traces. - You want custom attributes and business events attached to spans.
- You need conversation input/output logs for multi-turn apps.
Procedure
- Set IDs at request entry before any downstream LLM/tool calls.
- Attach stable custom attributes (tier, region, plan, channel).
- Record business events for key milestones.
- Add conversation entries for user inputs and assistant outputs.
- Clear or replace context at the next request boundary.
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