Add blog for query insights visualizations#4116
Conversation
Signed-off-by: Chenyang Ji <cyji@amazon.com>
|
Thank you for submitting a blog post! The blog post review process is: Submit a PR -> (Optional) Peer review -> Doc review -> Marketing review -> Published. |
|
Hi @ansjcy, It looks like you're adding a new blog post but don't have an issue mentioned. Please link this PR to an open issue using one of these keywords in the PR description:
If an issue hasn't been created yet, please create one and then link it to this PR. |
Signed-off-by: Emily Guo <35637792+LilyCaroline17@users.noreply.github.com>
|
Adding @kolchfa-aws for tech docs review. |
kolchfa-aws
left a comment
There was a problem hiding this comment.
Thank you, @ansjcy! Doc review complete - I pushed my changes into your PR. Before we can merge, please do the following:
- Add a bio and picture for Kishore
- Add 3 images marked TODO
- Please retake the screen shots so the font is larger. The font can be smaller than the text on the page but not too much smaller so users can read what's on the image.
Thanks!
Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>
d22b9f7 to
009bf7e
Compare
|
previous blog: https://opensearch.org/blog/whats-new-in-opensearch-query-insights-advanced-grouping-dashboards-and-historical-analysis/ @kolchfa-aws For the font size, that's actually what we're using on the product right now. What do you think, should we tune it just for the blog? |
|
@ansjcy Yes, please make the window smaller/font larger when taking screenshots. Users should be able to read what's on the screenshot, ideally on all device types. Of course, the font will still be small on mobile but we should definitely accommodate smaller screen sizes. |
|
@ansjcy @kolchfa-aws - Is this finished? Checking for scheduling purposes. |
|
@pajuric I would love for the images to be higher resolution so the font is larger and users can read the text on the image. |
Description
Add blog for query insights visualizations
Issues Resolved
Closes #4118
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.