Using data to drive design decisions
So far, we’ve discussed the importance of observability data for self-service and developer satisfaction, but not all other use cases for the telemetry data an IDP can collect. Data is a powerful asset that can be used to aid decision-making and help in cost and time savings. For example, when looking at two solutions that seem to split the middle on solution fit and technical debt, it can be hard to know which direction to go. This is where you can leverage data to make your decisions, and to keep track of your technical debt.
Nearly all the data your team will need to leverage for decisions will either already be in your observability solution or be an easy addition to it.
Observability is key
After spending all the time and effort to set up an observability stack and collect and retain data, it would be almost irresponsible to only use that data for incident management and response. Fortunately, platform teams are rarely accused...