-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metrics on canvas #1105
Metrics on canvas #1105
Conversation
The highlight on hover with this seems to also highlight all connected nodes... |
Feature! But will play with that. I guess its not stuff you might necessarily really be interested in, so, distracting. |
Need to figure out a better way to do the pruning for the websocket diff. Maybe The js seems to go a bit wonky when the websocket updates arrive. There's a metric on every node with the value |
Questions
|
Everytime there's a new report so every 3s. |
Figure out how we should handle
Does it make sense to try and figure out other values for max, e.g.
|
yes
Probably, yeah Edit: but all of that should be encapsulated in the metric's |
Nice! #1149 would be pretty great. I'm not sure about load.
A log scale could work for |
Upon reflection, I'm not convinced the |
|
9fbcb5d
to
eaed5f1
Compare
824dfb6
to
97d82ca
Compare
335dcb1
to
2863ad3
Compare
0a6fb4f
to
5b53cd8
Compare
rfr @davkal Just the JS code in this branch in the end. |
AppDispatcher.dispatch({ | ||
type: ActionTypes.PIN_METRIC, | ||
metricId, | ||
metricType: AppStore.getAvailableCanvasMetricsTypes()[metricId] |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
/* cloud paths have stroke-width set dynamically */ | ||
&:not(.shape-cloud) .border { | ||
stroke-width: @node-border-stroke-width; | ||
fill: @background-color; | ||
transition: stroke-opacity 0.5s cubic-bezier(0,0,0.21,1), fill 0.5s cubic-bezier(0,0,0.21,1); |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
All works well and looks good. My personal nit would be the fill color. I feel it's too strong. Maybe use |
- Adds metric on canvas support for more shapes - More variation from the debug bar.
Locks onto a metric after you mouseout.
- change color to bg - show "x" to remove the metric. - Small debugToolbar enhancements.
- Remove node's grey-inner-border when showing metrics
- Small fixes after the rebase
- Bump non-zero metrics up to start at 10% fill so we can see them.
- Fade out rank color opacity when showing metric
Going w/ the `top` key mappings, needs discussion.
- Bring MoC under new linting rules - adds support for immutable-console-renderer - fixes up metrics actually displaying after bad fixes when rebasing. - Mock all metrics client side for demoing
- Fixes metric keyboard selection order
- introduces "metric type" so we can flick across topos and keep the "type" of metric selected. Cheating and using label as the type atm.
- Fixes metric font-size on selected nodes - Round metric-height value to be the same as rounded displayed value. - No red/green colors in the MoC! They have to much association w/ success/failure
- no rand ids, org code - Fixes tests, no .includes in jest for now - Small comment on moc stuff - Patch up differences after MoC rebase
In meetings etc the term pin is more often used.
- Refactor some things. - Fixes heptagon moc rendering - Experiment w/ duller colors.
Fixes #1074
Bugs:
metric.format
, or a local mapping. It might be good to getmetric.label
here to keep the metrics consistent w/ the labels in the details panel.[node].metrics
onAdd/onUpdate.Clarify what it means to have an agg node metric. (In metric selector perhaps.-No agg metrics for now.avg
)Do we want to show "host cpu" on the processes topo, is that interesting?- NoFeatures
<
,>
, andq
kb shortcuts to cycle metrics, like thetop
command.