Nik Konyuchenko

@ligeweiwu, The OSS DCGM version does not have the profiling module required for DCP fields (>1000) on GPUs before Hopper. You can still use them with OSS if you copy...

@pintohutch, Currently, we do not have an AppArmor profile for the DCGM service.

Hello, We removed this metric from the default config.csv file some time ago. You can add this metric back on your own. We decided to return this metric to the...

@larivierec, sorry, I didn't get your point. Which metrics could be separated? WBR, Nik

Roughly, the meaning of the SM Occupancy could be described by this documentation: https://docs.nvidia.com/gameworks/content/developertools/desktop/analysis/report/cudaexperiments/kernellevel/achievedoccupancy.htm

@wade-liwei Most likely, you need one of these fields: ```cpp /** * Current Power limit for the device */ #define DCGM_FI_DEV_POWER_MGMT_LIMIT 160 /** * Minimum power management limit for the...

Hi @onstring, There are no such metrics as of today. DCGM does not have fields with such information, but there is an API to collect information about running PIDs. What...

Hi @Shadowphax, Have you tried to run dcgm-exporter with `--devices f` or `--devices i` command line argument? By default, the dcgm-exporter will not monitor MIG instances. You either need to...

@Shadowphax, You are right. In the current implementation, dcgm-exporter does not support multiple types of ranges and more than one range in general. This limitation is on the dcgm-exporter side...

@Shadowphax, Would you please look if `dcgmi discovery -c` would give you the info you need? WBR, Nik