Questions about forcing and recalculation of rollups when managing CAMM and SNMP data for the same device in DX NetOps Performance Management.
We know that the rollups would not be calculated if the "high-watermark" for the Metric Family & CAMM data was past the timestamp of the data added to the database.
In the environment that raises these questions, we see that rollups get calculated even if the data is a few hours "late".
Data is imported using a custom CAMM pack into the Interface Metric Family. This Metric Family is also getting data from SNMP devices so the high-watermark should always be current.
The CAMM data tied to the same Metric Family is typically at least 2 hours behind but could be delayed more due to the various components involved.
Is there a way to know what delay is allowed?
For example, are hourly rollups always calculated X hours after their timestamp?
Are daily rollups calculated at a specific time of the day?
Need to ensure methods are known to recalculate rollups when required.
All supported DX NetOps Performance Management releases
What happens here will depend on where the metrics are gathered and managed.
SNMP and CAMM on different Data Collectors is the only way this can work.
How does the reconciliation/isolation work between SNMP vs CAMM items in the following scenarios?
What about the same question for these scenarios?
Both sets of scenarios result in the same answers:
Note that when it comes to rollups:
Only issue is #1 when the SNMP/CAMM are on same IP Domain and DC.
If working with an environment configured like this, ensure the data consumers understand that if there is a gap in the middle of data because a system was unavailable, it is possible to go back via the CAMM pack to get the missing raw data.
Calculating the rollup is another complexity. It would work if all data after a specific timestamp was dropped, the high-watermark for the MF was cleared and the CAMM pack was run to re-import the data sequentially.
Keep in mind this also means deleting the rows in ifstats_ltd/eqd/gtd/rate for the CAMM item_ids to reload data to for tstamp >= beginning of the data gap.