-
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
[Uptime] Default alert connectors email settings #123244
Conversation
Pinging @elastic/uptime (Team:uptime) |
x-pack/plugins/uptime/public/components/settings/default_email.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/uptime/public/components/settings/default_email.tsx
Outdated
Show resolved
Hide resolved
description={ | ||
<FormattedMessage | ||
id="xpack.uptime.sourceConfiguration.defaultConnectors.description.defaultEmail" | ||
defaultMessage="Email settings required for selected email alert 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.
Might need to adjust this content. Should connectors be plural? Isn't there just one email connector?
x-pack/plugins/uptime/public/components/settings/translations.ts
Outdated
Show resolved
Hide resolved
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.
The page is crashing for me when I visit settings. Was on commit 103bf0c
103bf0c
to
17ef8a7
Compare
@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.
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.
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.
💚 Build SucceededMetrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
…fix-potential-race-condition-when-screenshotting * 'main' of github.com:elastic/kibana: (75 commits) [Reporting] Logging improvements while generating reports (elastic#123802) [Uptime] Default alert connectors email settings (elastic#123244) Update comparison series styles to match the main series (elastic#123858) [RAC][Uptime] remove extra dot from the uptime alert connector message (elastic#124000) [Exploratory view] Allow ability add extra actions in lens embeddable (elastic#123713) [SecuritySolution][Investigations] Add message about missing index in data view in analyzer (elastic#122859) [TSVB] Formatting in the left axis is not respected when I have two separate axis (elastic#123903) [Discover] Remove services from component dependencies (elastic#121691) Stop IM rule execution if there are no events (elastic#123811) [Security Solution][Endpoint] Update Fleet Trusted Apps and Host Isolation Exception cards to use exception list summary API (elastic#123900) [Security Solution][Exceptions] Switches modal to flyout component (elastic#123408) [Workplace Search] Fix bug where modal visible after deleting a group (elastic#123976) [Alerting] Remove state variables from action variable menu (elastic#123702) replace deprecated api usage (elastic#123970) Fix package policy merge logic for boolean values (elastic#123974) [Security Solution][Endpoint][Policy] Remove GET policy list api route (elastic#123873) Reenable alert_add test suite (elastic#123862) [Fleet] Remove usage of IFieldType in Fleet (elastic#123960) [Lists] Add an instance of `ExceptionListClient` with server extension points turned off to context object provided to callbacks (elastic#123885) [Maps] Add execution context (elastic#123651) ... # Conflicts: # x-pack/plugins/screenshotting/server/browsers/chromium/driver_factory/index.ts
Co-authored-by: Kibana Machine <[email protected]>
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.
Response Ops changes LGTM. Verified that email params still work as expected within the Rules Management UI
I've just tested this, and I've got a few comments and issues to highlight. Testing the default connector settingsAs @shahzad31 mentioned, I have:
Once I enabled alerts for a monitor I've created and made it fail, I also checked I did receive email alerts on the configured default connector ✅ ➡️ Open IssueAs you can see above, the screen actually flashes once I select the email connector, and I can consistently reproduce it by just refreshing the page. I've created an issue for that here: #125124. Creating a particular monitor alertOnce NodeMailer was setup, as per the test above, I've also tried to create a particular monitor alert, and I correctly got emails for that. ➡️ Open IssueTyping into the field for the rule name is extremely slow. Whenever I type, I have to wait quite a bit for each character to appear in the It's currently a very poor experience as you can see below, so I've created an issue for that here: #125123. Permissions for viewersIt seems like #121098 is also solved. As you can see below, when logging-in with a |
Summary
Fixes #116362
Fixes #121098
Added ability to select email connectors in uptime alert connectors settings.
When email connector is selected. Section to add default email appears. Where user can select, To, Cc, Bcc emails.
Those emails will be used to send alerts via selected email connectors in the uptime page.
Testing
To
,Cc
,Bcc
should appear in the settings pageTo
becomes a required field.Note
Unit testing this component was hard, so i opted for more streamlined e2e tests.