Event Schema #

We recommend you ingest the raw events once into a well-formed schema that are tailored to their purpose. This improves performance, reliability, and reduces the cost and complexity of producing actionable insights. Avoid building reports and dashboards against raw telemetry data.

Use name or nameHash and timestampMillis to filter on ingestion.

The idHash is created from the source sent on the initial request to the Telemetry Service. The value is hashed to obfuscate PII identifiers such as player Ids. This ensures compliance with data protection best practices.

Example event:

{
  "name": "player-open-menu",
  "timestampMillis" : 1646097667207,
  "idHash": 3241420594091297482,
  "nameHash": 3972874251632999575,
  "eventJson": "{\n  \"menuClicked\": \"shopkeeper\",\n  \"durationMenuOpenSeconds\": 43,\n  \"interactionsInMenu\": 7\n, \"transactions\": 2\n}"
}