-
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
Onboard Synthetics TLS rule type with FAAD #191127
Conversation
/ci |
Pinging @elastic/response-ops (Team:ResponseOps) |
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 !!
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]History
To update your PR or re-run it, just comment with: |
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
Resolves: #169867
This is the second attempt PR 🙂 to onboard the Synthetics TLS rule type with FAAD.
To verify
/create-ccs-cluster
on slack. Choosedev-oblt
.and start Kibana
4. Navigate to
app/synthetics/settings/alerting
and add a default connector.5. Go to
/app/synthetics/monitors/getting-started
and create a HTTP Ping monitor with whatever url you want ( I used https://github.com/) and select a location.6. Go back to
app/synthetics
and click the Alerts & Rules link. Click TLS certificate rule. Edit the older than param to something low, such as 1 day.7. The TLS rule should create an active alert, verify that the action message is populated.
8. Repeat step 5 update the older than param to be higher than the age of the cert. You can check your cert here
app/synthetics/certificates
9. The TLS rule should recover, and verify that the recovery action message is populated.
10. You can also check the AAD docs in dev tools using the following command: