Troubleshooting the configuration for IMF

Last published : Oct 13, 2026
If you face problems with the IMF configuration or functionality, consider the following:
  • Ensure that the following attributes are configured with appropriate values.
    • AgentFile
    • IMF
  • If you have configured the required attributes to enable the Microsoft SQL Server agent for IMF, but the agent is still not IMF-enabled, restart the agent. The imf_init function runs only when the agent starts up, so when you restart the agent, imf_init runs and initializes the Microsoft SQL Server agent to interface with the AMF kernel driver.
  • You can run the following command to check the value of the MonitorMethod attribute and to verify that a resource is registered for IMF.
# hares -value resource MonitorMethod system
The MonitorMethod attribute specifies the monitoring method that the agent uses to monitor the resource:
  • Traditional - Poll-based resource monitoring
  • IMF - Intelligent resource monitoring
  • You can use the amfstat to see a list of registered PIDs for a MSSQL resource.
A sample output of the ps -ef command for the MSSQL processes is as follows:
$ ps -ef | grep mssql
mssql    2442548       1  0 Sep11 ?    00:00:00 /opt/mssql/bin/sqlservr
mssql    2442551 2442548  0 Sep11 ?    00:28:00 /opt/mssql/bin/sqlservr
The amfstat command shows the PIDs monitored by the agent.
Registered Reapers (1):
=======================
 RID    PID     EVENT   REAPER
 1      568     2       0       MSSQL

Process ONLINE Monitors (3):
============================
 RID    R_RID   PID        GROUP
 22     1       2442548    mssql
 23     1       2442551    mssql
  • Run the following command to view the content of the AMF in-memory trace buffer.
# amfconfig -p dbglog