Domain mappings and impact
Domain mappings label parts of an API with product areas (billing, identity, …). Then Intello can tag changes with affected_domain so alert rules and triage match who owns that surface.
In the app
- Open a dependency that already has at least one successful sync.
- Find Domains / Domain mappings (tab or section name may vary).
- Add domains that match how your teams talk (keep the list small).
- Map paths, tags, or operations to those domains using the UI controls.
- Use Refresh when the vendor adds operations and you want rules re-evaluated.
Then in alert preferences, you can scope rules to a domain so e.g. only billing breakages page on-call.
Why bother?
- Routing: payments team gets payments changes.
- Noise control: ignore domains you don’t integrate with.
- Reporting: see concentration of risk by product area.
Edge cases
| Scenario | Guidance |
|---|---|
| Vendor renames paths | Update mappings or use broader patterns if the UI supports them. |
| Unmapped operations | Changes may have no affected_domain; broader alert rules still apply. |
Developers: HTTP API
GET/POST/PUT/DELETE /api/dependencies/:id/domains and POST .../domains/refresh mirror the UI. See Core resources.