%% date:: [[2023-11-26]] parent:: %% # [[Aggregating monitoring data]] Once the information has been [[Telemetry collector|collected]], a recommended practice is to practice [[Separation of Concerns]] by having the data sent to a separate service or component for aggregation, visualisation, and analysis. Having a separate component reduces the chances of the monitoring itself affecting the reliability and functionality of the system. ## Ways to aggregate [[Telemetry]] The traditional way of monitoring is called [[Push-based monitoring]]. This approach involves an agent installed in the server containing the service that is generating data. The agent converts metrics and sends them to the monitoring server. The disadvantage of this is that when many services are sending data to the same server, monitoring can be the bottleneck as the monitoring server struggles to deal with many requests at the same time. This is sometimes called _passive monitoring._ [[Pull-based monitoring]], or _active monitoring_, is different in that data is simply "exposed" by services, and the monitoring server is responsible for retrieving that data.