Skip to content
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

[alerting] adds doc on JSON-expanded action variables and task manager max_workers #92720

Merged
merged 3 commits into from
Mar 3, 2021

Conversation

pmuellr
Copy link
Member

@pmuellr pmuellr commented Feb 24, 2021

Summary

resolves #90006

For task manager, adds a note about the fact that the max_workers will be
limited to 100 starting in 8.0. Currently we allow any value (because we
always have), but do print a "deprecation" warning that the limit cannot
be exceeded starting in 8.0.

For alerting, adds note about the JSON expansion of action variables which are objects.

Checklist

Delete any items that are not applicable to this PR.

For maintainers

…r max_workers

resolves elastic#90006

For task manager, adds a note about the fact that the max_workers will be
limited to 100 starting in 8.0.  Currently we allow any value (because we
always have), but do print a "deprecation" warning that the limit cannot
be exceeded starting in 8.0
@pmuellr pmuellr added Feature:Alerting release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.12.0 v8.0.0 labels Feb 24, 2021
@pmuellr pmuellr marked this pull request as ready for review February 24, 2021 22:49
@pmuellr pmuellr requested a review from a team as a code owner February 24, 2021 22:49
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@YulNaumenko YulNaumenko requested a review from gchaps February 25, 2021 02:53
Copy link
Contributor

@YulNaumenko YulNaumenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@ymao1 ymao1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Just one suggestion for removing a duplication inside a sentence.

@@ -94,6 +94,10 @@ Some cases exist where the variable values will be "escaped", when used in a con

Mustache also supports "triple braces" of the form `{{{variable name}}}`, which indicates no escaping should be done at all. Care should be used when using this form, as it could end up rendering the variable content in such a way as to make the resulting parameter invalid or formatted incorrectly.

Each alert type defines additional variables as properties of the variable `context`. For example, if an alert type defines a variable `value`, it can be used in an action parameter as `{{context.value}}`.

For diagnostic or exploratory purposes, action variables whose values are themselves objects, such as `context`, can be referenced directly as variables. The resulting value will be a JSON representation of the object. For example, if an action parameter includes `{{context}}` in an action parameter, it will expand to the JSON representation of all the variables and values provided by the alert type.
Copy link
Contributor

@ymao1 ymao1 Feb 25, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For diagnostic or exploratory purposes, action variables whose values are themselves objects, such as `context`, can be referenced directly as variables. The resulting value will be a JSON representation of the object. For example, if an action parameter includes `{{context}}` in an action parameter, it will expand to the JSON representation of all the variables and values provided by the alert type.
For diagnostic or exploratory purposes, action variables whose values are objects, such as `context`, can be referenced directly as variables. The resulting value will be a JSON representation of the object. For example, if an action parameter includes `{{context}}`, it will expand to the JSON representation of all the variables and values provided by the alert type.

Copy link
Contributor

@gchaps gchaps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with suggested changes.

@pmuellr pmuellr added v7.13.0 v7.11.2 v7.11.0 auto-backport Deprecated - use backport:version if exact versions are needed and removed v7.11.2 labels Mar 3, 2021
@pmuellr pmuellr merged commit 60adc73 into elastic:master Mar 3, 2021
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Mar 3, 2021
…r max_workers (elastic#92720)

resolves elastic#90006

For task manager, adds a note about the fact that the max_workers will be
limited to 100 starting in 8.0.  Currently we allow any value (because we
always have), but do print a "deprecation" warning that the limit cannot
be exceeded starting in 8.0

For alerting, adds note about the JSON expansion of action variables which are objects.
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Mar 3, 2021
…r max_workers (elastic#92720)

resolves elastic#90006

For task manager, adds a note about the fact that the max_workers will be
limited to 100 starting in 8.0.  Currently we allow any value (because we
always have), but do print a "deprecation" warning that the limit cannot
be exceeded starting in 8.0

For alerting, adds note about the JSON expansion of action variables which are objects.
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Mar 3, 2021
…r max_workers (elastic#92720)

resolves elastic#90006

For task manager, adds a note about the fact that the max_workers will be
limited to 100 starting in 8.0.  Currently we allow any value (because we
always have), but do print a "deprecation" warning that the limit cannot
be exceeded starting in 8.0

For alerting, adds note about the JSON expansion of action variables which are objects.
@kibanamachine
Copy link
Contributor

💚 Backport successful

7.11 / #93519
7.12 / #93520
7.x / #93521

Successful backport PRs will be merged automatically after passing CI.

kibanamachine added a commit that referenced this pull request Mar 3, 2021
…r max_workers (#92720) (#93521)

resolves #90006

For task manager, adds a note about the fact that the max_workers will be
limited to 100 starting in 8.0.  Currently we allow any value (because we
always have), but do print a "deprecation" warning that the limit cannot
be exceeded starting in 8.0

For alerting, adds note about the JSON expansion of action variables which are objects.

Co-authored-by: Patrick Mueller <[email protected]>
kibanamachine added a commit that referenced this pull request Mar 3, 2021
…r max_workers (#92720) (#93520)

resolves #90006

For task manager, adds a note about the fact that the max_workers will be
limited to 100 starting in 8.0.  Currently we allow any value (because we
always have), but do print a "deprecation" warning that the limit cannot
be exceeded starting in 8.0

For alerting, adds note about the JSON expansion of action variables which are objects.

Co-authored-by: Patrick Mueller <[email protected]>
kibanamachine added a commit that referenced this pull request Mar 3, 2021
…r max_workers (#92720) (#93519)

resolves #90006

For task manager, adds a note about the fact that the max_workers will be
limited to 100 starting in 8.0.  Currently we allow any value (because we
always have), but do print a "deprecation" warning that the limit cannot
be exceeded starting in 8.0

For alerting, adds note about the JSON expansion of action variables which are objects.

Co-authored-by: Patrick Mueller <[email protected]>
gmmorris added a commit to gmmorris/kibana that referenced this pull request Mar 4, 2021
* master: (48 commits)
  Fix wrong import in data plugin causing 100kB bundle increase (elastic#93448)
  [Fleet] Correctly track install status of an integration (elastic#93464)
  Reviews data frame analytics UI text (elastic#93033)
  Display multiple copyable fields for process.args in resolver node detail panel (elastic#93280)
  [Security Solution][Detections] ML Popover overflow fix (elastic#93525)
  chore(NA): do not use execa on bazel workspace status update script (elastic#93532)
  Bump dependencies (elastic#93511)
  [dev/build_ts_refs] support disabling the ts-refs build completely (elastic#93529)
  [Security Solution] fix data provider cypress test (elastic#93465)
  Fix service map for All environment single service (elastic#93517)
  [Fleet] Fix package version comparaison in the UI (elastic#93498)
  [alerting] adds doc on JSON-expanded action variables and task manager max_workers (elastic#92720)
  [dev/build_ts_refs] ignore type checking failures when building ts refs (elastic#93473)
  [core-new-docs] Adds a dev-doc for core documentation (elastic#92976)
  remove opacity from maps legacy style (elastic#93456)
  [Security Solution][Lists] Escape quotes in list ids and quote the id in KQL query (elastic#93176)
  Revert "Make tests deterministic by providing unique timestamps (elastic#93350)"
  [Discover] Fix link from dashboard saved search to Discover (elastic#92937)
  update public api docs
  App Search - Polishing Analytics Views (elastic#92939)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed backported Feature:Alerting release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.11.0 v7.12.0 v7.13.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Catch-up release documentation - @pmuellr
6 participants