# Major changes in prometheus collector can be reverted ?

**URL:** https://community.netdata.cloud/t/major-changes-in-prometheus-collector-can-be-reverted/3962
**Category:** Help
**Tags:** agent, collectors
**Created:** [March 14, 2023, 10:47am UTC](https://community.netdata.cloud/t/major-changes-in-prometheus-collector-can-be-reverted/3962 "2023-03-14T10:47:53Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![t.gar](https://avatars.discourse-cdn.com/v4/letter/t/5f9b8f/32.png) [@t.gar](https://community.netdata.cloud/u/t.gar)
#### Post date: [March 14, 2023, 10:47am UTC](https://community.netdata.cloud/t/major-changes-in-prometheus-collector-can-be-reverted/3962/1 "2023-03-14T10:47:53Z")

</div>

i have just upgraded my netdata agent from 1.36.0 to 1.38.1 and i notice some big change on prometheus collector behavior, so we loss prometheus grouping graph (usefull for analysis) and alarm’s. Is it possible to have same behavior than before in the new version of prometheus collector ?  
example :

# HELP com\_siemens\_polarion\_license\_current com\_siemens\_polarion\_license\_current

# TYPE com\_siemens\_polarion\_license\_current gauge

com\_siemens\_polarion\_license\_current{statistics\_name=“Named\_XBase”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Named\_Requirements”,} 2.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Concurrent\_TFS Add-on”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Named\_Reviewer”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Concurrent\_XEnterprise”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Named\_Xcelerator Add-on”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Concurrent\_QA”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Concurrent\_Xcelerator Add-on”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Named\_XPro”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Named\_Pro”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Concurrent\_XBase”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Named\_ALM”,} 2.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Concurrent\_XPro”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Concurrent\_Reviewer”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Concurrent\_ALM”,} 1.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Concurrent\_Requirements”,} 6.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Named\_TFS Add-on”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Named\_QA”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Named\_XEnterprise”,} 0.0  
com\_siemens\_polarion\_license\_current{statistics\_name=“Concurrent\_Pro”,} 0.0

old behavior

 ![netdata_lic_old](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/2X/b/bc339ea94db8378ac6b9327591baa53176f171ed.png)

new behavior we get 20 graph’s like

 ![netdata_lic_new](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/2X/4/4104f4f949bf718c38b65a2083aa5cb607165c2d.png)

---

<div class="post-metadata">

### Author: ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)
#### Post date: [March 14, 2023, 11:00am UTC](https://community.netdata.cloud/t/major-changes-in-prometheus-collector-can-be-reverted/3962/2 "2023-03-14T11:00:56Z")

</div>

Hi, @t.gar. No, it is not possible to revert the changes/have the same behavior as before.

- You can have ~ the same chart if using Cloud UI and change “group\_by” of the chart to “statistics\_name”.
- Yes, alarms need to be rewritten. But in many cases, it was not possible to apply an alarm with the old grouping at all.