ddi.infoblox

Introduction

The tags beginning with ddi.infoblox identify events generated by Infoblox.

Valid tags and data tables

The full tag must have 4 levels. The first two are fixed as ddi.infoblox. The third level identifies the type of events sent, and the fourth level indicates the event subtype.

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

Product / Service	Tags	Data tables
Infoblox solutions	`ddi.infoblox.audit.httpd` `ddi.infoblox.dns.dtc` `ddi.infoblox.audit.serial_console` `ddi.infoblox.dns.config` `ddi.infoblox.dns.resolver` `ddi.infoblox.dns.database` `ddi.infoblox.dns.queries` `ddi.infoblox.dns.infoblox-responses` `ddi.infoblox.dns.query-errors` `ddi.infoblox.unknown.unknown`	`ddi.infoblox`
	`ddi.infoblox.audit.httpd` `ddi.infoblox.audit.serial_console` `ddi.infoblox.audit.sshd`	`ddi.infoblox.audit`
	`ddi.infoblox.audit.httpd`	`ddi.infoblox.audit.httpd`
	`ddi.infoblox.audit.serial_console`	`ddi.infoblox.audit.serial_console`
	`ddi.infoblox.audit.sshd`	`ddi.infoblox.audit.sshd`
	`ddi.infoblox.dhcp.validate_dhcpd`	`ddi.infoblox.dhcp`
	`ddi.infoblox.dhcp.dhcpd`	`ddi.infoblox.dhcp.dhcpd`
	`ddi.infoblox.dhcp.validate_dhcpd`	`ddi.infoblox.dhcp.validate_dhcpd`
	`ddi.infoblox.dns.dtc` `ddi.infoblox.dns.config` `ddi.infoblox.dns.database` `ddi.infoblox.dns.resolver` `ddi.infoblox.dns.query-errors` `ddi.infoblox.dns.queries` `ddi.infoblox.dns.infoblox-responses`	`ddi.infoblox.dns`
	`ddi.infoblox.dns.client`	`ddi.infoblox.dns.client`
	`ddi.infoblox.dns.config`	`ddi.infoblox.dns.config`
	`ddi.infoblox.dns.database`	`ddi.infoblox.dns.database`
	`ddi.infoblox.dns.dtc`	`ddi.infoblox.dns.dtc`
	`ddi.infoblox.dns.general`	`ddi.infoblox.dns.general`
	`ddi.infoblox.dns.infoblox-responses`	`ddi.infoblox.dns.infobloxResponses`
	`ddi.infoblox.dns.lame-servers`	`ddi.infoblox.dns.lameServers`
	`ddi.infoblox.dns.network`	`ddi.infoblox.dns.network`
	`ddi.infoblox.dns.notify`	`ddi.infoblox.dns.notify`
	`ddi.infoblox.dns.queries`	`ddi.infoblox.dns.queries`
	`ddi.infoblox.dns.queries_responses`	`ddi.infoblox.dns.queries_responses` Union table This is a union table that collects events from a set of tables for easy access and analysis. Learn more about this union table in this article.
	`ddi.infoblox.dns.queryErrors`	`ddi.infoblox.dns.queryErrors`
	`ddi.infoblox.dns.rateLimit`	`ddi.infoblox.dns.rateLimit`
	`ddi.infoblox.dns.resolver`	`ddi.infoblox.dns.resolver`
	`ddi.infoblox.dns.rpz`	`ddi.infoblox.dns.rpz`
	`ddi.infoblox.dns.security`	`ddi.infoblox.dns.security`
	`ddi.infoblox.dns.unknown`	`ddi.infoblox.dns.unknown`
	`ddi.infoblox.dns.update`	`ddi.infoblox.dns.update`
	`ddi.infoblox.dns.updateSecurity`	`ddi.infoblox.dns.updateSecurity`
	`ddi.infoblox.dns.xferIn`	`ddi.infoblox.dns.xferIn`
	`ddi.infoblox.dns.xferOut`	`ddi.infoblox.dns.xferOut`
	`ddi.infoblox.nios`	`ddi.infoblox.nios`
	`ddi.infoblox.nios.monitor`	`ddi.infoblox.nios.monitor`
	`ddi.infoblox.nios.ntpd`	`ddi.infoblox.nios.ntpd`
	`ddi.infoblox.nios.ntpdate`	`ddi.infoblox.nios.ntpdate`
	`ddi.infoblox.nios.rabbitmq_control`	`ddi.infoblox.nios.rabbitmq_control`
	`ddi.infoblox.nios.syslog-ng`	`ddi.infoblox.nios.syslog-ng`
	`ddi.infoblox.unknown.unknown`	`ddi.infoblox.unknown.unknown`

How is the data sent to Devo?

Set up the Devo relay rules

You will need to set up a rule on the relay to correctly process and forward the events received from Infoblox. In the example below, you should use any port that you can dedicate to these events.

Infoblox - DNS Categories

Infoblox classifies the DNS logs in different categories. You can know more about this in their documentation: Setting DNS Logging Categories. The table below depicts which Devo Relay rule would process each DNS Logging Category.

Infoblox DNS Logging Categories	Relay rule names
Infoblox DNS Logging Categories	DDI Infoblox - DNS Categories	DDI Infoblox - DNS Category DTC 1	DDI Infoblox - DNS Category DTC 2	DDI Infoblox - unknown DNS Categories
general	✓
client	✓
config	✓
database	✓
dnssec				✓
lame servers	✓
network	✓
notify	✓
queries	✓
rate-limit	✓
resolver	✓
responses	✓
rpz	✓
security	✓
transfer-in	✓
transfer-out	✓
update	✓
update-security	✓
DTC load balancing			✓
DTC health monitors		✓

Rules

DDI Infoblox - DNS Categories

Source Port → Customer source port, for example 13004
Source data → ^.*named\[\d*\]:\s+([\S]+):
Target Tag → ddi.infoblox.dns.\\d1
Sent without syslog tag → True
Is Prefix → False (by default)
Stop processing → True

DDI Infoblox - DNS Category DTC 2

Source Port → Customer source port, for example 13004
Source data → ^named\[\d*\]:\s+request\s
Target Tag → ddi.infoblox.dns.dtc
Sent without syslog tag → True
Is Prefix →False (by default)
Stop processing → True

DDI Infoblox - unknown DNS Categories

Source Port → Customer source port, for example 13004
Source data → ^(?:import_)?named\[\d*\]
Target Tag → ddi.infoblox.dns.unknown
Sent without syslog tag → True
Is Prefix → False (by default)
Stop processing → True

DDI Infoblox - DNS Category DTC 1

Source Port → Customer source port, for example 13004
Source data → ^idns_health
Target Tag → ddi.infoblox.dns.dtc
Sent without syslog tag → True
Is Prefix → False (by default)
Stop processing → True

Infoblox - DHCP

Rules

DDI Infoblox - DHCP

Source Port → Customer source port, for example 13004
Source data → ^.*(validate_dhcpd|dhcpd)
Target Tag → ddi.infoblox.dhcp.\\d1
Sent without syslog tag → True
Is Prefix → False (by default)
Stop processing → True

Infoblox - NIOS

Rules

DDI Infoblox - NIOS

Source Port → Customer source port, for example 13004
Source data → ^(ntpdate|monitor|ntpd|rabbitmq_control|syslog-ng)
Target Tag → ddi.infoblox.nios.\\d1
Sent without syslog tag → True
Is Prefix → False (by default)
Stop processing → True

Infoblox - Audit

Rules

DDI Infoblox - AUDIT

Source Port → Customer source port, for example 13004
Source data → ^.*(serial_console|httpd|sshd)
Target Tag → ddi.infoblox.audit.\\d1
Sent without syslog tag → True
Is Prefix → False (by default)
Stop processing → True

Infoblox - unknown

Rules

DDI Infoblox - unknown

Source Port → Customer source port, for example 13004
Target Tag → ddi.infoblox.unknown.unknown
Sent without syslog tag → True
Is Prefix → False (by default)
Stop processing → True

Configure Infoblox NIOS to send logs to the Relay

Before starting the configuration, please read the Infoblox documentation.

Setting DNS Logging Categories

Infoblox DNS logs have different categories. You can select which categories you would like to send into Devo by following these steps:

Select Data Management tab
Select the DNS tab
Click Grid DNS Properties from the Toolbar
Enable de Advanced Mode by clicking on “Toggle Expert Mode” if the editor is in the basic mode.
Select the Logging tab
Select the Logging Categories you would like to send to Devo.
Save & Close

Enabling some logging categories can increase disk space usage and adversely affect DNS services and performance. Check with Infoblox whether you are recommended to logging some of these categories.

After saving the changes, you may be prompted to restart the DNS service for the changes to take effect.

Specifying Syslog Servers

Follow the next steps to configure your Infoblox to send messages to the Devo Relay:

Select the Grid tab
Select the Grid Manager tab
Select the Members tab
Click Grid Properties from the Toolbar.
In the Grid Properties editor, select the Monitoring tab. You will see a window like this below.
Select “Log to External Syslog Servers” to enable the Infoblox appliance to send messages to a specified Syslog server.
Select also the “Copy Audit Log Message to Syslog” so you will be able to send audit logs to Devo.
To define a new Devo Relay, click the Add icon and complete the following fields:
- Address: Devo Relay IP address
- Transport: Secure TCP, TCP or UDP. If selecting Secure TCP, you will need to configure Stunnel in front of the Devo Relay so Stunnel will decrypt the logs and send them decrypted to the Devo Relay. Here you can read more about integrating Stunnel with the Devo Relay.
- Interface: at your convenience.
- Node ID: at your convenience.
- Source: at your convenience.
- Severity: at your convenience.
- Port: Devo Relay port or Stunnel port listening for logs. If using the Infoblox option Transport TCP or UDP you must use the Source port of the relay rules you configured previously. If you selected Secure TCP, then you must enter the Stunnel listening port.
- Logging category: you must select the option “Send selected categories” and then move to the “Selected” space all the categories you want to send to Devo. The reason for selecting the option “Send selected categories” instead of the option “Send all” is that logs will be prefixed and the Devo parsing will only work for prefixed logs of Infoblox. Read more about Infoblox log prefixes here.
- Then click on the Add button and you will see the configured Devo Relay as part of the list of Syslog Servers.
- Save & Close

After saving the changes, you may be required to do a service restart for the changes to take effect. Your Infoblox appliance will start to send Syslog to your Devo Relay.

Table structure

These are the fields displayed in these tables: