Hi All, Currently there is a PR[1] open for this Saga Management Console implementation but this PR is using '/events' from the alpha server which is just open for test profiles + the events api gives a lot of information which might not be relevant to the Saga Console and will result in lot of processing of data on the client browser. So I propose to add a few api's[2] in alpha server for Saga Mangament Console which will be used by the UI to display the relevant data. These API's can also be used by third party to implement their of own UI/Console/CLI for Saga. The complete proposal for the API is available here [3], please review and provide your feedback. [1] https://github.com/apache/incubator-servicecomb-saga/pull/317 [2] https://app.swaggerhub.com/apis/ServiceComb/SagaManagamentConsole/1.0.0 [3] https://cwiki.apache.org/confluence/display/SERVICECOMB/Saga+Management+Console+API%27s Regards Asif
On 2018/09/19 03:17:12, Willem Jiang <willem.ji...@gmail.com> wrote: > On Wed, Sep 19, 2018 at 12:21 AM Mohammad Asif Siddiqui > <asifdxtr...@apache.org> wrote: > > > > Hi All, > > > > Recently I was exploring Saga and I came across Saga Web[1] module which > > helps to create Saga Request and View the Results but I was not able to > > find any web based UI where I can see the list of all the transactions or > > view the transactions based on the status, microservices or tx-id. > > > > So I want to propose a Saga Dashboard which can list all the transactions > > and analyse the success and failure transactions which can be helpful for > > Users/Developers both in development as well as production env. > > > > The informations which can be shown in the UI is listed below : > > 1. Recent Transactions Trends( Last 7 Days) > > 2. Recent Successful Transactions( Last 7 Days) > > 3. Recent Failed Transactions( Last 7 Days) > > We don't know how much transactions there, I'd like to be able to do > some configuration for the time. > > > 4. Total Transactions > > It could be count by Saga or TCC transaction. > Each Saga/ TCC may have different MicroServiceName, admin may need to > find out the highest failure rate of MicroSerivce. > We can let the admin drill down to the sub transactions. > > > 5. Total Failed Transactions > > 6. Total Successful Transactions > > 7. Preview of Successful Transaction (Last 24 Hours) > > Not sure if it OK, maybe we can add last 5 mins? > > > 8. Preview of Failed Transaction (Last 24 Hours) > > 9. List of All Successful Transactions > > The could be lots of Transactions there, we need to let the user search it > > > 10. List of All Failed Transactions > > This is most important thing that we want to show to the admin, it > should be easy for the admin find out the which subtrancation is > failed and the failed reason. > > > 11. Search Transactions based on MicroService Name > > 12. Search Transactions based on Tx ID > > 13. See the Transaction hierarchy based on Tx ID > > > > A draft proposal for this dashboard is available here[2]. > > > > Please feel free to give a feedback/comments to make this UI better and > > useful to the Users. > > > > [1] > > https://github.com/apache/incubator-servicecomb-saga/tree/master/saga-web > > [2] https://github.com/asifdxtreme/Docs/blob/master/Saga-Dashboard.md > > > > Regards > > Asif > > >
