As an Elastic Cloud admin, I need to be able to grant my users the ability to create alerts within the Synthetics app without also granting them the ability to create tests from within the Kibana UI.
Details
We use the @elastic/synthetics Node.js library to create and deploy our synthetics tests. This allows us to develop and test user journeys offline, subject them to code review and version control, and use CI/CD for deployment. In short, it allows us to use best practices when developing and deploying tests to Elastic Synthetics.
However, our users also need to be able to create and manage their own alerts in the Synthetics app within Kibana. Currently, there are only three levels of access to the Synthetics app: (ALL|READ|NONE), and only ALL access grants users the ability to create alerts. But this also grants the ability to create tests from within the Kibana UI, which we do NOT want.
Request
Separate the ability to create alerts within the Synthetics app from the ability to create tests. In our situation, it would be acceptable to grant the ability to create alerts with the READ permissions, but I understand that this might not be generally desirable and while it would not be a breaking change, it would certainly change the current behavior of the application.
A better solution would be to create another permission level between READ and ALL called MANAGE ALERTS, which would grant access to perform CRUD operations on alerts in the Synthetics app. This would be a non-breaking change, as there would not be any change to access level or functionality for any of the three existing levels
Use Case
As an Elastic Cloud admin, I need to be able to grant my users the ability to create alerts within the Synthetics app without also granting them the ability to create tests from within the Kibana UI.
Details
We use the
@elastic/synthetics
Node.js library to create and deploy our synthetics tests. This allows us to develop and test user journeys offline, subject them to code review and version control, and use CI/CD for deployment. In short, it allows us to use best practices when developing and deploying tests to Elastic Synthetics.However, our users also need to be able to create and manage their own alerts in the Synthetics app within Kibana. Currently, there are only three levels of access to the Synthetics app:
(ALL|READ|NONE)
, and onlyALL
access grants users the ability to create alerts. But this also grants the ability to create tests from within the Kibana UI, which we do NOT want.Request
Separate the ability to create alerts within the Synthetics app from the ability to create tests. In our situation, it would be acceptable to grant the ability to create alerts with the
READ
permissions, but I understand that this might not be generally desirable and while it would not be a breaking change, it would certainly change the current behavior of the application.A better solution would be to create another permission level between
READ
andALL
calledMANAGE ALERTS
, which would grant access to perform CRUD operations on alerts in the Synthetics app. This would be a non-breaking change, as there would not be any change to access level or functionality for any of the three existing levels