Performance Data Collection
  • 25 Nov 2021
  • 1 Minute to read
  • Dark
    Light
  • PDF

Performance Data Collection

  • Dark
    Light
  • PDF

Article Summary

BizTalk360 allows users to enable performance data collection for the various server types, say BizTalk, SQL, IIS, Windows.  The BizTalk360 Analytics service will start collecting performance data for all the counters of the selected type. Users can optimize the performance data collection by using the Manage Metrics option. This allows users to select the required performance metrics for each server. So that the Analytics service will start collecting data for only the selected performance metrics.

In this section, we will take a detailed look at:

  • How to enable the performance data collection at the environment level
  • How to optimize the performance data collection using “Manage Metrics” option at server level 

Enabling Performance Data Collection at Environment level

The performance data collection can be enabled for an environment by navigating to (Environment Settings->Analytics Performance Data Collection).


Click and enable the performance data collection toggle. Once its enabled BizTalk360 Analytics service will start collecting performance data for all the servers under the corresponding environment.

Manage Performance Data Collection

To narrow down the data collection at server level, the user can optimize the performance data collection using the Manage Metrics option for each server under an environment. With this Manage Metrics option, users can choose the required performance metrics for each server, enabling BizTalk360 to start collecting data only for that metrics.

For instance, if you have a multi-server setup - BizTalk Server, SQL Server, IIS configured in different machines, you may expect different performance metrics from different servers. However, you might not want to have SQL-related performance metrics data in the BizTalk server machine. By using the “Manage Metrics” option you can define what metrics are needed for each and every server. This way the Analytics service will start collecting data only for that selected metrics. This avoids huge database growth and improves performance.

Initially, when the performance data collection is enabled, all the counters will be selected. The counters will be updated for selection only after the next polling cycle (15 mins later ).



Was this article helpful?

ESC

Eddy, a super-smart generative AI, opening up ways to have tailored queries and responses