-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Scope APM alert creation to environment #65681
[APM] Scope APM alert creation to environment #65681
Conversation
Pinging @elastic/apm-ui (Team:apm) |
retest |
@elasticmachine merge upstream |
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 - but maybe @dgieselaar wants a final word?
@cauemarcondes @sqren we can't use hooks (at least not out of the box) if we want to support creating/editing alerts outside of the APM app. I'm not sure if we should add hooks here because it will make supporting those use cases harder. Do we have an alternative that doesn't add any technical debt? |
x-pack/plugins/apm/server/lib/alerts/register_transaction_duration_alert_type.ts
Outdated
Show resolved
Hide resolved
@dgieselaar there is already a bug that will fix that #65399, but it's gonna be released only on |
Would it fix the problem if we wrapped the component in the appropriate context providers ? |
@cauemarcondes Editing for 7.8 will be disabled, but we will need to fix it for 7.8. Adding a hook will/could make that harder depending on the fix we come up with. So my question is whether this is the only and the right way to fix it given that it will add technical debt that we will need to pay off later. @sqren could be, and would be my preferred fix, but I'm not sure if that it is feasible. |
@dgieselaar @sqren wasn't it what @smith wanted to fix here #65412. |
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
* adding environment to alerting * fixing translations * addressing pr comments * addressing PR comments * addressing PR comments Co-authored-by: Elastic Machine <[email protected]>
* adding environment to alerting * fixing translations * addressing pr comments * addressing PR comments * addressing PR comments Co-authored-by: Elastic Machine <[email protected]>
* adding environment to alerting * fixing translations * addressing pr comments * addressing PR comments * addressing PR comments Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
* adding environment to alerting * fixing translations * addressing pr comments * addressing PR comments * addressing PR comments Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
* upstream/master: (223 commits) [Ingest] Support root level yaml variables in agent stream template (elastic#66120) [Snapshot Restore] Fix error when deleting snapshots behind reverse proxy (elastic#66147) [Lens] fix empty state for pie (elastic#66206) [APM] Improve e2e tests (elastic#66373) [ML] Data Frame Analytics: Fix steps to be named phases. (elastic#65855) [Discover] Encode context link filter part (elastic#63831) [APM] Scope APM alert creation to environment (elastic#65681) Move Kibana Usage collectors outside the telemetry plugin (elastic#65663) [ML] Data Frame Analytics: Fix confusion matrix data grid width. (elastic#65818) Switch to core application service (elastic#63443) Removes use of prefer_v2_templates (elastic#66316) [Maps] handle case where fit to bounds does not match any documents (elastic#66307) log error instead of throw (elastic#66254) [plugin-helpers] remove outdated postinstall task (elastic#66324) Spaces - migrate default space and enter space view to KP (elastic#66098) [APM] Change plugin id for `apm_oss` to `apmOss` (elastic#66164) [Maps] convert map_selectors to TS (elastic#65905) [uptime/usage-collector] add missing await (elastic#66079) [Ingest] Add additional attributes to the Datasources Saved Object (elastic#66127) [Endpoint]EMT-339: add new policy response schema (elastic#66264) ...
This is working correctly. There's no way to use the environment as a variable in the template (like you can with service.name and transaction.type) but we can address that in #66712. |
closes #65349