%% Last Updated: - [[2021-02-20]] %% # [[Observability Platforms]] [[Observability]] platforms aim to become the primary source of data for all operational metrics of components in an application. ## Key features ### Integrations with monitoring tools The most important feature in an observability platform is in the integrations available with various monitoring tools. Observability platforms gain value the more comprehensive their reach is. ### Unified dashboard All metrics need to be presented in a single place that allows for custom dashboards to created. ### Notifications A good observability platform has several ways to notify engineers when certain criteria are met. ### Analysis and troubleshooting The farther you can drill down into the cause of an issue, the better. Dynatrace, for example, lets you add a special header in your [[Load Testing Tool|load testing tools]] to be able to track each request as it is received by application components. That way, you can see how much time the transaction spent at each "hop". ## Observability Platforms Observability platforms are an expansion of monitoring tools. While they sometimes come with their own monitoring agents, they usually integrate well with standalone monitoring tools and focus on the visualization and real-time decision-making part of the process. - [[New Relic]] - [site](https://newrelic.com/) - [[AppDynamics]] - [site](https://www.appdynamics.com/) - [[Dynatrace]] - [site](https://www.dynatrace.com/) - [[Datadog]] - [site](https://www.datadoghq.com/) - [[Splunk]] - [site](https://www.splunk.com/) - [[Honeycomb]] - [site](https://www.honeycomb.io/) - [[Lightstep]] - [site](https://lightstep.com/) - [[Grafana]] - [site](https://grafana.com/) - [[Victoria Metrics]] - [site](https://victoriametrics.com/) - [[Chronosphere]] - [site](https://chronosphere.io/) - [[Cribl]] - [site](https://cribl.io/)