- 25 Nov 2021
- 2 Minutes to read
- Print
- DarkLight
- PDF
Event Logs
- Updated on 25 Nov 2021
- 2 Minutes to read
- Print
- DarkLight
- PDF
In addition to monitoring Disks, NT Services, etc., BizTalk360 offers monitoring of Event Logs and configure rules based on your requirements. Event Logs are logs that record specific events that happen within the environment. The event logs are normally used to inform about important events in the running applications and subsystems such as Errors, Warnings, or Information messages. The event log information can be used by administrators for troubleshooting problems. In this section, we will see how to set up monitoring of Event Viewer in the SQL server using BizTalk360.
Monitoring the Event Viewer in SQL Server
In BizTalk360, the administrator can configure alerts for a particular event log/source(s) by defining a filter condition on the available event logs and request to be notified, when there are more than a specific number of alerts/warnings from the server. For instance, you can customize the alert in such a way that you must be notified when there has been a sequence of start/stops of the host instances in the past 30 minutes. Without being alerted, you may not know the frequent start/stops of the host instances and this could impact the performance of the environment or be a sign of other problems in the environment.
The administrators can set up monitoring for the event log by defining their filter conditions on the event logs available in the server. Filter conditions can be defined in the following event log fields:
- Event Log name
- Event Sources
- Event Id
- Event Log Description
In addition, the administrators can also monitor the event logs by entering the event id of a particular event or by providing an error string to look for in the event log descriptions field. Once the event log information is selected, the threshold violation settings can be entered. This is where you define the amount of found event log entries that match the created criteria for each type (Error, Warning, and Information) and the time span to be analyzed during each run of the monitoring service. If you want to ignore a certain type of event log entry from monitoring, you can specify a really large number for the threshold, this is a common approach used when excluding information alerts from monitoring.
Setting up monitoring for Event Logs
- Log in to the BizTalk360 application
- Click 'Monitoring' in the navigation panel
- Click the expand button against the 'Manage Mapping' tab and depending on the requirement, select the 'SQL Servers' link
- Select the SQL Server for which you want to set up the monitoring of Event Log Entries
- Select the Alarm name (see Manage Alarms) from the drop-down for which you would like to associate the alerts
- At the tab pages at the top, select 'Event Logs'
- Click the 'New Event Log Alert' button to set up monitoring for the event logs. You can customize your alert on a specific event log/source
- In the configuration blade, you can set up notifications when there are more than a specific number of alerts/warnings
- Click 'Save' to save the Event log alert information
The SQL Server BT360DOC needs to be monitored for certain Event Log entries. Alerts should be received in case, within a time frame of 45 minutes, more than 15 Errors or 20 Warnings or 25 Information events were received from Event Log Sources Application and the Event Log entry Id is 30010, in the Applications log.