Performance Analytics Breakdown shows error

Pavithra R2
Tera Contributor

Hello all,

I have developed a breakdown for Requested Items based on Item. But the breakdown shows 'no element to display'. In the Breakdown source I get a error 'This breakdown source was automatically disabled because the number of elements exceeds the maximum allowed as defined in the Properties'. Could any one suggest if I need to update any performance analytics property value? And if so, is it a good practice to modify any performance analytics value? I have attached the screenshots below.

 

PavithraR2_0-1722269979494.pngPavithraR2_1-1722269995590.png

 

Thanks and Regards,

Pavithra

 

 

3 REPLIES 3

Slava Savitsky
Giga Sage

This error means that your breakdown has too many distinct elements. As this can cause performance degradation, the system stops data collection for an indicator where the number of breakdown elements exceeds the value of "com.snc.pa.dc.max_breakdown_elements_limit" system property (default value is 10,000). The indicator also gets deactivated ("DC active" checkbox on the form). Rather than changing the value of the system property, it is recommended to review the breakdown configuration.

 

What it the value of the system property in your instance? If it has the default value, is it possible that you have more than 10,000 different catalog items? If this is not the case, there must be a configuration issue in your breakdown.

 

For more information, refer to the following article from the product documentation:

Performance Analytics properties

Hello,
I have checked the system property value and its default value is 10000. Also, I have checked the number of catalog items. It is around 200. But I'm not able to figure out why this error shows. I have attached the screenshot of breakdown source below.

PavithraR2_0-1722328137747.pngPavithraR2_1-1722328159423.png

 

 

Thanks and Regards
Pavithra

Bert_c1
Kilo Patron

Data Collection Job logs are very helpful. More folks should review those. And a breakdown field should be one with limited choices/values.  Creating a breakdown on a sys_user field, for example, has little to no value.