Skip to content

v1.3.0

Choose a tag to compare

@ljaggarapu ljaggarapu released this 30 Jun 10:27
· 103 commits to main since this release

Highlights

This release adds cross-account search for tests and executions, plus optional OpenTelemetry tracing and metrics for MCP tool calls.

New features

Search actions for tests and executions

  • tests tool — new actions:
    • search — search tests across an account with filters for name, workspace, project, cloud provider, locations, creator, duration, engine count, and virtual users
    • search_filter_values — list allowed values for search filters (workspace, project, locations, etc.)
  • execution tool — new actions:
    • search — search executions (reports) with the same filter model, plus run-date time frames (latest, today, yesterday, last_7_days, last_30_days, or custom range)
    • search_filter_values — list allowed values for execution search filters
  • Search results include direct BlazeMeter URLs, workspace/project context, and pagination via page_index

OpenTelemetry observability

  • Optional tracing and metrics for every MCP tool call via a new telemetry module
  • Per-tool spans with action name, duration, client info, and distributed trace context (traceparent / tracestate)
  • Metrics: mcp.tool.calls (counter) and mcp.tool.duration (histogram)
  • Defaults to the Perforce gRPC OTLP collector; fully overridable via environment variables
  • New CLI flags:
    • --otel-endpoint — override OTEL_EXPORTER_OTLP_ENDPOINT
    • --otel-headers — set OTLP headers (repeatable)
    • --no-telemetry — disable telemetry (OTEL_SDK_DISABLED=true)
  • PyInstaller builds updated to bundle OpenTelemetry and gRPC dependencies

Dependencies

  • Added: opentelemetry-api, opentelemetry-sdk, opentelemetry-exporter-otlp (and transitive gRPC/protobuf packages)

Upgrade notes

  • Search and telemetry are opt-in / backward compatible — existing tool actions are unchanged
  • To disable telemetry: --no-telemetry or OTEL_SDK_DISABLED=true
  • To redirect telemetry: set OTEL_EXPORTER_OTLP_ENDPOINT (and optionally OTEL_EXPORTER_OTLP_PROTOCOL)
  • Docker: telemetry env vars are documented in the Dockerfile; no config change required unless you want a custom collector

What's Changed

Full Changelog: v1.2.0...v1.3.0