-
Notifications
You must be signed in to change notification settings - Fork 155
Ability to view active profiles and add missing query inspect information #3425
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
Ability to view active profiles and add missing query inspect information #3425
Conversation
🔍 Preview links for changed docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Words and their arrangement LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
### View active context-aware experience | ||
|
||
You can check which experience is currently active for your current Discover session. This can help you confirm whether the type of data you're currently exploring is properly detected or if Discover is currently using its default experience. | ||
|
||
1. Select **Inspect** from Discover's toolbar. | ||
1. Open the **View** dropdown, then select **Profiles**. | ||
|
||
The various profiles listed show details such as the active solution and data source contexts, which determine Discover's context-aware experiences. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I overlooked this one in the checklist you shared. While it's probably useful for some users, this was mainly added as a troubleshooting tool for profile issues in prod deployments. I don't personally have an issue with public docs for it, but we should check with @ninoslavmiskovic first to see what he thinks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is fine, since we have a section that explains we are rendering something for the user that is contextual, to also show how they can check it. There is no harm in that. I doubt it will be used much, but no harm in documentation it. ++ LGTM
This PR:
Closes: #3090