Skip to main content
The Gravitee AI Gateway LLM Proxy is a governed front door to your LLM providers — one OpenAI-compatible endpoint that fronts OpenAI, Anthropic, Gemini, Bedrock, Vertex AI, and any OpenAI-compatible provider, with subscriptions, token-based rate limiting, and guard rails applied at the gateway. The proxy exposes /chat/completions, /responses, /embeddings, and /models at https://<gateway-host>/<context-path>, so any OpenAI client works with base_url set to the proxy. Arize AX captures every call via the openinference-instrumentation-openai package — the same instrumentor that covers OpenAI’s hosted API.
This guide instruments your application’s calls to the gateway, producing OpenInference LLM spans with prompts, responses, and token usage. Gravitee’s own OpenTelemetry support emits gateway HTTP spans instead, which do not carry LLM attributes.

Prerequisites

  • Python 3.9+
  • An Arize AX account (sign up)
  • A deployed Gravitee LLM Proxy API — requires a self-hosted or hybrid APIM installation (4.10 or later) and an Enterprise license. See Proxy your LLMs.
  • A subscription API key for a plan on that API

Launch Arize

  1. Sign in to your Arize AX account.
  2. From Space Settings, copy your Space ID and API Key. You will set them as ARIZE_SPACE_ID and ARIZE_API_KEY below.

Install

Configure credentials

Setup tracing

Run Gravitee

If your LLM Proxy is secured with a JWT or OAuth2 plan instead, Gravitee reads a bearer token from the Authorization header. Pass the token as api_key= and drop default_headers.

Expected output

Verify in Arize

  1. Open your Arize AX space and select project gravitee-tracing-example.
  2. You should see a new trace within ~30 seconds containing a ChatCompletion LLM span with the prompt, response, and token usage attached.
  3. If no traces appear, see Troubleshooting.

Check from the skill, CLI, or SDK

Confirm spans are actually reaching your Arize AX project. Use whichever fits your workflow — the skill and CLI work for any framework; the SDK check is shown for each language.
Install the Arize Skills plugin and let your coding agent check for you:
Then prompt your agent:
Use the arize-trace skill to export and analyze recent traces from my project. Confirm spans are arriving, and summarize any errors or latency issues.

Troubleshooting

  • No traces in Arize. Confirm ARIZE_SPACE_ID and ARIZE_API_KEY are set in the same shell that runs example.py. Enable OpenTelemetry debug logs with export OTEL_LOG_LEVEL=debug and re-run.
  • Gravitee spans missing but other spans present. OpenAIInstrumentor().instrument(...) must run before any import openai. Make sure instrumentation.py is the first import in your entry point.
  • 401 from Gravitee. An API Key plan expects the subscription key in a custom header — X-Gravitee-Api-Key by default — not in Authorization: Bearer. Passing the key as api_key= alone will fail. If your plan overrides the header name, use that name in default_headers.
  • 404 on the request path. The base URL is your Gateway URL plus the LLM Proxy context path, with no /v1 segment (e.g. https://gateway.example.com/llmtest). The OpenAI client appends /chat/completions itself.
  • Model not found. Model IDs are namespaced by context path in a context-path:model-name format (e.g. llmtest:gpt-5.4-mini). Copy the exact ID from curl $GRAVITEE_BASE_URL/models.

Resources

Gravitee LLM Proxy Documentation

OpenInference OpenAI Instrumentor (used for Gravitee)

Add Gravitee as an AI Provider integration