Install Firetiger Instrumentation

Prerequisites

Requires Firetiger MCP server. If get_ingest_credentials fails, prompt user:

set_firetiger_deployment <cloud> <deployment>

Workflow

Step 1: Detect Project Type

Check for project files in priority order:

• Multiple matches → ask user which to instrument
• No matches → ask user for project type

Step 2: Derive Service Name

Extract automatically, confirm with user:

• Node.js: name from package.json
• Python: name from pyproject.toml, else directory name
• Go: last segment of module path in go.mod
• Rust: name from Cargo.toml

Step 3: Fetch Credentials

Call get_ingest_credentials MCP tool. Extract:

• Ingest URL → {{INGEST_URL}}
• Authorization: Basic ... value → {{AUTH_HEADER}}

Step 4: Install Dependencies & Create Files

Read the appropriate template from assets/<language>/. Each template directory contains:

• instrumentation.* – Main instrumentation file
• dependencies.md – Install commands

Replace placeholders: {{INGEST_URL}}, {{AUTH_HEADER}}, {{SERVICE_NAME}}

Step 5: Wire Entry Point

Guide user to import instrumentation at the top of their entry file (before other imports).

Step 6: Verify

Provide env vars for production:

export OTEL_EXPORTER_OTLP_ENDPOINT="{{INGEST_URL}}"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Basic {{AUTH_HEADER}}"
export OTEL_SERVICE_NAME="{{SERVICE_NAME}}"

Suggest triggering a request and checking Firetiger UI.

References

• references/troubleshooting.md – Common issues and fixes
• references/manual-instrumentation.md – Adding custom spans
• references/signals.md – When to use traces vs metrics vs logs