Data Sources Page
The Data Sources page lists every agent, integration and direct sender that feeds events into UTMStack v12, and shows whether each one is still sending. Use it to spot sources that went quiet, label and rate your assets, open a live console on an agent, and export a report.
Go to Configure > Data Sources. The page has no title or subtitle. Its header shows how many sources match the current tab and search ("N total"), and the Export PDF and Connect a source buttons.
This screenshot is from UTMStack v12.0.0; v12.0.2 also shows an Export PDF button next to Connect a source.
What the page shows
| Area | What it shows |
|---|---|
| Ingestion | A chart of events received over a time range you choose (the last 24 hours by default). |
| Data sources | How many data sources are configured. |
| Health summary | How many sources are online and offline, and the total. |
| Tabs | All, Agents, Integrations, Direct, Offline, each with a count. |
| Toolbar | Search by name…, List or Cards view, and Refresh. |
| Header buttons | Export PDF and Connect a source (opens the Integrations page). |
In the list view the columns are Source, Type, Status, Events 24h and Last seen. The list loads 50 sources at a time. Click a label on any source to show only the sources with that label; clear the filter from the "Filtered by label" chip.
Kinds of data source
| Kind | Tab | How it gets on the list | Name | How "last seen" is updated |
|---|---|---|---|---|
| Agent | Agents | When a Windows, Linux or macOS agent registers. | The host name | Every 60 seconds, from the agent's last contact with the server |
| Integration | Integrations | When you save a config group for a cloud integration. | The config group name | Every 10 minutes, from the count of events received for that config group |
| Direct | Direct | When UTMStack counts events from a new sender, for example a firewall sending through the UTMStack Forwarder. | The sender's IP address (or the Forwarder host name for local senders, github for GitHub webhooks) | Every 10 minutes, from the count of events received from that sender |
A row is identified by its name and its data type. So:
A firewall that sends two data types appears twice, once per data type.
Two devices with the same IP address and the same data type (for example two sites using the same private addresses) appear as one row.
A host keeps its row, labels and asset sensitivity when its agent is reinstalled, as long as its host name does not change.
Status
| Status | Meaning |
|---|---|
| Live | Last seen less than 15 minutes ago. |
| Idle | Last seen between 15 minutes and 24 hours ago. |
| Offline | Last seen more than 24 hours ago, or never. |
The Offline tab lists every source that is Offline, including sources that were never seen. The status is worked out in your browser from Last seen each time the page loads, so click Refresh to update it.
What to expect after you connect a source
| Source | When it appears | When it turns Live |
|---|---|---|
| Agent | About a minute after the install | At once |
| Device through the Forwarder | Up to about 20 minutes after its first logs | When it appears |
| Cloud integration | As soon as you save the config group | Up to about 20 minutes after the first events arrive. Until then it shows Offline. |
A source that sends rarely (for example a device that logs only on changes) can be Idle most of the time. That is normal; look at its Events 24h and its ingestion trend.
Source details
Click a source to open its details. The top shows the source's type, kind and data type, its name, IP address and status, and the View logs button.
The Metadata values in the screenshot are demo data; each source shows only the details it reports.
Stats & identity: Events 24h, Last seen, Discovered, Kind, and Data type and IP when the source has them.
Metadata: extra details reported by the source, when there are any (for agents: operating system, version, addresses and whether remote commands are disabled).
Ingestion trend: a small chart of recent events. Gaps show when the source stopped sending. When a source is offline, a warning shows "Last event … — possible log gap".
View logs: opens Log Explorer for this source over the last 7 days.
Labels: type a label and press Enter to add it. Changes save automatically.
Asset sensitivity: rate the business importance of this asset for Confidentiality, Integrity and Availability (None, Low, Medium or High), then click Save. Alerts that target this host or IP are weighted by these values.
Console (agents only): see below.
Danger zone: Delete data source, then Confirm delete.
Deleting a data source removes it from this list only. Its historical events stay searchable in Log Explorer. If the source keeps sending data, or its agent is still registered, it is discovered again and comes back on the list.
Run commands on an agent (console)
For agents, the details include a Console section: "Run commands on this host through its agent (live response)."
- 1
Open the console
Click Open console. On Windows hosts, choose cmd or powershell. Other systems use bash.
- 2
Authenticate
UTMStack asks you to authenticate before the first command runs.
- 3
Run a command
Type a command and press Enter. The output streams back into the console.
Variables lets you store values and reference them in commands. Mark a variable as Secret (encrypted, masked in output) for passwords and keys.
The console is turned off when the agent is Offline (not seen for more than 24 hours).
An agent installed with remote command execution disabled refuses every command. See Agent Command Line.
Running commands needs the
soar.writepermission. The same commands are available from SOAR > Interactive Console.
Export a report
Click Export PDF. UTMStack builds the "UTMStack — Data Sources Report" with event totals, the number of agents, integrations and direct sources, the volume received and the full list. Click Print / Save as PDF and use your browser's print dialog to save it.
A routine health check
Once a day or once a week:
Open the Offline tab. For each source, decide whether it was retired (delete it) or has a problem (investigate).
Sort or scan Events 24h in the All tab for sources whose volume dropped sharply compared with what you usually see.
Open Configure > Data Processing and check Dropped (parsing) by data type. A rise means a source changed its log format. See Data Processing.
Compare the Agents tab with your inventory of computers, to find machines without an agent.
For problems you find, see Checking and Troubleshooting Data Collection.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| A new device does not appear | Its logs have not been counted yet (up to about 20 minutes), or they do not reach UTMStack. | Wait 20 minutes, then check View logs on its card. See Forwarder Troubleshooting. |
| A new cloud integration shows Offline | No events have been counted for its config group yet. | Check View logs on its card. Some services deliver their first events only after a delay; see the integration's page. |
| An uninstalled agent stays on the list | Uninstalling removes the agent, not its row. The row turns Idle, then Offline. | Delete the row. |
| A deleted source comes back | It still sends data, or its agent registration still exists. | Stop the source or uninstall its agent first, then delete it. |
| Two devices share one row | They reach the Forwarder with the same IP address and send the same data type. | All their events are stored; only the row is shared. Tell them apart in Log Explorer with a field such as origin.host or the raw text. |
| A deleted cloud config group still has a row | Deleting a config group stops collection but leaves its row, which turns Offline. | Delete the row. |
Permissions
| Action | Permission needed |
|---|---|
| View the page and source details | datasources.read |
| Change labels or asset sensitivity, delete a source | datasources.write |
| Run console commands on an agent | soar.write |