What generates "skipped disabled breakdown source? Thanks

[sbrecht]

What generates "skipped disabled breakdown source?   I am getting this warning from a data collection job.   How do I fix it? Thanks

[Vincent Loffel1]

Hi Sally,

Couple of questions:

Have you changed something in the breakdown sources?

Which data job generates the error?

Are you on Eureka or Fuji?

Are you using Performance Analytics Premium pack or complementary?

Could you otherwise post the entire error?

Cheers,

Vincent

[sbrecht]

Hi Vincent,

Actually, I am playing in the Development environment and I created both the data collection job and the breakdown. The Dev environment is Eureka patch 10 or 11 and this is not a complimentary copy. The entire error is below. Please don't trouble yourself with the java script error as I will get help here. Thanks!!

[Jochen Pohle]

Hi Sally,

have a look at the Breakdown Source mentioned as "disabled" in you DC Job log, you will something like this:

The Breakdown Source has been disabled because you exceeded the limit set by the Data Collector property "Maximum number of breakdown elements for a breakdown to be included in data collection". Please do not change that property lightly.

Instead I recommend you apply additional filters for your Breakdown Source.

And don't forget to mark the Breakdown Source "DC active" again.

Hope this helps,

Jochen

[mike_bush]

Fuji - I am getting this message - the Breakdown Source is NOT named in the warning message!

The best I can do is see that the sequence for the messages (*3) comes after a line Processing Indicator Source Incidents.Resolved

The "DC Active" field is not on the form but can be seen in a list - all sources are marked TRUE

Where to next?