packages/tinybird/datasources/tcp_response.datasource at main

openstatus.dev / openstatus

fork atom

Openstatus www.openstatus.dev

fork atom

openstatus / packages / tinybird / datasources / tcp_response.datasource

at main 19 lines 624 B view raw

wrap content

Richard Hillebrand fix: correct schema formatting in tcp_response.datasource (#1748) 2mo ago

3def9e66

 1VERSION 0
 2
 3SCHEMA >
 4    `monitorId` Int32 `json:$.monitorId`,
 5    `region` String `json:$.region`,
 6    `timestamp` Int64 `json:$.timestamp`,
 7    `cronTimestamp` Int64 `json:$.timestamp`,
 8    `timing` String `json:$.timing`,
 9    `workspaceId` Int32 `json:$.workspaceId`,
10    `latency` Int64 `json:$.latency`,
11    `errorMessage` Nullable(String) `json:$.errorMessage`,
12    `error` Int16 `json:$.error`,
13    `trigger` Nullable(String) `json:$.trigger`,
14    `uri` Nullable(String) `json:$.uri`
15
16
17ENGINE "MergeTree"
18ENGINE_PARTITION_KEY "toYYYYMM(fromUnixTimestamp64Milli(timestamp))"
19ENGINE_SORTING_KEY "monitorId, workspaceId"