SQL Agent Logs

SQL agent logs mostly host critical log data. With OpManager Nexus AppLogs you can drill this data down to find out vital errors. The appropriate segregation of log information into relevant fields like date & time, user, log level, event ID, and Message gives more clarity on the log data.   Learn more about log management with OpManager Nexus.

Getting started

1. Log in to your OpManager Nexus account.
2. Download and install the OpManager Nexus Server Monitoring agent (Windows). 
3. Go to Admin > AppLogs > Log Profile and Add Log Profile.

Logs file path

Each application writes logs in different folders and files. By default, SQL agent logs are sourced from the below-mentioned folder path for the respective Operating System. If you have logs in a different folder, you can mention it under the File Path to source them from that particular folder while creating a log profile.

:

C:\Program Files\Microsoft SQL Server\*.MSSQLSERVER\MSSQL\Log\SQLAGENT*

Log pattern

$DateTime:date$ $User$ $LogLevel$ [$EventId$] $Message$

This is the default pattern defined by OpManager Nexus for parsing SQL agent logs based on the sample log mentioned below.

Sample log

2017-07-31 22:22:58 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent

The above sample log can be separated into 5 fields, each of which will take its respective value from here and will then be uploaded to OpManager Nexus.

Field name	Field value
Date Time	2017-07-31 22:22:58
User	-
Log Level	-
Event ID	364
Message	The Messenger service has not been started - NetSend notifications will not be sent

Related log types

• Windows event logs
• Other supported log types