storage latency stats break stats-provider interface #477

New Issue

warner · 2008-06-24T01:45:36Z

warner commented

2008-06-24 01:45:36 +00:00

The dictionary of storage latency statistics that I added recently causes Violation exceptions when the stats-gatherer tries to retrieve stats. The problem is that the RIStatsProvider interface requires numerical values, whereas the latency stats are all clumped together into a dictionary.

We could change the interface, or flatten the latency stats into the top-level dict.

The dictionary of storage latency statistics that I added recently causes Violation exceptions when the stats-gatherer tries to retrieve stats. The problem is that the `RIStatsProvider` interface requires numerical values, whereas the latency stats are all clumped together into a dictionary. We could change the interface, or flatten the latency stats into the top-level dict.

warner added the

labels 2008-06-24 01:45:36 +00:00

warner added this to the 1.2.0 milestone 2008-06-24 01:45:36 +00:00

warner commented

2008-06-25 00:22:32 +00:00

Fixed, in changeset:af4e4dc8478ef394, by flattening the latency stats. They now appear with keys like storage_server.latencies.readv.90_percentile .

Fixed, in changeset:af4e4dc8478ef394, by flattening the latency stats. They now appear with keys like `storage_server.latencies.readv.90_percentile` .