Integrations catalog
An integration tells your collectors how to collect one kind of data, such as host metrics, a database, a firewall's logs or a cloud account. Integrations come as packages in a catalog that Tracix keeps up to date. Browse the full catalog on the integrations page, and connect integrations in your workspace from Collectors › Integrations.
What a package contains
Every package has a manifest that defines its settings form and the collector configuration it produces. Many also bring:
- Dashboards for the data it collects.
- Log pipelines that parse its logs into fields.
- Workflow actions that Tracix workflows and agents can run against the same system.
The catalog holds three kinds of package:
| Kind | What it is | Where you use it |
|---|---|---|
| Data collection | Collects metrics, logs or traces | Collectors › Integrations, and a policy's Integrations tab |
| Workflow actions | Actions for one vendor's API, such as creating a ticket | The workflow builder's Apps & actions library. These don't appear as tiles. |
| MCP servers | Tools that Tracix Brain can call | Collectors › Integrations, under MCP servers |
New and updated packages reach your workspace without a Tracix or collector release. A few integrations need a recent collector; when the collectors on a policy are too old for one, the connect steps warn that a collector update is required, and older collectors aren't given it until they are upgraded.
Integrations and policies
Every connection is an integration on a collector policy:
- An agentless connection runs on your workspace's cloud gateway, which Tracix runs. Cloud accounts and many API-based integrations can run this way.
- An agent-based connection runs on the collectors of the policy you choose. Anything that listens for data or reads the host, such as syslog, SNMP or log files, runs this way.
Connecting an integration creates a new revision of that policy, which reaches its collectors like any other policy change.
Find an integration
In your workspace, open Collectors › Integrations. The page shows every integration you can connect, grouped by category, with All, Connected and Available filters and a search box that matches names and categories. Each tile says whether it is available or connected, and how many connections it has.
The public integrations page lists every package in the catalog, including the workflow action packs.
Connect an integration
Pick the integration
Select its tile, or select Connect account and pick it under What do you want to connect?
Configure it
Give the connection a Name, unique on its policy. Fill in the settings: required ones first, the rest under Advanced. Credentials are settings of the integration too, such as an API token or a community string.
Choose where it runs
For integrations that can run either way, choose Agentless or Agent-based under Collection. For agent-based ones, pick the policy under Where to add this integration, or select New policy to create one with this integration and your workspace's default output. If you pick none, the integration goes to the
defaultpolicy.Review and connect
Check the summary, with secrets masked, and select Connect. The last step links to where the data will appear.
You need permission to manage integrations to connect, change or delete one.
What connecting installs
- Dashboards from the package are added to your workspace when you connect through Collectors › Integrations. They update when the package does. If you delete one, it isn't added again. Adding the same integration from a policy's Integrations tab doesn't install dashboards.
- Log pipelines from the package apply to the integration's dataset automatically, until you publish your own pipeline for that dataset under Settings › Data Management › Pipelines.
- Monitors aren't part of packages. Tracix's monitor library lists ready-made monitors in Alerts, which you install one by one; see Monitors. The SNMP integration's Enable trap alerts is the exception: it installs the trap monitors when you connect.
Change or remove a connection
Select a connected tile on Collectors › Integrations to open its connections. From there you can edit a connection, disable or enable it, delete it, or add another instance, for example for a second region. You can make the same changes from a policy's Integrations tab with Edit, Disable and Remove.
Saved credentials are write-only
Once saved, a connection's credentials aren't shown again, to anyone. When you edit the connection, a saved secret reads Saved · type to replace, and a saved file reads Saved credential: leave them to keep the stored value, or type a new one. A password inside a URL, such as an output's DSN, is masked the same way. The policy's rendered configuration masks them too.
If you change where a connection with saved credentials points, such as its endpoint, host or URL, Tracix refuses the save and asks you to type the credentials again, so a saved password can't be sent to another server.
Deleting a connection removes it from its policy, so its collectors stop collecting that data with their next revision. Data already collected stays, and so do the dashboards it installed. A policy must keep at least one integration enabled.
Custom integrations
When you have built a log pipeline for logs your collectors read from files, you can reuse it: in the pipeline editor, under Settings › Data Management › Pipelines, select Save as integration. Tracix packages the dataset's source settings and pipeline as your own tile on Collectors › Integrations, which you connect to any policy like a catalog integration. Custom integrations run on your collectors.