What is Andon
Japanese name for a visual production-control device (usually a lighted overhead display) that continuously shows changing status of the production line and sounds alerts if a problem is imminent
Read more
One of my colleague recently came up with cool TV app that uses above concept to display the status of all upstream and down steam systems related.
In a agile environment when you are developing a complex application and you have your QA,staging ,dev environments ,you have teams testing on that continuously.
QA : we don't see this working ,we are not getting any response from this
Dev : its working fine in our env.
so now we check if it same version ,check the logs for errors ,and finally after some time you will come to know that some serer /db /service has wrong version or down.
Now if you have this Andon board you will see whats wrong by looking at the Big TV before you.so no need to spend time in checking what went wrong instead you can directly see whats wrong or in-fact you can customize your board to sound an alarm to signal if something critical is down.
Continuous integration : take advantage of continuous integration environment of your agile team as one feed for your Andon board.
Now how to design this:
1.List all the upstream or downstream systems , HTTP services JDBC services a,JMS services:
try a simple test of pinging the service or DB query to check if these services are up in your environments
do not list the ones which you don't need. No need to add the versions deployed etc.
if you have more.. try to group them logically ,so the you know overall status ,and when you click on the group that should list the ones in group.
2.Servers on which your apps hosted : get if server is up or down or needs a restart
3.how many environments like QA ,Dev,Prod : list the versions deployed in each environment
4.list whats critical and when you want to alarm the team
like in prod if some service is down
5. Use color coding like reds when some thing is down
6. Do not clutter your screen with unnecessary details.
Have a online url for your board if your team is split across geographical locations .
Japanese name for a visual production-control device (usually a lighted overhead display) that continuously shows changing status of the production line and sounds alerts if a problem is imminent
Read more
One of my colleague recently came up with cool TV app that uses above concept to display the status of all upstream and down steam systems related.
In a agile environment when you are developing a complex application and you have your QA,staging ,dev environments ,you have teams testing on that continuously.
QA : we don't see this working ,we are not getting any response from this
Dev : its working fine in our env.
so now we check if it same version ,check the logs for errors ,and finally after some time you will come to know that some serer /db /service has wrong version or down.
Now if you have this Andon board you will see whats wrong by looking at the Big TV before you.so no need to spend time in checking what went wrong instead you can directly see whats wrong or in-fact you can customize your board to sound an alarm to signal if something critical is down.
Continuous integration : take advantage of continuous integration environment of your agile team as one feed for your Andon board.
Now how to design this:
1.List all the upstream or downstream systems , HTTP services JDBC services a,JMS services:
try a simple test of pinging the service or DB query to check if these services are up in your environments
do not list the ones which you don't need. No need to add the versions deployed etc.
if you have more.. try to group them logically ,so the you know overall status ,and when you click on the group that should list the ones in group.
2.Servers on which your apps hosted : get if server is up or down or needs a restart
3.how many environments like QA ,Dev,Prod : list the versions deployed in each environment
4.list whats critical and when you want to alarm the team
like in prod if some service is down
5. Use color coding like reds when some thing is down
6. Do not clutter your screen with unnecessary details.
Have a online url for your board if your team is split across geographical locations .
No comments:
Post a Comment