Closed weronikaolejniczak closed 2 weeks ago
Thank you everyone for helping us on this, truly appreciated!
I've made a first test run with Amsterdam to verify that everything was still looking "as usual". I've been through all screens and I have nothing to report, everything looks great!
I'm not able to start Kibana with the Borealis theme (errors out), I've shared some details here so I'll do another test run with Borealis once we get that sorted out.
/ci
All LGTM -- I just noticed a badge (Replica) that I'm not sure should be success
as a positive reinforcement , or secondary accent
- leaving it here!
All LGTM -- I just noticed a badge (Replica) that I'm not sure should be
success
as a positive reinforcement , orsecondary accent
- leaving it here!
Totally agree with @patpscal it can definitely be secondary accent
@patpscal @consulthys great catch! Just fyi, accentSecondary
is removed for the EuiBadge
component. We can pass in the color
prop anything that we want, it doesn't have to be danger | warning | accent | default | primary | success
.
@patpscal @consulthys great catch! Just fyi,
accentSecondary
is removed for theEuiBadge
component. We can pass in thecolor
prop anything that we want, it doesn't have to bedanger | warning | accent | default | primary | success
.
Thanks @weronikaolejniczak I think instead of success
we just need a green-ish color
@andreadelrio @mgadewoll @patpscal @consulthys thank you so much for the testing and suggestions! 💚 I updated the PR with the changes.
Let me know the final decision on those legend badge colors and I'd appreciate a double-check of the paths I defined in the PR description (where I made riskier style changes).
Testing:
- ✅ Removing wrapping <div>
(addressing: https://github.com/elastic/kibana/pull/204258#discussion_r1886698189)
File: x-pack/plugins/monitoring/public/components/beats/listing/listing.js
Path: Menu bar > Under "Management" > Stack Monitoring > Under "Beats" > Beats (localhost url)
Amsterdam | Borealis |
---|---|
- ✅ Removing wrapping <div>
(addressing: https://github.com/elastic/kibana/pull/204258#discussion_r1886698189)
File: x-pack/plugins/monitoring/public/components/kibana/instances/instances.tsx
Path: Menu bar > Under "Management" > Stack Monitoring > Under "Kibana" > Instances (localhost url)
Amsterdam | Borealis |
---|---|
[!WARNING] The issue with the Badge overlapping the next column is reproducible regardless of the changes made in this PR. If you have a ready solution, I'd appreciate it! Otherwise, let's leave it like so.
Untested paths (fyi @consulthys):
- Removing wrapping <div>
(addressing: https://github.com/elastic/kibana/pull/204258#discussion_r1886698189)
File: x-pack/plugins/monitoring/public/components/logstash/listing/listing.js
Path: Menu bar > Under "Management" > Stack Monitoring > Under "Logstash" > Instances
- Removing wrapping <div>
(addressing: https://github.com/elastic/kibana/pull/204258#discussion_r1886698189)
File: x-pack/plugins/monitoring/public/components/apm/instances/instances.tsx
Path: Menu bar > Under "Management" > Stack Monitoring > Under "APM server" > APM servers (localhost url)
- Removing !important
flag (addressing: https://github.com/elastic/kibana/pull/204258#discussion_r1886753978)
File: x-pack/plugins/monitoring/public/components/logstash/pipeline_viewer/views/metric.tsx
Path: Menu bar > Under "Management" > Stack Monitoring > Under "Logstash" > Pipeline viewer
@patpscal @consulthys great catch! Just fyi,
accentSecondary
is removed for theEuiBadge
component. We can pass in thecolor
prop anything that we want, it doesn't have to bedanger | warning | accent | default | primary | success
.Thanks @weronikaolejniczak I think instead of
success
we just need a green-ish color
I think sticking with success
is our best option here. No harm in using it.
/ci
@elasticmachine merge upstream
/ci
@elasticmachine merge upstream
Fewer modules leads to a faster build time
id | before | after | diff |
---|---|---|---|
monitoring |
478 | 396 | -82 |
Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app
id | before | after | diff |
---|---|---|---|
monitoring |
532.1KB | 514.8KB | -17.3KB |
Size of the bundles that are downloaded on every page load. Target size is below 100kb
id | before | after | diff |
---|---|---|---|
monitoring |
25.5KB | 25.3KB | -217.0B |
Summary
This PR introduces changes to
x-pack/plugins/monitoring
necessary for the Visual Refresh project (https://github.com/elastic/kibana/issues/199715):euiThemeVars
witheuiTheme
contexteuiTheme
EuiProvider
Additionally:
@emotion/react
euiStyled
to@emotion/react
emotion.d.ts
intsconfig.json
for typing of the EUI themecloses #8228
QA
We need to test the critical paths in the Stack monitoring, paying close attention to:
Specific paths:
x-pack/plugins/monitoring/public/components/chart/monitoring_timeseries_container.tsx
x-pack/plugins/monitoring/public/components/elasticsearch/shard_allocation/components/assigned.js
x-pack/plugins/monitoring/public/components/elasticsearch/shard_allocation/components/shard.js
x-pack/plugins/monitoring/public/components/kuery_bar/autocomplete_field.tsx
x-pack/plugins/monitoring/public/components/kuery_bar/suggestion_item.tsx
Checklist
release_note:*
label is applied per the guidelines