<div dir="ltr">Just to clarify; Are you talking about an almighty specific ops dashboard for our services/deployment, or a dashboard service that almighty provide for the users of almighty for their apps (or possible an almighty service ops now that evolves to a user service later.. ;) ?<div> </div><div>-aslak-</div><div> </div><div> </div></div><div class="gmail_extra"> <div class="gmail_quote">On Sun, Sep 11, 2016 at 12:13 AM, Karanbir Singh <<a href="mailto:kbsingh@redhat.com" target="_blank">kbsingh@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'd like to start the conversations around the application dashboard, what it might look like and how we might achieve it. An application dashboard is a single endpoint that should give the user[1] an overall 'state' of play, along with history for the evolution of present state. It should include: - - tested state of the services, their end points and resource / deployment bits - - All the stateful components, db's, key val's etc - - The state of the infra running the app itself - - State of code evolution, by way of current commit hash's deployed for various services etc - - logs: of the app, from the app, of the infra under the app - - metrics: of the app, from the app one additional piece that I always try and get, and have found it very useful in the past, is to track the major dependencies upstream and report them into this app dashboard as well. eg, if we are investing in nodejs4.x; tracking their release; similarly if we rely on a specific feature in openshift we should track that as well. At the broad macro level. Think of it as the devops dashboard, it might itself service the content beyond some meters or red/yellow/green lights, but would host links to the relevant places where we deliver the content behind it. [1]: The user in this case would be the operations interested parties, the product and project management groups and most developers contributing into the codebase. regards, - -- Karanbir Singh, Project Lead, The CentOS Project, London, UK Red Hat Ext. 8274455 | DID: 0044 207 009 4455 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJX1IV0AAoJEI3Oi2Mx7xbtXMgH/3CjN7IHUM0dQqn2wE4Cjd9t bpeklJsZ/3NtbaqpP/k0aKXKBKgfXzH/50ZZdQl3tFuJ/RcQkaCCG/gfNXYK1hKU hzHxgrM3KG5UK3cIgjtMCe7LRd1zZbvU7dlgqTIq/ZJI3dBlY9ssP2vApXYPhgr+ YrvW3dmuwmQ56e1fSFmFZA/+kwKH8jb/MBiarna76+VEPvrgf0KimHPds1Uyv4or n4LvlQMs5NXh3+e64pvFALJ6Mj+61aqgkGuEWrx5oXHgXUqbc/EboVx+++Xn/cvd /gz66ELNL7JB2phBDqRN8ihXdy6FFuWpANCVxJZfWqYz3UCZDQx8DvwxmIccob0= =mhfo -----END PGP SIGNATURE----- _______________________________________________ almighty-public mailing list <a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/almighty-public</a> </blockquote></div> </div>