> ## Documentation Index > Fetch the complete documentation index at: https://docs.playflowcloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Get server log-volume histogram > Returns a stacked info/warn/error log-volume time-series for a single server over the same window as the logs. Use it to correlate a spike in error volume with a freeze: overlay these buckets on the CPU/memory/network charts on a shared time axis. Bins are `step` seconds wide (default 60). Empty bins may be omitted — treat gaps as zero. ## OpenAPI ````yaml https://api.computeflow.cloud/api/doc get /api/v3/servers/{instance_id}/log-histogram openapi: 3.1.0 info: title: PlayFlow API version: 3.0.0 description: > PlayFlow is a game server hosting and orchestration platform. Deploy, manage, and scale multiplayer game servers globally with built-in matchmaking, lobby management, and billing. ## Authentication All API endpoints (except Health) require the `api-key` header: ``` api-key: pf_your_project_api_key ``` Find your API key in the PlayFlow dashboard under **Project Settings**. Each project has two keys, both sent in the `api-key` header: - **Server key** (`pf_...`) — full access. Keep it secret (server-side only). - **Client key** (`pfclient_...`) — safe to embed in shipped game clients. It has access to all player-facing lobby, matchmaking, and read endpoints, but is **rejected with `403`** from admin/privileged routes: admin lobby get/force-delete (`GET`/`DELETE /v3/lobbies/{config}/{id}`), build deletion (`DELETE /v3/builds/{id}`), and project settings (`POST /v3/projects/settings`). Server lifecycle mutations (start/stop/restart/update) are allowed for client keys by default but can be locked to server-key-only per project via the `client_key_server_control` setting. ## Quick Start 1. **Upload a build**: `POST /v3/builds/upload-url` → get presigned URL → `PUT` your ZIP → processing starts automatically 2. **Start a server**: `POST /v3/servers/start` → get connection info in `network_ports` 3. **Connect your game client**: Use `host:external_port` from the response ## Key Concepts - **Builds**: Your game server binary packaged as a ZIP or Docker image. Versioned per name per project. - **Servers**: Running game server instances. Each gets dedicated compute and network ports with automatic health monitoring. - **Pool Servers**: Pre-provisioned servers for instant startup (~5s vs ~30s cold start). - **Regions**: 13 global regions (us-east, us-south, us-west, eu-north, eu-west, eu-uk, ap-south, sea, ap-north, ap-southeast, south-africa, south-america-brazil, south-america-chile). - **Compute Sizes**: From micro (512MB) to dedicated-xlarge (16GB dedicated CPU). ## Server Lifecycle `launching` → `running` (game ports open) → `stopped` (game exits, TTL expires, or manual stop) ## Build Lifecycle `uploading` → `processing` (build pipeline creates deployable image) → `ready` | `failed` ## Rate Limits - General reads: 100 req/sec per API key - Write operations (start server, upload build): 10 req/sec per API key - Player-facing lobby writes (join, matchmaking, start): 10 req/sec **per player** (keyed by `x-player-id`), so a game's whole player base doesn't share one bucket - Headers: `X-RateLimit-Limit`, `X-RateLimit-Remaining` ## Plan Limits - **Free**: 1 server max, forced 1hr TTL, small size only - **Pro**: Unlimited servers, all sizes, custom TTL, pool servers ## Error Format All errors return: `{ "error": "message", "detail": "context", "status": 404 }` servers: - url: https://api.computeflow.cloud security: - ApiKeyAuth: [] tags: - name: Servers description: >- Create, manage, and monitor game server instances. Each server gets dedicated compute, network ports, and automatic health monitoring with TTL enforcement. Servers start in `launching` status and transition to `running` when the game opens its ports. - name: Builds description: >- Upload and manage game server builds. Supports ZIP uploads (automatically processed into deployable images) and direct Docker image references. Builds are versioned per name per project — uploading a new build with the same name auto-increments the version. Servers always use the latest `ready` build unless a specific version is pinned. - name: Projects description: >- Configure project-level settings including network ports, player authentication, environment variables, server pooling, and lobby/matchmaking rules. Settings apply as defaults to all servers in the project and can be overridden per-server at start time. - name: Lobbies description: >- Player-centric lobby and matchmaking system. Every request identifies the player via the `x-player-id` header. Use `/me` endpoints to interact with your current lobby — the API resolves which lobby you're in automatically. **Quick start:** `POST /v3/lobbies/default` creates a lobby with sensible defaults (no dashboard config needed). Share the invite `code` with friends, or use `POST /v3/lobbies/default/me/matchmaking` to find opponents automatically. **Matchmaking** supports symmetric teams (2v2, 5v5), asymmetric roles (1 monster vs 5 hunters), FFA, battle royale duos, and skill-based matching with auto-expanding MMR buckets. paths: /api/v3/servers/{instance_id}/log-histogram: get: tags: - Servers summary: Get server log-volume histogram description: >- Returns a stacked info/warn/error log-volume time-series for a single server over the same window as the logs. Use it to correlate a spike in error volume with a freeze: overlay these buckets on the CPU/memory/network charts on a shared time axis. Bins are `step` seconds wide (default 60). Empty bins may be omitted — treat gaps as zero. operationId: getServerLogHistogram parameters: - schema: type: string description: Server instance ID. required: true description: Server instance ID. name: instance_id in: path - schema: type: string description: >- Window start. ISO 8601 or relative (e.g. "-1h"). Omit to use the default 1-hour window (matches the log query so the histogram and the log table share one time axis). required: false description: >- Window start. ISO 8601 or relative (e.g. "-1h"). Omit to use the default 1-hour window (matches the log query so the histogram and the log table share one time axis). name: start_time in: query - schema: type: string description: Window end. Same format as start_time. Defaults to now. required: false description: Window end. Same format as start_time. Defaults to now. name: end_time in: query - schema: type: integer minimum: 5 maximum: 3600 default: 60 description: >- Bin width in SECONDS (5–3600). Each bucket counts logs whose _time falls in [bin, bin+step). Use a small step (e.g. 15) for short windows to resolve a freeze spike. required: false description: >- Bin width in SECONDS (5–3600). Each bucket counts logs whose _time falls in [bin, bin+step). Use a small step (e.g. 15) for short windows to resolve a freeze spike. name: step in: query - schema: type: string maxLength: 256 description: >- Case-insensitive substring to match within log messages, applied server-side across the whole window (same semantics as the log query). required: false description: >- Case-insensitive substring to match within log messages, applied server-side across the whole window (same semantics as the log query). name: search in: query responses: '200': description: Log-volume histogram over the requested window. content: application/json: schema: type: object properties: buckets: type: array items: type: object properties: t: type: string description: ISO 8601 timestamp of the bin start. info: type: integer description: Count of info-level entries in this bin. warn: type: integer description: Count of warn-level entries in this bin. error: type: integer description: Count of error-level entries in this bin. required: - t - info - warn - error description: >- One time bin of the log-volume histogram with per-severity counts. description: >- Ordered (oldest→newest) time bins. A bin with no logs may be omitted — treat gaps as zero when rendering. step: type: integer description: Bin width in seconds actually used. window: type: object properties: start: type: string description: ISO 8601 resolved window start. end: type: string description: ISO 8601 resolved window end. required: - start - end description: >- The resolved time window these buckets cover (after applying the default window). required: - buckets - step - window description: >- Log-volume histogram: per-severity counts bucketed over time, for correlating log spikes with resource metrics during a freeze. '404': description: No server found with this instance_id in your project. content: application/json: schema: type: object properties: error: type: string description: Human-readable error message describing what went wrong. detail: type: string description: >- Additional error context. May contain the same text as error or more specific technical details. status: type: number description: HTTP status code (matches the response status code). required: - error - status description: >- Standard error response returned by all API endpoints on failure. components: securitySchemes: ApiKeyAuth: type: apiKey in: header name: api-key ````