---
title: "Get Field Performance"
method: GET
path: "/v1/analytics/namespaces/fields/performance"
tags: ["Analytics", "Analytics - Namespaces"]
---

# Get Field Performance

`GET /v1/analytics/namespaces/fields/performance`

Analyze field performance correlation.

Shows which metadata fields correlate with slow queries, helping identify
fields that would benefit most from indexing.

**Use Cases:**
- Identify fields causing performance issues
- Quantify indexing impact potential
- Prioritize index creation
- Monitor field usage patterns

**Response Includes:**
- Field usage count
- Latency statistics (avg, P50, P95, P99, max)
- Index priority score (usage × latency)
- Sorted by priority score

**Index Priority Score:**
Higher scores indicate fields where indexing would have greatest impact.
Score = (query count) × (average latency)

**Example:**
```bash
curl -X GET "https://api.mixpeek.com/v1/analytics/namespaces/fields/performance?days=30" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "X-Namespace: your-namespace"
```

## Query parameters

- `days` integer — Days of history to analyze
- `limit` integer — Maximum fields to return

## Response `200`

Successful Response

- FieldPerformanceResponse — Response for field performance correlation endpoint.
  - `namespace_id` string, required — Namespace ID analyzed
  - `time_range_days` integer, required — Number of days analyzed
  - `fields` FieldPerformanceMetrics[], required — Field performance metrics
    - `field_name` string, required — Metadata field name
    - `usage_count` integer, required — Number of times field was queried
    - `avg_latency_ms` number, required — Average latency when field is used
    - `p50_latency_ms` number, required — 50th percentile latency
    - `p95_latency_ms` number, required — 95th percentile latency
    - `p99_latency_ms` number, required — 99th percentile latency
    - `max_latency_ms` number, required — Maximum latency observed
    - `index_priority_score` number, required — Priority score for indexing (usage_count * avg_latency)
  - `total_fields` integer, required — Total fields analyzed
  - `coverage` RecommendationCoverage — What share of the namespace's traffic these recommendations were computed from. Index recommendations are derived only from queries that FILTERED on a field (``length(filter_fields) > 0``), since an index is only meaningful for a filtered field. Without this block an empty ``recommendations`` list is indistinguishable from "this namespace is fine", and on 2026-08-22 that is exactly how it read: 184 slow queries in ``ns_7aa8b538a5`` against a ``NO ACTION - Low usage`` verdict computed from 8.
    - `total_queries` integer, required — All queries in the window
    - `filtered_queries` integer, required — Queries carrying at least one filter field. These, and only these, are what the recommendations above were computed from.
    - `slow_queries` integer, required — Queries over the slow threshold, filtered or not
    - `slow_filtered_queries` integer, required — Slow queries carrying a filter field. The gap between this and `slow_queries` is slow traffic no index recommendation can address — look at embedding, vector search or stage cost for those.
    - `threshold_ms` number — Latency above which a query counts as slow here

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `422` — Validation Error
- `500` — Internal Server Error

---

[API](https://skmtc.net/mixpeek/apis/mixpeek-api.md) · [All operations](https://skmtc.net/mixpeek/apis/mixpeek-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mixpeek/mixpeek-api/revisions/5307993e44d3/schema)