-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Kibana Navigation Redesign for 7.x #56232
Comments
Pinging @elastic/kibana-core-ui (Team:Core UI) |
@andrew-moldovan pointed out that with the most recent designs, we seem to have displaced the links back to the deployment views in Cloud. In early discussions, we settled on having two links in the top/black section of the left nav:
With the stacked header, the deployment switcher moved up into that top black header bar. However, that new switcher seems to only serve the purpose of switching directly between kibana deployments without ever seeing the Cloud UI. Perhaps we can accommodate these links up there (cc:/ @johnbarrierwilson ), however we will need an interim solution until the header and switcher are both in place. Long story short, should we still add those two links atop the header? The good news is that EUI built that top section into the collapsible nav. The last piece of the puzzle then would be figuring out how we get the deployment id and in order to build the links. Proposed links |
The current mockups (for the future solution) should account for this: clicking on the deployment name in the top header will open a switcher modal. The modal will have links to various things... Obviously this is a far-reaching future solution, so the dropdown/popover with deep links (such as "scale and configure", "activity feed", etc.) back into Cloud might not be possible once the headers actually arrive, so we can just change the three dots to a simple "manage deployment" link, if needed. |
Something to note: the interim solution (screenshot above from Ryan) includes the deployment dropdown as part of the sidebar. I've been viewing that specific piece of the design as an artifact from earlier designs that shouldn't be included in the interim between now and the future solution. The reasoning is that, as a user, it might be difficult and confusing to learn the paradigm of deployment navigation within Kibana to only have it moved and changed again once the stacked header arrives. Double-taxing the users to figure out a singular feature two times could have adverse effects. Let me know your thoughts! |
In the future state, I'm happy with the And so in the intermediate state, we still need that one link back to the Cloud view of a deployment. Could be the same as the future state or not. I'm fine with leaving out the black section of the navbar, but I think a link back to Cloud should be there. Maybe under |
Clarifying question, @andrew-moldovan you would like to have a link back to the Cloud view of this deployment ASAP, right? In other words, if the header redesign and switcher push out to 2+ minor versions away, then we need an intermediate solution within the current header layout (or new left nav). Correct? Let's hope we hire somebody and can ultimately avoid this, but depending on the simplicity of this solution we may also be able to get this into the imminent left nav work, if necessary. |
yes exactly. We can't switch over to defaulting to Kibana in Cloud until we having this navigation back to Cloud. 2+ minors is too long. |
Good point, and I agree. This specific problem could easily be solved by simply labeling the current deployment within the switcher (see image below). I think it's a good thing to keep all cloud links within the switcher as the user will already have the context that the switcher is where they interact with cloud-based actions. If we were to bring these links out of the switcher—either into the sidebar are somewhere else—it would potentially begin confusing the user since they will end up going to the switcher for some cloud actions, and another place for other cloud actions. Ultimately, leaving them with an inconsistent UX.
I agree that links to the deployment in Cloud should be in the sidebar in the interim. It should also be prominent since we want to begin communicating to users that the experience is moving towards a cohesive concept. How's this solution (see image)? |
Yep, I like the interim solution. Not 100% about the wording. Since there's already a management link at the bottom which is the ES-UI area. But I think it's good enough. For the future state, I'm not sure I agree that all Cloud actions should be in the deployment switcher.
|
Cool. @gjones might have some input here since this is what we were working on together. We discussed using the modal for cloud-related items—but I'll hold my opinions until Gareth gets a chance to chime in. |
The idea was that the table in the switcher has the same behaviour / options as the deployment list page, potentially this consistent interaction could be expanded to other areas where ewe list the deployments in the future, in and out of kibana. I was under the impression that any future state would always allow users to get to the cloud page in the sidebar, in the prototype last month in was called infrastructure settings under management, which I think presents a few problems, but in general the idea would be an ever present link. |
Fair enough, will be basically impossible to keep it the exact same behaviour over time, but good thing to strive for. But yes, we should be able to go to the Cloud view of a deployment from the left nav I think |
@andrew-moldovan can you provide us some guidance on how we should build this Cloud deployment link? |
Sure. Kibana has the A So in ESS creating the link is pretty simple.
And that will take you to the overview page in Cloud.
See below for some example ESS:
ECE:
|
Dropping this in here just to make sure it's captured. The Observability team saw in some mocks that the ordering of apps was incorrect. To clarify, the expected order under Observability is meant to be this:
Related (though I believe this team is already plugged in), the Kibana app team is planning to move Dashboard to the primary action for the Kibana grouping: #61632 |
@andrew-moldovan are there conditions where the deployment link would not display? For example, if I log in to a Kibana Cloud instance using the basic username/password form (not SSO)? |
Yes, I think if the user has logged in with a native user (non SSO) then we shouldn't be showing them this link, just like we don't show them the account links |
@andrew-moldovan Michail has a draft PR up and is now working through the broken tests and adding new tests. That work is obviously critical to getting this PR into a 'green', passable state in time for the 7.8 feature freeze cutoff, but that also means there are some unfinished features. Once the testing work is complete, and barring any necessary bug squashing or other critical adjustments, the Cloud deployment link and pinning are next up (in that order). Given all that, and the amount of presumed work for adding the deployment link, there is a good chance that it will not make it into the 7.8 release. We anticipate having additional eng support immediately following the 7.8 FF at which time this item will be addressed. Let me know if you'd like to discuss this further and I'll keep you posted as things progress. |
Thanks for the update! That sounds good, not much we can do |
@andrew-moldovan we have another engineer joining our team next week and would like to have her start on the cloud-related links (deployment link in nav; account links in profile). Given the outstanding nature of https://github.com/elastic/cloud/issues/54009 , should we still proceed with this work or wait until the ECE URL is being captured and passed? Is there a way we can start with ESS in the meantime since it seems 'ready'? cc:/ @bmcconaghy |
I would start with ESS by just basically assuming that you're in ESS always. After https://github.com/elastic/cloud/issues/54009, there will probably be a new variable passed into the kibana yaml file ( |
Summary
The need for improved navigation has been expressed through customer feedback, internal stakeholders, surveys, the addition of new solutions to Kibana, and the interrelated efforts on Cloud.
Target outcome
Design a long-term, scalable navigation solution that enables users to quickly switch between Elastic solutions.
Considerations
Scope
Initially, any conceptual work can and should span to affect both Cloud and Kibana. In the future, this might change due to various requirements, but at this time there are no limitations to how broad these changes can be.
As this project progresses, we will break down the desired solution set into iterations aligned to Kibana releases.
Objectives
Listed below are several goals and requirements that need to be addressed in any mockups/prototypes/concepts that are created:
Search as Navigation
Moved to #57576
Project milestones
Build out checklist
Prototype
https://ela.st/k8
Decision log
The text was updated successfully, but these errors were encountered: