A 'metric grouping' issue occurs when an agent is sending too many different metrics to DripStat.
Doing so means DripStat needs to store and process unnecessary enormous amount of data and it also reduces the effectiveness of the data in charts due to too high a granularity.
Lets say your application has a URL like the following which returns the user account details:
A URL like this have a different id each time its called, eg:
However, DripStat will usually record this call
as /class name/method name of your controller, eg -
/UserController/userDetails. This way all the above calls will be grouped as one and you will be able to see it as a single transaction in the 'Transactions' tab.
Now lets assume you have a million users.
If we recorded each call individually using the URL instead of the controller method, you will see a million different transactions. Not only will this result in DripStat needing to store and process enormous amounts of data to track each of those million URLs, it will also make it humanly impossible for you to sift through those million different transactions to figure out the performance of your
When can Metric Grouping issues occur
Some scenarios where metric grouping issues can occur is:
- You use the DripStat Agent API to add a custom name to your transactions which results in a unique name each time the url is hit. This basically becomes similar to the example described above.
- Your application crawls the internet, so every call to an 'external service' goes to a different URL. Here the enormous amount of different 'External Services' will create a metric grouping issue.
- Your application dynamically generates temporary database tables on every request. Here the database metrics run into a grouping issue.
Effects of Metric Grouping issues
Metric grouping issue result in highly reduced effectiveness of DripStat charts for you since now there is too much data to humanly look at or understand.
It also results in enormous data storage and processing for DripStat, which can slow down the DripStat service for all users.
Resolving Metric Grouping issues
The DripStat agent tries a lot to prevent metric grouping issues. However in some cases it is unable to do so.
If your application does run into a Metric Grouping Issue, we will temporarily pause accepting data from it.
A DripStat engineer will then contact you. We will then work with you to find a way to fix the issue for you by adding rules in the agent.
Usually the issue is resolved the same day.