If you have been using ITCAM for Microsoft Applications and recently decided to upgrade to v6.3.0 for monitoring your .NET and IIS infrastructure, you must be wondering what is this new '.NET Data Collector' (code: K4) in addition to '.NET Framework Agent' (code: QF) that is there in the installer package!
Please go through my earlier post for a brief introduction of .NET Data Collector before we proceed to differentiate it from .NET Framework Agent.
|.NET Framework Agent (QF)||.NET Data Collector (K4)|
|It is an agent||It is a Data Collector|
|It can be managed from TEMS configuration panel||It can only be managed from the configDC utility|
|It has TEMS and TEPS support and can be seen from the TEP||It does not have its own UI, it sends events to the Transaction Collector agent of ITCAM for Transactions bundle. You have to see the .NET transactions from Transaction Reporter agent UI on TEP.|
|It can monitor |
- Various Event Log entries related to .NET Framework
- Various performance counters
- Availability of core processes
|It can monitor the transactions occurring in the applications targeting .NET Framework.|
|The .NET Framework agent itself can only be installed on Windows, however the TEPS and TEMS support can be seeded in TEPS/TEMS servers deployed on Non-Windows platforms.||The .NET Data Collector can only be installed on Windows. Since it does not have its own TEPS/TEMS support, there is no question of Non-Windows platform. Deploying the Collector and Reporter agents from ITCAM for Transactions bundle is a different story altogether.|
|The agent has its own EXE which is registered as Windows Service||The .NET Data Collector is a set of DLLs and the only EXEs offered are for configuration purposes.|