You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
A question for the Compass development team...
We monitor all our services but when things go wrong with them it's not always obvious how that affects end-user experiences, which often involve multiple services. Sometimes there's no impact because of resilience or redundancy. Other times there's major impact on a bunch of user experiences, but the person called out may not be aware of all the dependencies so doesn't realise.
What we need is a way to represent our end-to-end user experiences in Compass as components, so we can keep track of the most important ones and their dependencies on services and other components. We'd need API end-points to feed in data on performance of those experiences in production. They could have score cards that show how well we're doing at making those experiences smooth and reliable.
Is that something being considered as a future Compass feature?