# Idea for Elastic Observability Blogs or Documentation

**URL:** <https://discuss.elastic.co/t/idea-for-elastic-observability-blogs-or-documentation/381319>\
**Category:** Elastic Observability\
**Created:** [August 25, 2025, 6:22pm UTC](https://discuss.elastic.co/t/idea-for-elastic-observability-blogs-or-documentation/381319 "2025-08-25T18:22:36Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [August 25, 2025, 6:22pm UTC](https://discuss.elastic.co/t/idea-for-elastic-observability-blogs-or-documentation/381319/1 "2025-08-25T18:22:36Z")

</div>

Hello,

I wanted to share an idea about how elastic can improve their “monitoring” use cases. I am not sure where to share my ideas.

So, currently Elastic Agent with integrations is one of the quickest ways to get data into Elastic. Some integrations come with their own dashboards. This is great and more integrations are getting added!

**But** I would like to take this a step further. Introduce the concept of “Packs”. These “packs” are more use-case based and are essentially a way to monitor something specific using existing integrations.

For example, your use case is to monitor Domain Controllers. Elastic can offer “Domain Controller pack” where it will utilize:

- **Custom Windows Integration** (to collect Directory Service event logs)
- **Windows integration** (to collect Standard Windows Event logs and Perfmon Counters)
- **Systems integration** (to collect System Metrics and Windows Services)
- Specifications on “ **DC Services** ” to monitor
- Specifications on perfmon counters like “ **LDAP Client Sessions** ”)
- Dashboard showing all of the data under “ **DC Overview** ”
- ML jobs to run to detect anomalies

Why is this beneficial:

- Leveraging existing integrations
- Customers can consolidate their old traditional monitoring tools with Elastic
- Allows for more community-driven use cases
- Eliminates dashboard context switching, one dashboard contains all useful information

Example of the dashboard (inspired by other observability solutions 🫣 ):

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/e/aee2196d525f4394100c658b51012532b34d618a.png)

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [August 27, 2025, 6:53pm UTC](https://discuss.elastic.co/t/idea-for-elastic-observability-blogs-or-documentation/381319/2 "2025-08-27T18:53:24Z")

</div>

Thanks for sharing this, @erikg . Have you considered creating feature requests for these ideas?

---

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [August 27, 2025, 9:54pm UTC](https://discuss.elastic.co/t/idea-for-elastic-observability-blogs-or-documentation/381319/3 "2025-08-27T21:54:11Z")

</div>

@jessgarson Thanks for the suggestion. I wasn’t sure what repo would this apply in?  
Kibana? Integrations?

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [August 27, 2025, 10:33pm UTC](https://discuss.elastic.co/t/idea-for-elastic-observability-blogs-or-documentation/381319/4 "2025-08-27T22:33:36Z")

</div>

I was thinking Kibana.

---

<div class="post-metadata">

**Author:** ![erikg](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@erikg](https://discuss.elastic.co/u/erikg)\
**Post date:** [August 27, 2025, 10:48pm UTC](https://discuss.elastic.co/t/idea-for-elastic-observability-blogs-or-documentation/381319/5 "2025-08-27T22:48:57Z")

</div>

> [@erikg](#):
>
> Example of the dashboard (inspired by other observability solutions 🫣 ):

Done!  
[[Observability] Introduce "Packs" · Issue #233227 · elastic/kibana](https://github.com/elastic/kibana/issues/233227)

Thanks! @jessgarson

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [September 2, 2025, 4:12pm UTC](https://discuss.elastic.co/t/idea-for-elastic-observability-blogs-or-documentation/381319/6 "2025-09-02T16:12:57Z")

</div>

Thanks again, @erikg. I also shared this post with our content team as well too,