At Capital One, says platform engineering fellow Dr. Tapabrata Pal (who goes by “Topo”), they have been doing DevOps for four years. During this time of using multiple tools, each with its own dashboard, they identified a need for a single dashboard that could view the whole pipeline in one single dashboard. Not finding anything in the commercial or open source markets, they decided to build themselves one. “It gets all the information from each individual tool, collects it in a central place and have a nice UI to show you the actual information coming out of these tools. The whole Idea is to shorten and amplify the feedback loop,” says Topo, citing the second of Gene Kim’s "Three Ways of DevOps." Topo suggests development teams who are working concurrently on isolated projects as a prime use case, in which the dashboard would signal to everyone if a build should fail, shortening the time it takes to determine the cause.
At Capital One, says platform engineering fellow Dr. Tapabrata Pal (who goes by “Topo”), they have been doing DevOps for four years. During this time of using multiple tools, each with its own dashboard, they identified a need for a single dashboard that could view the whole pipeline in one single dashboard. Not finding anything in the commercial or open source markets, they decided to build themselves one.
“It gets all the information from each individual tool, collects it in a central place and have a nice UI to show you the actual information coming out of these tools. The whole Idea is to shorten and amplify the feedback loop,” says Topo, citing the second of Gene Kim’s "Three Ways of DevOps."
Topo suggests development teams who are working concurrently on isolated projects as a prime use case, in which the dashboard would signal to everyone if a build should fail, shortening the time it takes to determine the cause.