dns.bluecat

[ 1 Valid tags and data tables ] [ 2 Send it ] [ 3 Table structure ]

The tags beginning with dns.bluecat identify events generated by the BlueCat Domain Name System (DNS).

Valid tags and data tables

This tag must have three levels. The first two are fixed as dns.bluecat. The third level identifies the type of events sent.

These are the valid tags and corresponding data tables that will receive the parsers' data:

Product / Service	Tags	Data tables

Product / Service	Tags	Data tables
BlueCat DNS	`dns.bluecat.named`	`dns.bluecat.named`
	`dns.bluecat.stats`	`dns.bluecat.stats`
	`dns.bluecat.stats.authquery`	`dns.bluecat.stats.authquery`
	`dns.bluecat.stats.authresponse`	`dns.bluecat.stats.authresponse`
	`dns.bluecat.stats.clientquery`	`dns.bluecat.stats.clientquery`
	`dns.bluecat.stats.clientresponse`	`dns.bluecat.stats.clientresponse`
	`dns.bluecat.stats.resolverquery`	`dns.bluecat.stats.resolverquery`
	`dns.bluecat.stats.resolverresponse`	`dns.bluecat.stats.resolverresponse`
	`dns.bluecat.stats.updatequery`	`dns.bluecat.stats.updatequery`
	`dns.bluecat.stats.updateresponse`	`dns.bluecat.stats.updateresponse`

For more information, read more About Devo tags.

Send it

Data should be sent using the relay.

Example relay rules

         Source message: 
            Source data: 
             Source tag: 
             Target tag: dns.bluecat.named
Sent without syslog tag: false
        Stop processing: true

Another option to forward logs generated by BlueCat is by using any Syslog drain (for example, Syslog-ng). Learn more about how to send BlueCat logs and their structure here.

Table structure

These are the fields displayed in these tables: