Skip to content
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

[Automation Kit - Feature]: Include a COE Admin Command Center App in the Automation COE Satellite Solution that tracks its cloud flow errors daily and allows setting email alerts. #338

Open
bilodeauju opened this issue Aug 17, 2023 · 0 comments
Assignees
Labels

Comments

@bilodeauju
Copy link

bilodeauju commented Aug 17, 2023

Is your feature request related to a problem? Please describe.

The Automation kit is currently time consuming to troubleshoot when something doesn't work as expected. As an admin, you have to dig and look through potentially 18 cloud flows run history in a Satellite environment to find if there is a failure somewhere. This is especially true when you are new to the Automation kit and not yet familiar with how the different flows work.

For example, Satellite Solution flows can fail if a variable is missing or using an incorrect default value, and lead to unexpected behavior.

Example 1: #337. An automation kit tester inquired why some of the flow sessions for their metered cloud flows where not showing up in the Automation Center app in the Automation COE Main environment. There was no visible errors to hint where the failure came from and the tester initially believed they did something wrong or missed a step, so they didn't report the issue right away. After a lot of digging through the Satellite Solution flows run history, I found it was due to the flow "Sync Solution Metering Artifacts" failing. From there it was easy to find that a variable default value was causing the issue.

Example 2: #310. During early testing, we encountered an error in the Automation Solution Manager app when clicking on any solution, preventing us to see the flows within the solution to enable metering. Looking through the Satellite Solution flows run history, I found it was due to the flow ""Get Dataverse Solution Artifacts" failing. Again from there it was easy to find that a variable default value was causing the issue.

Describe the solution you'd like

It would be extremely useful to have an "Admin Command Center App" included in the Automation COE Satellite Solution that tracks its flow errors daily, with the option to set email alerts to multiple email addresses. This would ensure the alerts are sent to a mailbox that is monitored and for sync flow errors to be addressed proactively rather than react when an automation kit user notices and informs the COE admin that something isn't working as expected.

For reference, the CoE Starter kit includes an Admin Command Center App which makes it a lot easier to troubleshoot proactively. It has other neat features such as a screen to view and modify environment variables. A similar app would be a great addition to the Automation kit.

Describe alternatives you've considered

Just the ability to set email alerts to the email address(es) of our choice when an Automation COE Satellite flow fails would be a great improvement by itself.

Additional context?

List of flows in the Automation COE Solution. It can be time consuming to look through the flows run history when you are not yet familiar with the flows and don't know exactly where to look for potential flow run failure.
image

CoE Starter kit Admin Command Center App sync flow error screen. It is much easier and user friendly to look for flow run errors under one screen.
image

AB#464

@bilodeauju bilodeauju added the enhancement New feature or request label Aug 17, 2023
@biswapm biswapm self-assigned this Aug 22, 2023
@RajeevPentyala RajeevPentyala modified the milestone: Bulk Edit Nov 17, 2023
@RajeevPentyala RajeevPentyala modified the milestone: Bulk Edit Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

3 participants