cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Split by Country Visit

jose-antonio_ra
Inactive

Hello,

we have a BT that
makes a split for the measure “Country of Visits”, but the following error
appears:

Can someone help me?
How can I know the network contribution and server contribution from each
geographical locations?

Thanks in advance.

Cheers,

Jose A


3 REPLIES 3

Radu
Dynatrace Pro
Dynatrace Pro

Hi Jose,

Please post a definition of your "BT - Contribucion por Oficinas" Business Transaction.

It's clearly not working as intended since there's only 195 countries in the world and our built-in limit for splittings is 50,000 before we disable the BT.

Best regards,

Radu


jose-antonio_ra
Inactive

Hi Radu,

The BT definition is:

This is measure Country
ofVisits:

And this should be the
result:

thanks and best regards,

Jose A


Radu
Dynatrace Pro
Dynatrace Pro

Hi Jose,

From what you posted I see that the 'Country of Visits' has been modified to get more granular level of detail. This granular detail, overall, seems to have breached the 50k built-in limit for splittings.

Your options in this case are to adjust the way splitting occurs for this BT (more on this here😞
  • Specify a maximum most frequent number of splittings (so only top X most frequent locations will be shown as separate splittings, the others being aggregated as <...>)
  • Specify a fixed maximum number of splittings (same as above, but splittings will be shown as they come in rather than by popularity)
  • Specify a minimum % contribution (so if a location has at least x% of total transactions it will be reported as a separate splitting, otherwise will be aggregated as <...>)
  • Add a flag on the server.ini file to override and raise the built-in limit of 50k (as instructed by the alert message you shared) - although not entirely recommended since 50k is already quite a high threshold
  • If you don't actually use this BT's data for longer term charting and trend analysis, then you can disable storage to the Performance Warehouse altogether. This will leave you with only 'live' data to look at (e.g. ~1hr).

More about excessive splitting can be found here

Finally, if you think that there's no way this BT definition could have generated >50k splittings, it may be possible that the current BT has gone through a few configuration changes and it used to be more aggressive on splittings before this current definition and nobody cleared the previous config data from the system so old splittings might still be in with the new ones. If this sounds familiar then I would recommend first clearing all data from performance warehouse and see if the 50k limit is still reached.

Best regards,

Radu