rob05c opened a new issue #3981: Add Traffic Monitor gbps calculated stat, for thresholds. URL: https://github.com/apache/trafficcontrol/issues/3981 Right now, for bandwidth thresholds, the Monitor has `availableBandwidthInKbps` and `kbps`. For multi-gigabit servers, the Parameters end up being like `60000000`. Hard to keep track of all those zeros. It'd be super-easy to add another calculated stat to the Monitor, `gbps`, so you could use a parameter `health.threshold.gbps 4`, which is much easier for Ops to visually verify is correct. ## I'm submitting a ... - [ ] bug report - [x] new feature / enhancement request - [x] improvement request (usability, performance, tech debt, etc.) - [ ] other <!--(Please do not submit support requests here - see above)--> ## Traffic Control components affected ... - [ ] CDN in a Box - [ ] Documentation - [ ] Grove - [ ] Traffic Control Client - [x] Traffic Monitor - [ ] Traffic Ops - [ ] Traffic Ops ORT - [ ] Traffic Portal - [ ] Traffic Router - [ ] Traffic Stats - [ ] Traffic Vault - [ ] unknown ## Current behavior: Bandwidth thresholds are `kbps` , which has tons of zeros, hard for Ops to manage and verify correct. ## Expected / new behavior: `gbps` Calculated Stat exists in the Monitor, so operators can use `health.threshold.gbps` as a Threshold. ## Minimal reproduction of the problem with instructions: Setting `health.threshold.gbps` Parameter in TO works as a TM threshold. ## Anything else: Not really.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
