Viewing Admin Probes
This page describes the metrics within the Admin Portal Probes.
Use Case
Lets give a situation where an admin user is experiencing latency or problems in communication regarding the IIS and they want to verify and validate if the systems are operating properly.
Viewing the Admin Portal Service Metrics
🚧To view the Admin Portal Service Metrics, please follow the steps below:
Go to the System → Probes page.
Select Local Service from the Show Probes From dropdown.
Wait for the metrics to load.
You should see a view similar to below
Local Service Breakdown
.NET Thread Pool
Breakdown of .Net Thread Pool Metrics
This section of the probes describes the current characteristics of the .NET thread pool. Since the technology used is vastly of the .NET framework, the Admin Portal can provide metrics pertaining to threads that are in use. In other words, processes on the Admin Portal which may still be performed that could be still in use, stuck, or just not being released after being used.
🛠️The .NET Pool metric (on the left) defines background workers that are busy
📝The .NET I/O Threads metric (on the right) describes threads that are performing reading and writing operations within the IIS.
💼In the case of the above image, the system is not doing very much and is mostly at idle.
📝This is a characteristic for a machine that is not seeing much activity.
🖥️On a machine that was being used more frequently, this number would fluctuate and depend on:
🔨the how the system was implemented,
👥how many people were using the system, and
👀how much activity the system was seeing.
Thread Pool
Breakdown of the Thread Pool Metrics
This section of the probes describes the primary SanteDB thread pool performance monitor.
These metrics illustrate characteristics such as:
🔢How many threads are available to do work?
🧵How many threads of the thread pool are currently busy doing operations?
⌛How many operations are waiting to be performed by the thread pool?
💼In the case of the above image, the system is not doing very much and is mostly at idle.
📝This is a characteristic for a machine that is not seeing much activity.
🖥️On a machine that was being used more frequently, this number would fluctuate and depend on: - 🔨the how the system was implemented, - 👥how many people were using the system, and - 👀how much activity the system was seeing.
Memory Cache Services
Breakdown of Memory Cache Service Metrics
This section of the probes describes statistics about registered memory caching services.
These metrics illustrate characteristics such as:
🫙How many objects of data are being cached for re-use by other services, devices, and clients?
🗒️How many objects of Ad-Hoc data are being cached for re-use by other services, devices, and clients?
This pertains to reporting data.
👤How many objects related to user sessions are being cached for re-use
This pertains to logged in sessions.
🔍How many objects related to Queries of data that are being cached for re-use?
This pertains to lookups and other data queries.
🔃This is useful when accessing and validating if the infrastructure is adequate for the load demanded by the users and other services of the system.
HTTP Workers
Breakdown of HTTP Worker Metrics
This section of the probes describes the servers ability to process HTTP requests.
These metrics illustrate characteristics such as:
🧵How many threads are allocated to processing HTTP requests?
🛠️How many threads that are working already to process HTTP requests?
⌛How many HTTP requests are queued and waiting to be executed?
🗣️This is useful in accessing and validating if devices are communicating actively and appropriately... or if the system seems to be halted with communicating with other devices
Last updated