While investigating T261633 I noticed in the statsd_exporter mappings we're only reporting PUT method for object-server, whereas reporting at least GET too would be helpful for performance investigation purposes.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| hieradata: expand swift object server statsd mappings | operations/puppet | production | +12 -12 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | fgiunchedi | T266016 Refresh and expand Swift hardware capacity | |||
| Resolved | fgiunchedi | T261633 Put ms-be2057 (Dell R740xd2) in service | |||
| Resolved | fgiunchedi | T264588 Report swift-object server per-method latencies |
Event Timeline
Comment Actions
Change 632205 had a related patch set uploaded (by Filippo Giunchedi; owner: Filippo Giunchedi):
[operations/puppet@production] hieradata: expand swift object server statsd mappings
Comment Actions
Change 632205 merged by Filippo Giunchedi:
[operations/puppet@production] hieradata: expand swift object server statsd mappings
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2020-10-07T08:32:50Z] <godog> roll-restart statsd-exporter across ms-be* after puppet run - T264588