TrueSight Cloud Docs

Cloud documentation that follows the product state.

Cloud Docs keeps integration guides, object schemas, release notes, and operational examples aligned with the same data synchronization model used across TrueSight.

Browse guides

Docs freshness94.8%

Schema sync window: 15 minutes

Guides128

Schemas42

Examples310

Last syncJust now

Documentation sync

Docs generated from versioned cloud metadata.

The sync endpoint is framed as a documentation intake channel for API schemas, example payloads, release states, and compatibility notes.

POST/api/user

{
  "collection": "cloud.docs",
  "include": ["schemas", "examples", "releases"],
  "version": "latest"
}

Docs library

Guides arranged for implementation work.

API references

Endpoint behavior, payload structures, status codes, and compatibility notes.

Schema catalog

Versioned object definitions with field purpose, type, and lifecycle notes.

Runbooks

Operational procedures for deploys, incident checks, and service validation.

Integrations

Step-by-step setup for cloud, account, and analytics workflows.

Quotas

Limits, retention windows, and rate behavior explained by plan tier.

Examples

Practical payloads and response patterns for common implementation cases.

Schemas

A reference surface for exact cloud objects.

Cloud Docs is separate from the product page: it is quieter, denser, and designed for people who need precise implementation details.

version:latestformat:jsonsync:enabled

cloud.projectProject identity, owner, plan, and environment metadata.

cloud.syncBatchBatch envelope for documentation and product state synchronization.

cloud.releaseNoteVersioned cloud changes with compatibility and migration fields.

Examples

Payloads that match real product flows.

Examples stay close to the versioned schemas instead of drifting into stale snippets.

Release notesCurrent branch

Cloud changes are grouped by version, impact, and migration need.

StatusDocs current

Documentation metadata is synced and ready for publication.