Observability

There are two ways that you can find potential problems with your game: monitoring and observability. Observability is where you set up your game in a way that reveals what’s going on under the hood. It’s about getting insights into your game and diagnosing problems.

How might you use observability?

Observability is all about revealing internal parts of your game. For example, you might set up your game to send a player’s latency. You could then collect this data from multiple devices. Combining this with your server metrics, you could find the root cause of any lag that might be happening.

How do observability and monitoring differ?

The two are very similar. It’s best to think of monitoring as reactive, while observability is proactive. Monitoring is essentially making sure that you are collecting the data you need in a way you can review. While observability is about showing you underlying problems.

Back to Glossary