Define a collection extension’s table and view, assign it through role‑based configurations, and schedule and retain its data so endpoints can send structured information to the master database for dashboard use.
Video Transcript
Creating a collection extension is a two‑phase process. First, when you create the extension, it adds a new table to the local agent. On the endpoints, you define the table structure and instruct the agent to create it in its local collection database, which uses a Jet‑style Access database format.
To move that data up to the master level, you need to create a view.
A view is essentially a SQL statement that the endpoint runs against its local collection database. It does not store data permanently. Instead, it extracts the relevant data and sends it to the SysTrack master server, where it creates a corresponding table in the master database. From there, you can access the data through dashboards.
Views can be factory‑provided or custom, and they allow you to selectively collect data from endpoints. Custom views are defined by SQL statements and can be enabled for specific roles rather than globally. You apply the role to a configuration, which lets you control which endpoints execute which views.
Each view runs on a schedule. You define whether it runs daily, weekly, or within specific time windows—such as 12 hours a day, five days a week. Most views typically run once per day. You can also set retention policies, usually around 30 days, to manage how long data is stored and ensure proper purging.
This process is how data from a custom collection extension moves from the endpoint to the master database, where it can be displayed in dashboards.