db.mssql
- Former user (Deleted)
- Laszlo Frazer
- Juan Tomás Alonso Nieto (Deactivated)
- Former user (Deleted)
Introduction
Devo recommends sending Microsoft SQL Server data using Snare. Snare sends to db.mssql_snare, which is preferred to db.mssql.
The tags beginning with db.mssql identify events generated by Microsoft SQL Server.
Valid tags and data tables
The full tag must have at least three levels. The first two are fixed as db.mssql. The third level identifies the type of events sent. The fourth, fifth, and sixth levels identity the corresponding environment, application, and clone.
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service | Tags | Data tables |
|---|---|---|
Microsoft SQL Server |
|
|
|
| |
|
|
For more information, read more about Devo tags.
How is the data sent to Devo?
Devo recommends using Snare.
If the relay is used, these examples can be followed:
Source message:
Source data:
Source tag:
Target tag: db.mssql.audit
Sent without syslog tag: true
Source message:
Source data:
Source tag:
Target tag: db.mssql.error.env.app.clon
Sent without syslog tag: true
Source message:
Source data:
Source tag:
Target tag: db.mssql.events.env.app.clon
Sent without syslog tag: true
In the rules, if you have multiple environments, applications, or clones of databases, then the env, app, and clon should be customized.
Data can also be sent with NXLog.