Get Field 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:

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"

GET /v1/analytics/namespaces/fields/performance

Get Field Performance

cURL

curl --request GET \
  --url https://api.mixpeek.com/v1/analytics/namespaces/fields/performance \
  --header 'Authorization: Bearer <token>' \
  --header 'X-Namespace: <api-key>'

200

{
  "namespace_id": "<string>",
  "time_range_days": 123,
  "fields": [
    {
      "field_name": "<string>",
      "usage_count": 123,
      "avg_latency_ms": 123,
      "p50_latency_ms": 123,
      "p95_latency_ms": 123,
      "p99_latency_ms": 123,
      "max_latency_ms": 123,
      "index_priority_score": 123
    }
  ],
  "total_fields": 123
}

Authorizations

Authorization · string · header · required

Mixpeek API key, sent as Authorization: Bearer mxp_sk_.... Create one in Studio under Settings → API Keys, or with an admin key via POST /v1/organizations/users/{user_email}/api-keys. A missing header returns 403; an invalid or revoked key returns 401.

X-Namespace · string · header · required

Namespace id (ns_...), not the namespace name. This scopes the request rather than authenticating it, and it is required on every operation marked x-mixpeek-namespace-scoped.

Query Parameters

days · integer · default: 30

Days of history to analyze

Required range: 1 <= x <= 90

limit · integer · default: 50

Maximum fields to return

Required range: 1 <= x <= 1000

Response

200

application/json

Successful Response

Response for field performance correlation endpoint.

namespace_id · string · required

Namespace ID analyzed

time_range_days · integer · required

Number of days analyzed

fields · FieldPerformanceMetrics · object[] · required

Field performance metrics

Show child attributes

total_fields · integer · required

Total fields analyzed