ref(deis component health): Refactored deis components health dashboards

[jchauncey]

• Use the pod name for tagging data instead of container name
• Removed non-negative-derivative from some memory graphs
• rearranged graphs to be in alphabetical order
• Add refresh of 5s
• Change time resolution to 3 hours

[deis-bot]

@smothiki is a potential reviewer of this pull request based on my analysis of git blame information. Thanks @jchauncey!

[helgi]

What is the resolution time changing from?

[jchauncey]

6 hours

[jchauncey]

I just changed it again. It was 5 mins but I changed it to 3 hours

[helgi]

What's the reason to change? and why change it to 3 after 5 mins? :)

[jchauncey]

Most of our dashboards use a 5 minute resolution so I first wanted it to be consistent. 6 hours means it takes a while for the graph to really show a problem. Felt like 3 hours was a good compromise

[helgi]

Telegraf memory graphs are showing up as undefined - The CPU name of one of the pods is deis-monitor-telegraf-f1sbj

The Redis memory graph has a lot of granularity, 5.3454534543534MB

Under Registry it seems both registry and token refresher show up as the same name in the memory graph

[jchauncey]

I cant do much about the granularity and I did not see anything about the token refresher show up in my memory graphs.

[helgi]

The refresh token name now shows up properly.

Is there no way to define a rounding anywhere on the memory info? We have to do it on the info as we store it?

[jchauncey]

I can investigate and see if we can round the values

On Aug 25, 2016 4:50 PM, "Helgi Þormar Þorbjörnsson" <
notifications@github.com> wrote:

The refresh token name now shows up properly.

Is there no way to define a rounding anywhere on the memory info? We have
to do it on the info as we store it?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#135 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAaRGCMrGu87IumWeHkUENzjdMxzRvd9ks5qjgAJgaJpZM4JtRqJ
.