过度分割的预防 Application Monitoring.pptx

过度分割的预防Application Monitoring什么是过度分割?性能仓库WRITING什么引起了过度分割?Metric: Web请求– URI 模式的值Query: /index?sid=9fih39684szbgh61ni8jr6rmyl3svyx5URI path: /9fih39684szbgh61ni8jr6rmyl3svyx5/index当出现过度分割的时候会发生什么?如何预防过度分割在性能仓库中控制存储结果改变分割选项对需求的业务分析进行再配置移除导致数据激增的分割选项 激活分割约束如何预防过度分割预防过度分割的选项:创建一个新的分析来解决过度分割的问题.在dtserver.ini文件中增加对所有分割的限制.或者在dtserver.ini 文件中增加对独立业务分析的限制.总结Performance WarehouseWRITINGPreventing Excessive Split ResultsThis video will help you to understand why excessive splitting occurs, what happens when it occurs, and what you can do to prevent it from happening.Excessive Splitting or a Measure Explosion can cause the Performance Warehouse to fill up and can lead to an unstable state where no writing to the Performance Warehouse is possible anymore.Even a well-designed business transaction can have excessive splitting. For example, Web Requests – URI Pattern Value is a common metric to monitor. When the captured URI contains a Session-ID, this will eventually result in a Measure Explosion because the Session-ID is often passed as a URL parameter or contained somewhere in the URI path.If you haven’t defined a splitting restriction and the Split Results contains a measure such as Session-ID, the business transaction is predisposed for a Measure Explosion.The Measure Explosion Prevention detects possibly misconfigured business transactions and disables creating measures for it. Business transactions with more than 50k split values are automatically disabled.When excessive splitting occurs, no new Charting data is generated for the business transaction, and no new data is generated for existing splitting values. Additionally, no new splitting entries in the Business Transaction Hotspots Dashlet are generated, and existing splitting values are not updated. Lastly, no Incidents based on Result Measures of the business transaction will be triggered.All other diagnostic Dashboards will work without any limitations.If the business transaction is not intended for charting, it can