Open ghost opened 3 years ago
@andrewseling - do you currently use the "Combine SLOs" view at all? If not, that can probably be repurposed for this case.
I do not, but I agree that it would probably work for this use case with a few upgrades.
From: Keagan Peet notifications@github.com Sent: Wednesday, October 14, 2020 8:17:42 AM To: newrelic/nr1-slo-r nr1-slo-r@noreply.github.com Cc: Andrew Seling andrew@andrewseling.com; Mention mention@noreply.github.com Subject: Re: [newrelic/nr1-slo-r] Add user journey view for end-to-end SLO reporting (#124)
@andrewselinghttps://github.com/andrewseling - do you currently use the "Combine SLOs" view at all? If not, that can probably be repurposed for this case.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/newrelic/nr1-slo-r/issues/124#issuecomment-708362605, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHIBOKFZPAZDMPQTFMNMW3SKWJGNANCNFSM4SNCAM4A.
can be closed. Added in https://github.com/newrelic/nr1-slo-r/pull/133
Summary
SLOs are defined at the level of individual systems or services (e.g. a single entity in NR). This is useful for services operators to understand how their service is behaving, but doesn't reflect the end user experience when services are chained together in deep dependency trees.
Desired Behaviour
I would like a user journey view that allows individual SLOs to be associated with a user journey such that I can quickly see and understand:
As an executive, I want the ability to see the status of my critical user journeys at a glance, whether I'm meeting my across the board, and if not, which service owner I need to talk to.
As a service owner or operator, I want to understand how my dependencies might be negatively impacting my SLOs, and how I might be negatively impacting my upstream services SLOs so I can take corrective action.
Possible Solution
Blameless.com has a basic implementation of this feature. We might be able to redesign the composite view to have a) saved views, b) funnel view of SLOs, and c) lowest attainment, rather than average.
Additional context
We have deep dependency chains. Front end services that are accessed by users with their browser may go half a dozen "hops" into the backend, and the backend services have their own dependencies. These "hops" often cross organizational boundaries and technology stacks, making it difficult to identify the constraint that needs to be improved for overall system performance to improve.
At minimum, I would like a view that makes it obvious how a particular business process functions and how well it is working, but future enhancements might also include a way to "walk the graph" of services/SLOs based on defined relationships.
@khpeet