jcoffey-dev is traveling from Thursday 1 October through Sunday 4 October. Issues and pull requests are welcome, and will get an answer after that. Thanks for your patience.
Each node stores histograms as running totals since it started (MON-4). The node was only in the sample id's low bits, so a reader couldn't diff totals per node. The console diffed across nodes, and every dashboard timing was wrong on the cluster.
On production, the command center showed 1 stage running slow (delivery attempt time 14.7 s over the last hour). Diffing the stored samples per node gives 0.7 s. The 24 h figure is 5.8 s, mostly one 300 s greeting timeout at fo.dmarcly.com.
x:Metric/get returns nodeId alongside timestamp, both taken from the id (SnowflakeIdGenerator::to_node_id, StoredMetric::node_id).
The telemetry suite checks that every sample carries it (passes locally, RocksDB).
Pairs with inbuxa-admin #73, which diffs per metric + nodeId. That PR falls back to the old behavior when nodeId is missing, so the two can land in either order.
No new strings.
Each node stores histograms as running totals since it started (MON-4). The node was only in the sample id's low bits, so a reader couldn't diff totals per node. The console diffed across nodes, and every dashboard timing was wrong on the cluster.
On production, the command center showed **1 stage running slow** (delivery attempt time 14.7 s over the last hour). Diffing the stored samples per node gives 0.7 s. The 24 h figure is 5.8 s, mostly one 300 s greeting timeout at fo.dmarcly.com.
- `x:Metric/get` returns `nodeId` alongside `timestamp`, both taken from the id (`SnowflakeIdGenerator::to_node_id`, `StoredMetric::node_id`).
- The telemetry suite checks that every sample carries it (passes locally, RocksDB).
Pairs with inbuxa-admin #73, which diffs per `metric` + `nodeId`. That PR falls back to the old behavior when `nodeId` is missing, so the two can land in either order.
No new strings.
Each node stores histograms as running totals since it started. A sample
didn't say which node wrote it (the node was only in the id's low bits),
so a reader couldn't diff totals per node, and the console diffed across
nodes: on the three-node production cluster the delivery attempt time
read 14.7 s over the last hour against 0.7 s from the nodes' own figures.
x:Metric/get now returns nodeId alongside timestamp, both from the id.
The telemetry suite checks every sample carries it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Each node stores histograms as running totals since it started (MON-4). The node was only in the sample id's low bits, so a reader couldn't diff totals per node. The console diffed across nodes, and every dashboard timing was wrong on the cluster.
On production, the command center showed 1 stage running slow (delivery attempt time 14.7 s over the last hour). Diffing the stored samples per node gives 0.7 s. The 24 h figure is 5.8 s, mostly one 300 s greeting timeout at fo.dmarcly.com.
x:Metric/getreturnsnodeIdalongsidetimestamp, both taken from the id (SnowflakeIdGenerator::to_node_id,StoredMetric::node_id).Pairs with inbuxa-admin #73, which diffs per
metric+nodeId. That PR falls back to the old behavior whennodeIdis missing, so the two can land in either order.No new strings.