====== NIOS Reporting Server ======
A good reason to have a reporting server is DHCP lease history. This enables you to show the different MAC addresses that have all been issued a given IP address.

Remember that syslog forwarding of query/response logs can have a major impact on performance.

  * 1,000 DNS QPS amounts to 25GB of data per day.  
  * An average DNS query byte size of 290 bytes (ish)
===== Management =====
If MGMT port is enabled on a node, then the node will use that port to communicate with the reporting server (if there is one)
===== Migration =====
If you are running two reporting servers on hardware (or VM's that can't be moved) configured in a single-site cluster  and you need to replace hardware, it is possible to [[https://support.infoblox.com/s/article/8603|upgrade while retaining historical data]].


You can backup just reporting and re-import.
  - If you need a full backup, then Infoblox support [[https://support.infoblox.com/s/article/Full-Reporting-Backup|has a hot fix]] to force the full backup.
  - It takes a fair amount of time to do this.  If it takes 4 hours to backup the import will take at least the same.  

===== Dangling CNAME Report =====
[[https://community.infoblox.com/t5/reporting/dangling-cname-report/td-p/22398|Dangling CNAME Report]]

===== Licence=====
  * 1GB
  * 2GB
  * 5GB
  * 10GB
  * 20GB
  * 50GB
  * 100GB
  * 200GB
  * 500GB

=====  Reporing Usage =====
You can use this search to review the usage and generate a predictive model of their future usage: 
<code>index=_internal source=*license_usage.log* type=Usage
| eval GB_used = b/1024/1024/1024
| timechart span=1d sum(GB_used) AS GB_used
| predict GB_used AS GB_forecast future_timespan=90 holdback=0</code>