infoblox_nios:reporting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| infoblox_nios:reporting [2024/04/02 09:43] – [NIOS Reporting Server] bstafford | infoblox_nios:reporting [2026/03/19 22:53] (current) – [Licence] bstafford | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * 1,000 DNS QPS amounts to 25GB of data per day. | * 1,000 DNS QPS amounts to 25GB of data per day. | ||
| * An average DNS query byte size of 290 bytes (ish) | * 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 | ||
| + | |||
| + | |||
| + | You can backup just reporting and re-import. | ||
| + | - If you need a full backup, then Infoblox support [[https:// | ||
| + | - 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:// | ||
| ===== Licence===== | ===== Licence===== | ||
| Line 17: | Line 29: | ||
| * 200GB | * 200GB | ||
| * 500GB | * 500GB | ||
| + | |||
| + | ===== Reporing Usage ===== | ||
| + | You can use this search to review the usage and generate a predictive model of their future usage: | ||
| + | < | ||
| + | | eval GB_used = b/ | ||
| + | | timechart span=1d sum(GB_used) AS GB_used | ||
| + | | predict GB_used AS GB_forecast future_timespan=90 holdback=0</ | ||
infoblox_nios/reporting.1712050981.txt.gz · Last modified: by bstafford
