[feature request] Display a target disk usage percentage for after storage-based reassignment

[brouberol]

Current output

Storage free change estimations:
  range spread: 214.52% -> 23.87%
  std. deviation: 220.58GB -> 75.34GB
  -
  Broker XXXX: 1107.78 -> 964.58 (-143.20GB, -12.93%)
  Broker YYYY: 816.58 -> 967.81 (+151.23GB, 18.52%)
  Broker ZZZZ: 1230.99 -> 809.87 (-421.12GB, -34.21%)

Ideal output

Storage free change estimations:
  range spread: 214.52% -> 23.87%
  std. deviation: 220.58GB -> 75.34GB
  -
  Broker XXXX: 1107.78 -> 964.58 (-143.20GB, -12.93%, disk usage: 66%)
  Broker YYYY: 816.58 -> 967.81 (+151.23GB, 18.52%, disk usage: 68%)
  Broker ZZZZ: 1230.99 -> 809.87 (-421.12GB, -34.21%, disk usage 69%)

(the numbers are completely phony)

What do you think?

[jamiealquiza]

One reason total usage wasn't present is that topicmappr is working purely from storage free metrics without knowledge of how much total storage is available per broker. This would require a doubling of metrics fetched (one for storage used, one for storage free). It was assumed to be less reliable, but it's actually probably fine.

[brouberol]

Ah gotcha.

On Mon, Jun 4, 2018 at 5:42 PM, Jamie Alquiza [email protected] wrote:

One reason total usage wasn't present is that topicmappr is working purely from storage free metrics without knowledge of how much total storage is available per broker. This would require a doubling of metrics fetched (one for storage used, one for storage free). It was assumed to be less reliable, but it's actually probably fine.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/DataDog/topicmappr/issues/164#issuecomment-394401761, or mute the thread https://github.com/notifications/unsubscribe-auth/AAdTg4Fw65l5kafGu-gyXegRlBi2Jw57ks5t5VVtgaJpZM4UYmH5 .