Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

rmars
Copy link
Contributor

@rmars rmars commented May 24, 2016

Fixes #412
I used viewport widths rather than pixels, and guestimated on reasonable values for our col-md choices.
Now if you widen the window the dashboard will scale.
Let me know what you think. Latency table does look a little weird.

Here are some screenshots of various widths:

screen shot 2016-05-24 at 3 13 42 pm
screen shot 2016-05-24 at 3 13 47 pm
screen shot 2016-05-24 at 3 13 56 pm
screen shot 2016-05-24 at 3 13 59 pm
screen shot 2016-05-24 at 3 14 06 pm
screen shot 2016-05-24 at 3 15 42 pm

@rmars rmars self-assigned this May 24, 2016
@siggy
Copy link
Member

siggy commented May 24, 2016

Hmmm, this might be more work than it's worth, but is it possible to not scale the elements on the left side of the red line?

width

@wmorgan
Copy link
Member

wmorgan commented May 24, 2016

Golden Buoy Award for this branch

@rmars
Copy link
Contributor Author

rmars commented May 25, 2016

@siggy - I've now coerced it into doing that.

It kiiiiind of breaks the idea that we were doing responsive columns, a la bootstrap, but it does look less weird.

This is what it looks like now, let me know what you think:

screen shot 2016-05-24 at 5 02 02 pm
screen shot 2016-05-24 at 5 02 14 pm

@siggy
Copy link
Member

siggy commented May 25, 2016

⭐ πŸ‘ i think it looks great! we can always double back at some point to get more responsiveness.

@rmars rmars force-pushed the rmars/wide-dashboard branch from 8e921a9 to cd8e26d Compare May 25, 2016 00:25
@adleong
Copy link
Member

adleong commented May 25, 2016

⭐ πŸ“Š

Approved with PullApprove

/* globals UpdateableChart */
/* exported ClientSuccessRateGraph */
var ClientSuccessRateGraph = (function() {
var columnGridPadding = 27; // grom our css grid setup
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hehe this is our fav number 🎩 🐰

@esbie
Copy link
Contributor

esbie commented May 25, 2016

πŸ‘ 🎩 🐰

Approved with PullApprove

@rmars rmars force-pushed the rmars/wide-dashboard branch from cd8e26d to 844accc Compare May 25, 2016 22:26
@rmars rmars merged commit e2d00bb into master May 25, 2016
@rmars rmars deleted the rmars/wide-dashboard branch May 25, 2016 23:25
@rmars rmars removed the reviewable label May 25, 2016
Tim-Brooks pushed a commit to Tim-Brooks/linkerd that referenced this pull request Dec 20, 2018
The telemetry service in the controller pod uses a non-fully qualified URL to connect to the prometheus pod in the control plane. This PR changes the URL the telemetry's prometheus URL to be fully qualified to be consistent with other URLs in the control plane. This change was tested in minikube. The logs report no errors and looking at the prometheus dashboard shows that stats are being recorded from all conduit proxies.

fixes linkerd#414

Signed-off-by: Dennis Adjei-Baah [email protected]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants