# About the Elastic Observability category

**URL:** <https://discuss.elastic.co/t/about-the-elastic-observability-category/235255>\
**Category:** Elastic Observability\
**Created:** [June 2, 2020, 12:08am UTC](https://discuss.elastic.co/t/about-the-elastic-observability-category/235255 "2020-06-02T00:08:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 2, 2020, 12:08am UTC](https://discuss.elastic.co/t/about-the-elastic-observability-category/235255/1 "2020-06-02T00:08:06Z")

</div>

## Unified visibility across your entire ecosystem

Bring your [logs](https://www.elastic.co/log-monitoring), [infrastructure](https://www.elastic.co/infrastructure-monitoring) and [availability](https://www.elastic.co/uptime-monitoring) metrics, and [APM traces](https://www.elastic.co/apm) together at scale in a single stack so you can monitor and react to events happening anywhere in your environment. And it's free and open.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 4, 2022, 8:00am UTC](https://discuss.elastic.co/t/about-the-elastic-observability-category/235255/3 "2022-11-04T08:00:37Z")

</div>