> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mixpeek.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 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:**
```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"
```



## OpenAPI

````yaml get /v1/analytics/namespaces/fields/performance
openapi: 3.1.0
info:
  title: Mixpeek API
  description: >-
    This is the Mixpeek API, providing access to various endpoints for data
    processing and retrieval.
  termsOfService: https://mixpeek.com/terms
  contact:
    name: Mixpeek Support
    url: https://mixpeek.com/contact
    email: info@mixpeek.com
  version: '0.82'
servers:
  - url: https://api.mixpeek.com
    description: Production
security: []
paths:
  /v1/analytics/namespaces/fields/performance:
    get:
      tags:
        - Analytics
        - Analytics - Namespaces
      summary: Get Field Performance
      description: >-
        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"
        ```
      operationId: get_field_performance_v1_analytics_namespaces_fields_performance_get
      parameters:
        - name: days
          in: query
          required: false
          schema:
            type: integer
            maximum: 90
            minimum: 1
            description: Days of history to analyze
            default: 30
            title: Days
          description: Days of history to analyze
        - name: limit
          in: query
          required: false
          schema:
            type: integer
            maximum: 1000
            minimum: 1
            description: Maximum fields to return
            default: 50
            title: Limit
          description: Maximum fields to return
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FieldPerformanceResponse'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    FieldPerformanceResponse:
      properties:
        namespace_id:
          type: string
          title: Namespace Id
          description: Namespace ID analyzed
        time_range_days:
          type: integer
          title: Time Range Days
          description: Number of days analyzed
        fields:
          items:
            $ref: '#/components/schemas/FieldPerformanceMetrics'
          type: array
          title: Fields
          description: Field performance metrics
        total_fields:
          type: integer
          title: Total Fields
          description: Total fields analyzed
      type: object
      required:
        - namespace_id
        - time_range_days
        - fields
        - total_fields
      title: FieldPerformanceResponse
      description: Response for field performance correlation endpoint.
    ErrorResponse:
      properties:
        success:
          type: boolean
          title: Success
          description: Always false for error responses
          default: false
        status:
          type: integer
          title: Status
          description: HTTP status code for this error
        error:
          $ref: '#/components/schemas/ErrorDetail'
          description: Error details payload
      type: object
      required:
        - status
        - error
      title: ErrorResponse
      description: Error response model.
      examples:
        - error:
            details:
              id: ns_123
              resource: namespace
            message: Namespace not found
            type: NotFoundError
          status: 404
          success: false
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    FieldPerformanceMetrics:
      properties:
        field_name:
          type: string
          title: Field Name
          description: Metadata field name
        usage_count:
          type: integer
          title: Usage Count
          description: Number of times field was queried
        avg_latency_ms:
          type: number
          title: Avg Latency Ms
          description: Average latency when field is used
        p50_latency_ms:
          type: number
          title: P50 Latency Ms
          description: 50th percentile latency
        p95_latency_ms:
          type: number
          title: P95 Latency Ms
          description: 95th percentile latency
        p99_latency_ms:
          type: number
          title: P99 Latency Ms
          description: 99th percentile latency
        max_latency_ms:
          type: number
          title: Max Latency Ms
          description: Maximum latency observed
        index_priority_score:
          type: number
          title: Index Priority Score
          description: Priority score for indexing (usage_count * avg_latency)
      type: object
      required:
        - field_name
        - usage_count
        - avg_latency_ms
        - p50_latency_ms
        - p95_latency_ms
        - p99_latency_ms
        - max_latency_ms
        - index_priority_score
      title: FieldPerformanceMetrics
      description: Performance correlation metrics for a field.
    ErrorDetail:
      properties:
        message:
          type: string
          title: Message
          description: Human-readable error message
        type:
          type: string
          title: Type
          description: Stable error type identifier (machine-readable)
        code:
          anyOf:
            - type: string
            - type: 'null'
          title: Code
          description: >-
            Fine-grained error code for programmatic handling (e.g.,
            namespace_name_taken, feature_extractor_not_found). Present only
            when consumers may need to branch on a specific error condition.
        details:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Details
          description: >-
            Optional structured details to help debugging (validation errors,
            IDs, etc.)
      type: object
      required:
        - message
        - type
      title: ErrorDetail
      description: Error detail model.
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````