Log-to-Process Mapping for SystemEDGE is not working

book

Article ID: 103035

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

Log Monitor alarm is asserted on the systemEDGE host model instead of on the ProcMonSysEDGE model. 

CA Spectrum is not generating the event on the process model that a parsed log file entry refers. It is being generated on the host model. 



User-added image

First was enabled the option of creating the SystemEDGE Process Models by adding the following entry in the $SPECROOT/SS/.vnmrc file: 

"enable_sysedge_process_modeling_support=true" 


This is covered in this CA Spectrum guide: 

https://docops.ca.com/ca-spectrum/10-2-3/en/managing-network/host-system-resources-management/process-monitoring/differentiating-processes 

-Creation of SystemEDGE Process Models 


Then mapped the monitored log file to a monitored process. 


This is covered in this CA Spectrum guide: 

https://docops.ca.com/ca-spectrum/10-2-3/en/managing-network/host-system-resources-management/log-file-monitoring/log-to-process-mapping 

- Log-to-Process Mapping 

- Specify a Mapping for RFC 2790 Agents and SystemEDGE Hosts 

Cause

The Process Name (calc) configured in the "Monitored Process Log File Mappings" subview do not match with Model_Name (0x1006e) attribute value of ProcMonSysEDGE application model.



Environment

CA Spectrum 10.2.x and CA SystemEDGE 5.9

Resolution

The workaround is changing the Model_Name (0x1006e) attribute value from "Monitor Calculator process" to "calc" to match with the Monitored Process Log File Mappings setting.





Another workaround is changing the Process Name value from "calc" to "Monitor Calculator process" to match with Process Monitor Description field.





Note: Use the UNIX path in the Log File Name field


Attachments