-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
2.5
-
False
-
-
False
Hello, summarizing here my feedback on the Event Stream details page and its usage.
I saw lots of demos and presentation around AAP Event Driven functionalities, anyway getting hands-on the product feature for building a customer's demo, I found some things that could be improved in the UI (that could request also some changes under the hood).
I was integrating OpenShift's AlertManager webhook receiver to send alerts to an Ansible EDA Event Stream created in AAP to then starting some automation on the OpenShift cluster. Unfortunately I put the wrong credential on the OpenShift AlertManager webhook receiver and I was struggling to debug the authentication problem.
- The test mode of the Event Stream should be highlighted and should have a dedicated section in the documentation (maybe titling it "Troubleshooting"), it was not so easy to understand that I need to disable the Event Stream to enable this "test mode".
- Even after enabling the "test mode" it is NOT so intuitive to find (just) the latest event received in the "Details" tab, this is usually cut by the web browser and you need to scroll down to see it.
- In case of Authentication issues, there is NOT any evidence that let you assume from server side (so from AAP side) the type of Error returned to the client: no error code, just the received header. As you can imagine going in to the client side to see if any error is not always possible (in a demo environment that could be fine, but in a customer environment the client may be managed by a different group).
- The counter of the "Events received" increase also if the authentication is wrong BUT it does NOT increase if you just remove the Authentication header/options.
Given all the previous comments, my suggestion would be:
- Create a dedicated tab / page to show the last (or even more incoming request) with more details and reporting also the server answer (error 403, for example).
- Improve the documentation to highlight how to troubleshoot and enable this "test mode"
Customers may benefit from these improvement for troubleshooting common issues and save time in their AAP EDA configuration (that very often involve 3rd party platform managed by different groups in the company).
Thanks!
BR