BT Splittings and best practises
I am using "Web Page Requests" (Built-in) BT in the application overview to monitor and get alerted on the response times. But this keeps getting disabled as it reaches more than 50k splittings. Does this mean at any time the splittings are more than 50k? When i looked at the chart in the meaure health dashboard, i see that in the top contributors it has around 50k count continuously.
I have bumped that limit to 75k by adding the below entry in dtserver.ini. But i just want to find out what is the best practice on this and how big we can go on this limit? should i restrict the splittings (for example Aggregate to common URI patterns - minimum 5%) so that i don't have that many splittings? if i restrict i am worried that i might miss some of the key transactions. I am thinking to create a separate BT to include key transactions only and reduce the splittings on the current one. what do you guys suggest? I don't have any custom alerts for individual transactions i am just relying on the auto alerts from the baseline learning of dynatrace and violations settings for that BT.
-Dcom.dynatrace.diagnostics.server.OverruleMaxSplittingsBTs=SystemProfilename:Web Page Requests=75000
Hi. The Built-In BT should actually have a "Smart Splitting" option that only looks at the e.g: Top 50 URLs or the Top 5%. Have you by any chance changed the configuration of that BT? Please double-check.
General Info:
A BT that crosses the 50k (or in your case 75k) limit will simply stop producing measures we write in the performance warehouse for each splitting value. PurePaths will however still be tagged with the BTs that they are mapping to. This allows you to use the BT Dashlet or a BT Filter on a PurePath-based dashlet to anlayze specific splitting values.
IT IS NOT RECOMMENDED to produce measures for BTs with that many splittings - thats also why we have the limit in there. We assume that nobody wants to chart the 50k individual measure points but just wants to use the BT to help with faster root cause diagnostics by using this BT as a filter.
Andi
Hi Andi,
Yes i have changed the default setting.As i mentioned I am using this BT for monitoring in the application overview and getting alerts based on the violation settings. I have changed the limit so that i don't miss any of the web requests that are important and hence i might miss alert on it in case of any perf issues. So if i restrict to 5% contribution, do you suggest that i should monitor another BT with all the key transactions that i am worried about?
Well - I dont think it makes sense if you have 75k Split values and get alerts on these. 99.9% of these URLs are probably useless for you.
The Best Practice here is to create your own BT (or BTs) that filter on your important requests that you want to monitor, e.g: Homepage, search, checkout, Product Pages, ...
These should be put on the Application Overview for Baselining.
