Activities: scan and analysis status in AQG↑
Activities gives you a single place to see whether scans and backend analysis are actually progressing or stuck. When a code scan, a filesystem scan, or cloud ingestion runs, Activities shows who triggered it, which data source it came from, and whether data import and analysis have finished, so you can quickly answer “is the system doing work?” and “where is it stuck?” without digging through logs or CI pipelines.
What’s new↑
New Activities page for scan and analysis status↑
A dedicated Activities view shows one row per execution (for example, a code scan or a filesystem scan), with timestamps, the data source, and the current state.
End-to-end visibility: data import and data analysis↑
Each activity tracks both:
- Data import status — whether AQtive Guard has successfully received data from the source.
- Data analysis status — whether AQtive Guard analysis has completed on those events.
This makes it easy to distinguish “the source never sent data” from “AQtive Guard is still processing,” which was previously invisible.
Multi-sensor coverage from day one↑
Initial scope covers:
- Filesystem scans
- Static code scans
- Cloud ingestion activities
- Cryptographic bill of materials (CBOM) imports
Additional sensors and integrations are being added, and the Activities tab will continue to scale as new data sources are introduced.
UI polish for easier troubleshooting↑
- Data source filter — lets you focus on specific activity types, for example only code scanning or filesystem activities.
- Default sort by most recent activity — surfaces the latest runs and any stuck jobs at the top.
- 90-day activity window — keeps the view performant and focused on recent behavior.