Manual Chapter :
What resources do I need to collect ASM data
Applies To:
Show Versions
BIG-IQ Centralized Management
- 5.4.0
Use this table to estimate the number of DCDs necessary to collect and display ASM event data from BIG-IP devices.
- If you are using an off-box logging solution to log ASM events, review a week’s worth of alert logs to identify the logging load you need to support. Take note of both the average and maximum alerts per second.
- If you are logging ASM events locally on the BIG-IP device, you can also use those logs to identify your peak event logging rates. Compare the peak rates against the alerts per second (Alerts/Sec column) to estimate the number of DCDs you need.
- If you have not yet deployed an ASM solution in your environment, but you have an estimate of your application’s peak HTTP/HTTPS traffic requirements, you can estimate your logging needs by projecting that 10% of your peak traffic could generate logging events. You can then use that value to estimate the number of DCDs you need.
| Alerts/Sec | Data Redundancy | Recommended DCD count |
|---|---|---|
| 10000 | No | 1 |
| 14000 | Yes | 2 |
| 17000 | Yes | 3 |
| 20000 | Yes | 4 |
| 23000 | Yes | 5 |
| 26000 | Yes | 6 |
Note:
- The sizing recommendations in this table assume that you provision your DCDs with 8 cores/CPUs and 32 GB of memory.
- When you choose an alert rate, consider both the average and peak loads that you anticipate. If your peak loads are frequent, consider provisioning additional data-collection nodes for the increased load. Also, when you determine your peak rates, plan for growth by considering the rate at which you expect your traffic load to increase.
