# Changelog for Elastic Agent Integrations **URL:** \ **Category:** Elastic Observability\ **Created:** [June 25, 2022, 9:47am UTC](https://discuss.elastic.co/t/changelog-for-elastic-agent-integrations/308159 "2022-06-25T09:47:25Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\ **Post date:** [June 25, 2022, 9:47am UTC](https://discuss.elastic.co/t/changelog-for-elastic-agent-integrations/308159/1 "2022-06-25T09:47:25Z")
The assumptions seems to be that we upgrade these integrations without easy access to know what we are upgrading or what potentially could break and what has been fixed. We have changelogs for all other components in a set location (example in Docs for each application). If i wanted to see the fixes and breaking changes for Beats, this was where they we located ! Why can this be the same for these integrations ? Consistency is important. ![Screenshot 2022-06-25 at 11.40.03](https://us1.discourse-cdn.com/elastic/original/3X/2/5/250139097d405e060f9e82bb78bd4dfc3fee3515.jpeg) ---
**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:35am UTC](https://discuss.elastic.co/t/changelog-for-elastic-agent-integrations/308159/2 "2022-11-04T08:35:59Z")