-
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
[APM] Add default message to alerts. #78930
[APM] Add default message to alerts. #78930
Conversation
Pinging @elastic/apm-ui (Team:apm) |
@formgeist @bmorelli25 @sqren as suggested, I created a very basic message for each alert type available. I also added the threshold in the Transaction duration anomaly alert. |
x-pack/plugins/apm/public/components/alerting/register_apm_alerts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/alerting/register_apm_alerts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/alerting/register_apm_alerts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/alerting/register_apm_alerts.ts
Outdated
Show resolved
Hide resolved
We should not output |
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.
Overall a much-needed improvement by adding these placeholders. I wanted to ask if it's possible to detect one action from the other, and e.g. use the Subject field for the first line?
to something like
Basically, define a placeholder subject
as well for the actions that use the subject field?
I think we'll make the messages more consistent across Observability in later design implementation.
x-pack/plugins/apm/public/components/alerting/register_apm_alerts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/alerting/register_apm_alerts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/alerting/register_apm_alerts.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/public/components/alerting/register_apm_alerts.ts
Outdated
Show resolved
Hide resolved
Alerting doesn't support default values for anything but the message field yet. But it's something @pmuellr is looking into |
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'm not sold on alert is firing because of the following conditions:
. I think I actually like the original wording better, as I can see configuration
applying to all of the bulleted values, but I can only see conditions
applying to the last two. I'm not passionate about this though -- I think they're both fine. So LGTM with recommended changes.
With many of the alerts being global, I do see service, environment and type as conditions not just configurations. Not sure if this is even something the user will notice anyhow, so happy to leave as is. |
That's a fair point; I'm on board. |
@elasticmachine merge upstream |
'xpack.apm.alerts.action_variables.intervalSize', | ||
{ | ||
defaultMessage: | ||
'The interval size the alert will use to check for any incident', |
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.
If somebody doesn't understand the term "interval size" it might be a good idea to use a synonym in the description. WDYT of this?
'The interval size the alert will use to check for any incident', | |
'The length of the time period where the alert conditions were met', |
or perhaps:
'The interval size the alert will use to check for any incident', | |
'The alert will trigger if the conditions are met within the given interval', |
cc @bmorelli25
x-pack/plugins/apm/server/lib/alerts/register_transaction_error_rate_alert_type.ts
Outdated
Show resolved
Hide resolved
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]@kbn/optimizer bundle module count
distributable file count
page load bundle size
History
To update your PR or re-run it, just comment with: |
* adding default message * addressing pr comments * addressing pr comments * addressing pr comments * addressing pr comments Co-authored-by: Kibana Machine <[email protected]>
* master: (85 commits) Refactor attribute service (elastic#78414) [APM] Add default message to alerts. (elastic#78930) [Discover] Modify columns and sort when switching index pattern (elastic#74336) Document ts project references setup (elastic#78586) build all ts refs in single kbn:bootstrap (elastic#79438) [TSVB] Allow string fields on value count aggregation (elastic#79267) [SECURITY SOLUTION] Investigate EQL signal in timeline (elastic#79049) [Fleet] Add loading spinner to page headers (elastic#79568) [Security Solution][Resolver] Resolver query panel load more (elastic#79160) Add type row to monitor detail page. (elastic#79556) Remove license refresh from setup (elastic#79518) [docker] add reporting fonts (elastic#74806) [SECURITY_SOLUTION][ENDPOINT] Add info about trusted apps to the page subtitle + create flyout (elastic#79558) Trim Hash value before validating it (elastic#79545) Warn users when security is not configured (elastic#78545) update copy styling (elastic#79313) Update dependency @elastic/charts to v23.1.1 (elastic#78459) Introduce geo-threshold alerts (elastic#76285) elastic#76920 Show base breadcrumb when there is an error booting the app (elastic#79571) remove react-intl from kibana and keep it inside only i18n package (elastic#78956) ...
* adding default message * addressing pr comments * addressing pr comments * addressing pr comments * addressing pr comments Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Kibana Machine <[email protected]>
✅ This was tested with the |
closes #78573