What are Blueprint Analytics

Managed devices generate large amounts of data over time. On their own these data are voluminous and unhelpful. With Intent-Based Analytics (IBA) you can combine intent from the graph with current and historic data from devices to reason about the network at-large.

Data generated by devices are ingested via agents and sent to the Apstra server. With the use of probes, data can be aggregated across devices in response to operator configuration. Combining probes with intent from the blueprint graph generates a reduced set of data that can be more easily reasoned about. You can directly inspect advanced data from the Apstra GUI or from REST API to gain real-time insight about the network. It can also be streamed out with our existing streaming infrastructure. Also, based on the state of this advanced data, anomalies can be raised.

While operating IBA at scale, using many probes, disk usage can grow significantly within the Apstra server VM. This is expected because the system will persist at least enough samples to maintain data for the requested duration for all time-series for all existing probes. Additionally, the system will create checkpoint (backup) files up to a configured limit. Settings in the /etc/aos/aos.conf file indicate how often to rotate logs and remove old checkpoint files. Using IBA can increase disk usage to tens of gigabytes. If this is an issue, you can adjust the log rotation settings to reduce disk usage.

Additional space may be used by system snapshots and old images from any in-place Apstra server upgrades. These can be deleted or moved off the system to increase free disk space.

Agents ingest data that devices generate and send them to the Apstra server. With IBA probes, you can aggregate data across devices based on how they are configured. Combining probes with intent from the blueprint graph generates a reduced set of data. You can directly inspect advanced data from the Apstra GUI or from REST API to gain real-time insight about the network. You can stream data out with our existing streaming infrastructure. Also, based on the state of this advanced data, probes can raise anomalies.

While operating IBA at scale, using many probes, disk usage can grow significantly within the Apstra server VM. This is expected because the system will persist at least enough samples to maintain data for the requested duration for all time-series for all existing probes. Additionally, the system will create checkpoint (backup) files up to a configured limit. Settings in the /etc/aos/aos.conf file indicate how often to rotate logs and remove old checkpoint files. Using IBA can increase disk usage to tens of gigabytes. If this is an issue, you can adjust the log rotation settings to reduce disk usage.

System snapshots and old images from in-place Apstra server upgrades may use additional space. You can delete them or move them off the system to increase free disk space.