Conclusion

In this lesson, you learned about a different approach for your APIs instead of returning spans for developers, and they have the responsibility of managing them. You take over this responsibility inside your framework which can drastically reduce the integration effort. You learned about controlling the amount of telemetry to send from your app and how to increase it or reduce it through configuration that you can change in runtime.

Finally you learned about the risks of adding user’s information in your telemetry, and how critical it is to be mindful on user data.

OpenTelemetry and Grafana can greatly improve your understanding of your apps’ performance directly from the users’ perspective. They provide insights into what might be going wrong and help you analyze problems easily through graphical representations, without having to go through hard-to-comprehend text logs. A picture is worth a thousand words, and in this case, a graph can be worth thousands of logs.

Additionally, you integrated Apple’s MetricKit framework allowing you to receive valuable metrics about your app, even crashes.

Understanding your app performance from Xcode is one thing, and understanding how it performs at scale is another. With app observability, you can make your apps much better in shorter time.