Which of the following are examples of events?

In the context of monitoring and observability, events represent significant occurrences in a system that can be logged and tracked to provide insights into system behavior, performance, and changes. Code changes are a prime example of an event because they denote a specific alteration in the codebase that could impact application performance, functionality, and behavior. Tracking code changes as events helps teams understand the context around performance issues or bugs that may arise after a deployment.

Events like the end of a sprint or alerts also have their own significance, but they do not fit the definition of events in the same technical capacity. The end of a sprint is more of a project management milestone rather than a system behavior change, while alerts—though they prompt action—are typically responses to incidents and are derived from monitoring systems rather than events themselves. Throughput, on the other hand, is a performance metric that quantifies the amount of processed data over time, but it is not an event in isolation.

Thus, code changes stand out as clear, definitive instances that can trigger logging and analysis, making them exemplary representations of events in monitoring contexts.