resolves https://github.com/elastic/kibana/issues/60135
See the reference issue for how to configure Kibana to test this manually.
There are no automated tests for this ATM.
The basic test scenario is to create a role with just the Uptime space
privilege, make sure it get to the Alerts and Actions management app,
make sure you can create an action (server log), and alert (index threshold),
and that the alert and action run successfully.
Then repeat with just the Metrics space privilege.
* Migrated sample_action to NP. Panel action tests returned to the test flow.
* fixed names
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
When Kibana is certain actions (connectors) disabled due to insufficient licensing we now display buttons that lead to both the Subscriptions page and the License Management page (where the user can start a trial).
Fixes handling of default and advanced search on the summary view of the define step.
- Before this, default searches would should up in the Query section, they are now hidden.
- Before this, instead of the full query DSL, only the query string would be shown when the advanced query editor was used.
resolves https://github.com/elastic/kibana/issues/54920
The scenario this message warns about is actually something that we should
expect to happen in a busy system - and we back off as we should. But
there's no reason it needs to be info-logged, especially as it seems
somewhat frightening.
Changing to debug, so in case we do need this for diagnostic purposes, we
can still get it via logging config.
* Fix validation for index threshold when selecting an index
* Ensure timeField gets validation message
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
UI Performance could degrade to make a page unusable if a dataset had a very much number of columns to be displayed in data grid (e.g. filebeat based date with 1000+ fields).
This PR fixes it by limiting the columns selected by default to a maximum number of 20. The fix gets applied to Transforms Source Table and Pivot Preview as well as the Analytics Outlier Results page.
This adds the --no-base-path flag and also enables endpoint. I think we should get used to always running endpoint too.
This also adds the bootstrap step as if this is missing, things often break.
Elasticsearch master is now returning a different order for these
fields and is failing the promotion of our nightly builds.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
There's a race condition with our rule creation tests where if they're
executed we'll get a failure message in the response, but if they
haven't yet executed we won't.
This ultimately seems like a bug with this
removeServerGeneratedProperties helpers, which has been updated to
remove those failure properties as well.
* add functional test
* update func test
* refactor more changed
* update test
* update test
* update type and test
* fix the fix of fix, which din't get fix
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Add action variables for monitor status alert.
* Translate action variable descriptions.
* Add state variables to list. Update defaultActionMessage.
* Remove non-literal characters from test names, and update outdated snapshots.
* endpoint-161-refactor-management-list-test
* fix location of es archive file
* restored missing data and added new tests
* remove commented out code
* implement suggested enhancments
* fix api tests to use the restored data
* add endpoint metadata to the alert es_archive
* restore the original alerts/api_feature archive
* skipped failing endpoint alert tests
* implement Policy Details header
* use Ingest APIs to persist (save) policy data to the Datasource
* implement UI behaviour for Save, Cancel
* implement UI bahaviour for when Policy (datasource) can not be retrieved
* [ci/es] always pull snapshots, break early when they're not available
* move to setup.sh after deps are installed
Co-authored-by: spalger <spalger@users.noreply.github.com>
* Hide APM alerting menu if alerting plugin is disabled
Checks for presence of plugin and does not display the link if the plugin is disabled.
Use `xpack.alerting.enabled: false` in config/kibana.dev.yml to try it.
Fixes#61048.
