-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[DOCS] Adds What's New for 7.9 #74709
Conversation
analysis from a new perspective. For example, | ||
your dashboard might have a visualization for overall HTTP responses. | ||
You can navigate to Discover to see the saved search | ||
for HTTP responses. The new {kibana-ref}/explore-underlying-data.html[*Explore underlying data*] |
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.
This was disabled by default in #74332.
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.
@hendry-lim there are two "Explore underlying data" actions.
- One that appears in panel's context menu;
- and one that appears in-chart on chart interaction.
The one in panel's context menu is always enabled, there is no way to disable it.
It is only possible to disable the second, in-chart, action. And it is disabled by default. I don't think we should overwhelm users with the specifics in this release note. I believe it is OK if they learn about the second action when they navigate to the docs of "Explore underlying data".
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
analysis from a new perspective. For example, | ||
your dashboard might have a visualization for overall HTTP responses. | ||
You can navigate to Discover to see the saved search | ||
for HTTP responses. The new {kibana-ref}/explore-underlying-data.html[*Explore underlying data*] |
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.
@hendry-lim there are two "Explore underlying data" actions.
- One that appears in panel's context menu;
- and one that appears in-chart on chart interaction.
The one in panel's context menu is always enabled, there is no way to disable it.
It is only possible to disable the second, in-chart, action. And it is disabled by default. I don't think we should overwhelm users with the specifics in this release note. I believe it is OK if they learn about the second action when they navigate to the docs of "Explore underlying data".
docs/user/whats-new.asciidoc
Outdated
you’ll see individual lines and polygons. | ||
|
||
{kibana-ref}//tile-layer.html[Vector tile layers] are also enhanced—add layers to your map for data services that implement the |
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.
Should this be a new section since vector tile layers are very different from geo_shape field clustering?
docs/user/whats-new.asciidoc
Outdated
you’ll see individual lines and polygons. | ||
|
||
{kibana-ref}//tile-layer.html[Vector tile layers] are also enhanced—add layers to your map for data services that implement the |
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.
Can you replace "enhanced". This is a new feature and not an enhancement. This is the first time you can add vector tile layers to your map
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
docs/user/whats-new.asciidoc
Outdated
=== ServiceNow action in Alerts | ||
|
||
Alerting introduces a ServiceNow action that pushes or updates |
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 pushes or updates
might sounds wrong, because ServiceNow in Alerting doesn't update incident, just create a new one per each execution.
I see that below is a line data to a new incident in ServiceNow
which make it clearer, maybe it is just my translation, but I prefer to keep only word pushes
instead of pushes or updates
.
Not sure if should mention here about the license with which this action type is available.
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.
@YulNaumenko good catch, I think the push or update terminology was pulled from what we display in the other docs and UIs. It might be worth fixing them there as well? Possibly the same with other connectors?
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 created an issue here to update the docs + UI: #75072.
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.
ServiceNow docs LGTM. Added a comment in @YulNaumenko's review: #74709 (review).
Pinging @elastic/kibana-docs (Team:Docs) |
@elasticmachine merge upstream |
@elasticmachine, run elasticsearch-ci/docs |
Summary
This PR adds content to the doc "What's new in 7.9"
Preview
https://kibana_74709.docs-preview.app.elstc.co/guide/en/kibana/7.9/whats-new.html