Changes search service/search session infrastructure to improve performance, stability, and resiliency by ensuring that search sessions don’t add additional load on a cluster when the feature is not used
* Adding config for max alerts. Throw error in alert factory when max alerts are reported. Process alerts differently when alert limit is reached
* Fixing types. Adding new config to docker and docs
* Setting flag to indicate limit reached. Update rule status to warning if limit reached
* Fixing task runner test
* Cleanup
* Fixing task runner test
* Actually using result of hasReachedAlertLimit
* Fixing types
* Copying over scheduled actions for active alerts. Only execute actions if they exist
* Setting lower limit in functional test config
* Adding functional test
* Update x-pack/plugins/alerting/server/constants/translations.ts
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
* PR feedback
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
The new proxy tests added can test a variety of different proxy
and target server configurations, however many of those tests
are broken with our current proxy agents. Hopefully to be fixed
by replacing with hpagent instead. In the meantime, we wanted to
get the basic test framework in as well.
In addition to tests, the stand-alone forward proxy has been
enhanced to use a better proxy server, `proxy`. The existing
proxy server `http-proxy` does not support HTTPS out of the box,
and so any HTTPS testing with it is going to be a little sketchy.
Using the stand-alone forward proxy, I was able to post to Slack
through http/https proxies with and without auth, with
proxyRequestUnauthorized set to false. Which shows the existing
proxy agents do work in _some_ environments.
* [Stack Monitoring] Add stale status reporting for Kibana (#126386)
* Fix stale message grammar and update stale indicator to use EuiBadge
* Fix i18n ids
* Remove unused i18n key
* Fix Jest tests
* Update exposeToBrowser test
* Update API integration tests
* Fix functional tests
* Fix API integration tests
* Update snapshots
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [Reporting] Update docs to use screenshotting config properties
* add the remaining capture settings moved from reporting
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
resolves https://github.com/elastic/kibana/issues/126944
Adds a new configuration setting for the actions plugin,
xpack.actions.email.domain_allowlist, which is an array of domain name
strings which are allowed to be sent emails by the email connector.
* Rename the term "execution" in config to "run"
* Rename the term "execution" in config to "run"
* Rename the overlooked terms
* [DOCS] Fix example indentation
* Update docs/user/alerting/troubleshooting/alerting-common-issues.asciidoc
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
Co-authored-by: lcawl <lcawley@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
resolves https://github.com/elastic/kibana/issues/124366
Adds new task manager configuration keys.
- `xpack.task_manager.event_loop_delay.monitor` - whether to monitor
event loop delay or not; added in case this specific monitoring
causes other issues and we'd want to disable it. We don't know
of any cases where we'd need this today
- `xpack.task_manager.event_loop_delay.warn_threshold` - the number
of milliseconds of event loop delay before logging a warning
This code uses the `perf_hooks.monitorEventLoopDelay()` API[1] to collect
the event loop delay while a task is running.
[1] https://nodejs.org/api/perf_hooks.html#perf_hooksmonitoreventloopdelayoptions
When a significant event loop delay is encountered, it's very likely
that other tasks running at the same time will be affected, and so
will also end up having a long event loop delay value, and warnings
will be logged on those. Over time, though, tasks which have consistently
long event loop delays will outnumber those unfortunate peer tasks, and
be obvious from the volume in the logs.
To make it a bit easier to find these when viewing Kibana logs in Discover,
tags are added to the logged messages to make it easier to find them. One
tag is `event-loop-blocked`, second is the task type, and the third is a string
consisting of the task type and task id.
* Changing structure of minimumScheduleInterval config
* Updating rules client logic to follow enforce flag
* Updating UI to use enforce value
* Updating config key in functional tests
* Fixes
* Fixes
* Updating help text
* Wording suggestsion from PR review
* Log warning instead of throwing an error if rule has default interval less than minimum
* Updating default interval to be minimum if minimum is greater than hardcoded default
* Fixing checks
* Fixing tests
* Fixing tests
* Fixing config
* Fixing checks
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Begin work on building out the backend of an xMatters connector
* Begin work on building out the frontend of an xMatters connector
* Continue attempting to get connector to register properly
* Begin working on the UI for the Edit Connector Test page
* Start working on writing tests for backend component of the xMatters connector
* Remove unneeded test due to not having any fancy escaping
* Write tests for the frontend component of the xMatters connector
* Add documentation for new xMatters connector
* Begin working on functional tests
* Continue work on frontend for xMatters conenctor
* Continue work on backend for xMatters conenctor
* Continue work on the functional tests for the xMatters connector
* Update based on xMatters string reviews
* Remove hidden parameters from ui
* Continue working to get tests running successfully
* Fix my code after rebasing onto latest main
* Fix the xMatters server for the simluator
* Check if listening before listening to the xmatters server in simulator
* Continue work on improving the xMatters connector
* Update strings based on the xMatters team string review
* Remove the headers as an option for the xMatters connector
* Fix alignment of the xmatters logo on the connectors page
* Allow alertId and alertActionGroupName to be null in the xMatters connector for test requests
* Fix the functional tests for the xMatters connector
* Rename alertName to ruleName and remove headers from xMatters connector
* Continue removing headers and renaming alertName to ruleName
* Update the tests so all are passing
* Some clean up for the xMatters connector
* Update the doc images based on changes for the xMatters connector
* Change alert id to use rule id and alert id and be labeled as signal id in the xMatters connector
* Fix failing tests for xMatters connector
* Start addressing comments and failing builds
* Combine if statement
* Update test strings after updating error strings
* Begin making updates after discussions and reviews
* Update failing tests
* Few adjustments after my self review of the xMatters connector
* Fix one failing test
* Fix a few small bugs in the xMatters connector
* Address a few small bugs in the xMatters connector
* Address latest comments and fix a few tests on the xMatters connector
* Adjust naming of secretsUrl and configUrl
* Work on fixing tests for xMatters connector
* Begin updating the xMatters documentation
* Update based on build errors
* Update documentation typo
* Add validation tests for connectors created using the API
* Fix the failing functional tests
* Update docs after review from xMatters team
* Update accidentally duplicated translate id
* Fix small bugs and update based on xMatters team string reviews
* Fix failing tests due to string changes
* [DOCS] Fixes doc build errors
* Update based on comments and feedback
* Update docs based on feedback
* Fix failing functional tests
* Update based on the feedback
* Fix failures in the functional tests
* Remove accidentally added file
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: lcawl <lcawley@elastic.co>
* add back monitoring.ui.metricbeat.index and deprecate
* add back to test
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Removing minimumScheduleInterval on rule type registration
* Adding minimumScheduleInterval to config and enforcing in rule type registry
* Validating interval on create and update
* Fixing types and tests
* Fixing types and tests
* Fixing types and tests
* Passing config to client and using to validate on rule creation
* Fixing small bug and tests
* Fixing tests
* Fixing tests
* Fixing tests
* Updating interval in docs
* Updating interval in docs
* Updating UI copy
* Fixing types and tests
* Fixing i18n
* Fixing tests from bad merge
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
