Integrations (one list)
Admin → Integrations gathers every link Spitfire has to other systems on one page: you see, test, edit and delete them here. The addresses of the old list pages (Notification channels, Data sources, Connections, APM) open the matching group on this page.
One list
| Group | What is in it | Adding steps |
|---|---|---|
| Connections | Database, Kafka, MQTT, Redis, gRPC… connections the tests use | Protocols and connections |
| APM | OpenTelemetry, Prometheus, Tempo, Jaeger, Loki, Zabbix, Datadog and the like; infrastructure data sources | APM |
| Notification channels | Slack, Teams, e-mail, SMS, webhook | Notification channels |
| Issue tracking | Jira-like channels that open issues | Notification channels |
| Cloud and Kubernetes | AWS, Azure, GCP, IBM Cloud, vCenter and Kubernetes data sources | On this page In Spitfire: /admin/integrations#cloud |
You see a group only if your role can see that area; data sources are for the installation admin only.
Statuses
- Working (green): the last check or delivery succeeded.
- Slow (yellow): it answers, but late.
- Error (red): the last check failed; the error shows under the row.
- Not tested (grey): not tested yet, or no data has come in.
- Off (grey): the link is disabled.
The summary line at the top counts the total and those failing or slow. If a health-checked link goes down a warning shows at the top; click a name in it and the page scrolls to that row.
Cards and table
The Cards | Table switch at the top right changes the view, and this browser remembers it. In Cards each link's left edge has its status colour; in Table groups fold, a column heading sorts, and the toolbar filters and searches. With no integrations yet only the kind picker shows.
Test, edit and delete
If you may edit, each row has Test (the result and new status show under the row), Edit (pencil; for data sources the source's dashboard) and Delete (bin, asks first). A connection that tests use cannot be deleted; the dialog lists those tests.
Rows carry extra details by kind:
- Connections: description, the Production mark, SSH tunnel, the names of stored secrets (never their values), last change. On a SQL connection the installation admin opens Suggest from schema with the light bulb icon (SQL schema suggestions). A failed PostgreSQL test names the step it stopped at and its guide heading.
- APM: the last characters of the receiver's and browser key's token, allowed origins, last data, how many tests it feeds. New token (key icon) renews a receiver's token; the old one stops working at once. Monitoring event connections outside your license carry the not read (license) badge. Add a service at the top right sets up an application's telemetry step by step.
- Data sources: Last data, why the last test failed if it did, who reads the source (the Spitfire server, a Tower, the Collector in the cluster or the Windows agent on the IIS server) and the health badge. The line above the list shows the license quota (Infrastructure sources, Cloud accounts / clusters: used / allowed).
- Notification and issue-tracking channels: events sent, last delivery, Deliveries (clock icon), and buttons to send the weekly summary and monthly SLA report now.
Adding an integration
- Click + Add integration.
- Find the kind in the picker's groups, or search with the box at the top.
- Click the kind; its own add form opens. Data sources open on the Add a source page and go to their dashboard after saving. A log source in the APM · Log collectors group opens its Collector setup window (Log collection).
- Save the form. Check: the row's Test button in the list gives Working.
Kinds your license does not include show a lock; the orange i under the picker says which plans they come with, and Add to licence opens the purchase page.
Settings
The Settings section below the list gathers the cards that apply to every integration (for those who can see notification channels):
- Notification channels: the schema and signature of what channels send (orange i), Sample payload, the issue-tracking module's license and 7-day trial.
- General (install admin): Spitfire's public address and the notification language.
- E-mail (SMTP) (install admin): the server for channels, reports and password resets; try it with Send a test e-mail.
- Send Spitfire metrics out (OTLP) (install admin): forwards live metrics to an OpenTelemetry collector.
- Expose Spitfire metrics to Prometheus: the scrape address and a ready
scrape_configs.