Table of Contents | ||||
---|---|---|---|---|
|
...
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.
Technology | Brand | Type | Subtype |
---|---|---|---|
ddi | infoblox |
|
|
|
| ||
|
| ||
|
|
...
Tag | Data table |
---|---|
ddi.infoblox.audit.serialconsole | ddi.infoblox.audit.serialconsole |
ddi.infoblox.audit.sshd | ddi.infoblox.audit.sshd |
ddi.infoblox.audit.httpd | ddi.infoblox.audit.httpd |
ddi.infoblox.dhcp.dhcpd | ddi.infoblox.dhcp.dhcpd |
ddi.infoblox.dhcp.validate_dhcpd | ddi.infoblox.dhcp.validate_dhcpd |
ddi.infoblox.dns.general | ddi.infoblox.dns.general |
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.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.rate-limit | ddi.infoblox.dns.rateLimit |
ddi.infoblox.dns.resolver | ddi.infoblox.dns.resolver |
ddi.infoblox.dns.infoblox-responses | ddi.infoblox.dns.infobloxResponses |
ddi.infoblox.dns.rpz | ddi.infoblox.dns.rpz |
ddi.infoblox.dns.security | ddi.infoblox.dns.security |
ddi.infoblox.dns.xfer-in | ddi.infoblox.dns.xferIn |
ddi.infoblox.dns.xfer-out | ddi.infoblox.dns.xferOut |
ddi.infoblox.dns.unknown | ddi.infoblox.dns.unknown |
ddi.infoblox.dns.update | ddi.infoblox.dns.update |
ddi.infoblox.dns.update-security | ddi.infoblox.dns.updateSecurity |
ddi.infoblox.nios.ntpd | ddi.infoblox.nios.ntpd |
ddi.infoblox.nios.ntpdate | ddi.infoblox.nios.ntpdate |
ddi.infoblox.nios.monitor | ddi.infoblox.nios.monitor |
ddi.infoblox.nios.syslog-ng | ddi.infoblox.nios.syslogNg |
ddi.infoblox.nios.rabbitmq_control | ddi.infoblox.nios.rabbitmq_control |
ddi.infoblox.unknown.unknown | ddi.infoblox.unknown.unknown |
How is the data sent to Devo?
Set up the Devo relay rules
...
Infoblox DNS Logging Categories | Relay rule names | |||
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 | Relay screenshot |
---|---|
DDI Infoblox - DNS Categories
| |
DDI Infoblox - DNS Category DTC 2
| |
DDI Infoblox - unknown DNS Categories
| |
DDI Infoblox - DNS Category DTC 1
|
...
Rules | Relay screenshot |
---|---|
DDI Infoblox - DHCP
|
...
Rules | Relay screenshot |
---|---|
DDI Infoblox - AUDIT
|
...
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
Note |
---|
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.
...
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.
...