Which processes are included in SQL Server CPU metrics, how CPU is collected, default intervals for offline/online/realtime, and steps to adjust them. (4309812)

On the Foglight database page for a SQL Server instance, under CPU utilization, you see two graph lines:

• One labeled SQL Server
• One labeled Total

What Windows processes are included in the "SQL Server" CPU graph, and which are included in "Total" CPU?
Would the CPU usage for **databasemail90.exe** appear under "SQL Server" or "Total" CPU? 

• Total CPU reflects the overall operating system CPU usage, including all processes running on the Windows host. This is collected using the WMI class `Win32_PerfRawData_PerfOS_Processor` for all host processors.
• SQL Server CPU tracks only the main SQL Server executable process (typically `sqlservr.exe`). Foglight identifies this process by running:
    SELECT SERVERPROPERTY('ProcessID') AS process_id
    
    The process ID is then used to query WMI:
    SELECT Name, VirtualBytes, PercentProcessorTime, TimeStamp_Sys100NS 
    FROM Win32_PerfRawData_PerfProc_Process 
    WHERE IdProcess = {SQL Server PID}
• databasemail90.exe is an external utility for sending mail from SQL Server. Although it interacts with SQL Server, it runs as a separate Windows process.
• Collection interval: for the SQL Server Host Group (DBSS_SQL_Server_host) is set by mode:
  • Offline: 300 seconds (5 minutes)
  • Online: 60 seconds (1 minute)
  • Realtime: 20 seconds

1. "SQL Server" CPU graph:  

• Only includes CPU usage for the main SQL Server process (`sqlservr.exe`) associated with your database instance.
• Does **not** include external SQL-related processes.

2. "Total" CPU graph:

• Includes CPU usage for all Windows processes running on the host, including `sqlservr.exe`, `databasemail90.exe`, SSIS, backup agents, antivirus, and others.

3.. databasemail90.exe: 

• The CPU usage for `databasemail90.exe` appears only in "Total" CPU.
• It is not counted in the "SQL Server" CPU graph, since it is a separate process from `sqlservr.exe`.
• This separation remains valid for SQL Server 2005-2022 and likely future versions.
• The main SQL Server process is tracked by its PID; external tools/utilities are grouped under "Total" CPU.

4. How often does Foglight gather CPU data?  

• Offline mode: every 300 seconds (5 minutes)
• Online mode: every 60 seconds (1 minute)
• Realtime mode: every 20 seconds

5. Where can you change the collection interval?  

• In the Foglight console, go to Databases → SQL Server.
• Select your monitored agent or host.
• Open Agent Properties or Monitoring Settings.
• Find the Collection Interval for the SQL Server Host Group (DBSS_SQL_Server_host).
• You can adjust intervals for offline, online, and realtime modes as needed.
• Save and deploy your changes.
• Note: Lower intervals increase data granularity but may impact performance, monitor resource usage after changes.

6. Troubleshooting and best practices:

• Ensure Foglight agents are healthy and running.
• Align Foglight’s interval with other monitoring tools for better comparison.
• Check agent logs for missed polls or errors.
• Monitor performance after changing interval settings.