How to reduce the amount of "dependency telemetry" RRS feed

  • Question

  • Our service makes several thousands of DB requests. By the end of the year this rate may increase in 5 times. We really like to use dependency tracking. But because of the huge traffic of dependencies we will be forced to abandon it. Is there a possibility of aggregation  a dependency telemetry on client side ?Maybe there is a possibility for set of some restrictions on this kind of telemetry? For example, to limit the number of data points (only for dependecy telemetry) within a unit of time?
    Thursday, February 2, 2017 10:31 PM


  • Hello Igor,

    I would recommend to filter out fast dependencies before they are sent from AI SDK to AI Backend.

    You can use Telemetry Processors to do that. With this approach you will be in control of which dependencies are of interest to you (with duration slower than a threshold and/or with some certain property) and which are not. Sampling is also a good approach to collect less data but still have a good statistical representation. You can set some aggressive sampling values to lower the amount of the data sent.

    Dmitry Matveev

    Thursday, February 2, 2017 11:15 PM