Usage tracking and assessing the performance

QUESTION:
We want to capture usage stats on page hits within Changepoint at the URL level. Currently, we have IIS logging disabled as recommended by Changepoint for performance reasons Do you have any recommendations to capture these stats? Another option we have available is third party applications which tags each page with javascript. We want to keep performance impact to a minimum as well.

ANSWER:
-IIS logging is considerably low impact on a healthy web servers with enough disk space. It’s a built-in IIS functionality, therefore there isn’t much overhead. However, as with anything, it can be impactful if web servers are already constraint with high CPU utilization and bad Disk I/O (large disk queue length). As with many things, it’s not simple black and white. Customer should examine the web server performance and make the decision.

- As for the third-party tool, Javascript injection on pages are typically part of UEM (user experience monitoring), while it is useful for tracing end-user experience, it can be very heavy on the infrastructure and can lead to slower performance. It’s much more impactful than simple IIS logging. Only thing that UEM tool provides that IIS log does not is an ability to interpret the results. IIS log is a simple text file and someone technical has to review it.