# Change collision system map: ITSM to monitoring | SourceX

Canonical: https://refer.sourcex.si/guides/change-collision-recovery-records-across-systems
Last updated: 2026-11-04

Five keys rebuild a clash between two approved changes: the change number, which ties each change to its approval, its conflict result and later its rollback; the CI ID, which ties a change to the components it depends on; the service name, which ties those components to what monitoring watches; the alert ID, which ties monitoring to the incident; and the incident number, which ties the response to the correlated change and the review. ServiceNow holds the change and configuration side, monitoring and on-call tools hold the response side, and the review often sits in a wiki. Break any one key and the case becomes unrelated tickets.

This system map is part of the [change collision recovery guide](/guides/workflow-change-collision-recovery). It answers a single question for an ITSM implementation partner: across the systems a company uses, which identifier joins which record, who owns each system, and what does one fully joined case look like?

## The system map: who holds what, and the key between them

| System | Record it holds | Linking key out | Typical owner |
|---|---|---|---|
| Change management (ServiceNow) | Change request, approvals, planned window, conflict results | Change number; affected CI | Change manager |
| CMDB (ServiceNow) | CIs and the relationships between them | CI ID; relationship record | Configuration manager |
| Monitoring | Alert, threshold, start and clear times | Alert ID; service name | Platform or SRE lead |
| On-call (PagerDuty) | Incident, responders, change events and correlations | Incident number; change event reference | Service delivery director |
| Review wiki or problem record | Post-incident review, actions, configuration fix | Links to incident and change numbers | Problem manager |

Each owner sees one slice. The change manager sees approvals but not the alert. The on-call lead sees the incident timing but not the CAB notes. Nobody holds the case; it exists only where the keys line up.

## The links, and what breaks each one

| Link | Key | What usually breaks it |
|---|---|---|
| Change to CI | Affected CI field on the change | Work logged against a broad service, not a CI |
| Change to conflict result | Change number | Results shown on screen but never stored |
| CI to dependency | CMDB relationship record | Relationships added later, with no history |
| Change to on-call | Change event created by an integration | Integration never switched on |
| Alert to incident | Alert ID copied onto the incident | Incidents opened by hand without the alert |
| Incident to change | Correlation shown on the incident | No change events, or no service dependencies configured |
| Rollback to change | Change number on the back-out task | Rollback done under the original record with no note |
| Review to all | Incident and change numbers cited | Reviews that describe "the Tuesday outage" in prose |

Two keys are created by tools rather than people: the change event and the correlation. The other six depend on habits, such as copying an alert ID or citing a ticket number, which is why their quality varies by team and by year.

## Chronology: the join that needs no key

Keys say which records belong together. Timestamps say what came first, and this kind of failure is defined by timing: two windows overlapping, an alert inside both, a rollback before recovery.

Three things often damage chronology:

- **CMDB relationships without history.** If a dependency was added after the incident, the current configuration data suggests it always existed. Only relationship history shows otherwise.
- **Migrated tickets.** Consolidations can reset created dates to the import date, so a change looks approved after it ran.
- **Separate clocks.** Monitoring, on-call and ITSM may log in different time zones. Record which.

The [ServiceNow archiving and retention guide](/guides/servicenow-data-archiving-retention-policy) explains why closed records and their history may already sit in archive tables, which affects whether chronology survives.

## What the vendor documentation says about these links

Three documented behaviors explain why some links exist at all. ServiceNow's conflict detection needs a configuration item and planned start and end dates, and lists the conflicting change, the CI and the issue type; a check built on CIs cannot flag a dependency the CMDB does not hold. PagerDuty's ServiceNow integration can create change events when a change request opens, and those events never page anyone; they appear as context. On an incident, PagerDuty shows up to three changes correlated from the past 24 hours with a reason, and related-service matches depend on configured service dependencies. If dependencies were not configured, correlation fell back to time, which can be right by coincidence, so note which reason past incidents show.

## One fully joined case (Illustrative)

Illustrative. A fictional 900-person managed services provider. On a Tuesday evening a firewall rule update (CHG-1) and a certificate rotation on the API gateway (CHG-2) each passed review, ran in overlapping windows and together cut off a partner API. All numbers are invented.

| Order | System | Record | Key that joins it |
|---|---|---|---|
| 1 | Change management | CHG-1 approved, 21:00 to 23:00 | Change number; CI: edge firewall |
| 2 | Change management | CHG-2 standard change from 21:30 | Change number; CI: API gateway |
| 3 | Change management | Conflict results for both: none | Change numbers |
| 4 | On-call | Change events for CHG-1 and CHG-2 | Created by the ITSM integration |
| 5 | Monitoring | Alert at 21:52: partner API handshake failures | Alert ID; service: partner API |
| 6 | On-call | Incident at 21:55; CHG-1 and CHG-2 both correlated by time | Incident number; alert ID |
| 7 | Change management | Emergency rollback of CHG-1 approved at 22:10 | Change number of CHG-1 |
| 8 | On-call | Incident resolved at 22:25 | Incident number |
| 9 | Review wiki | Review cites the incident and both changes | Incident and change numbers |
| 10 | CMDB | Partner API now linked to the firewall and the gateway; relationship dated after the incident | CI IDs; relationship date |

Every row holds because a key was present. Remove row 4 and row 6 loses its correlation. Remove the citations in row 9 and the review floats free. Row 6 also shows a limit: with two changes correlated by time, the record alone does not say which was the cause, so the rollback note in row 7 carries the reasoning. A different collision, told step by step with who decided what, is in the [worked collision case](/guides/change-collision-recovery-exception-examples).

## A quick test of whether a client's joins are intact

Ask the service delivery director about one past clash:

1. Can the team show the stored conflict result that said "no conflict"?
2. Does the incident show the change that was later rolled back, and with what correlation reason?
3. Was the rollback approved on its own record, citing the change number?
4. Does the review cite both the incident and the change numbers?
5. Can the configuration data show when the missing link was added?

Yes to most means the joins are probably intact. Note the answers as metadata, never as exports. For each system in more depth, see [ServiceNow incident data](/systems/servicenow-incident-data-for-ai-training), [PagerDuty incident exports](/systems/pagerduty-export-incidents) and [ITSM ticket history](/data-types/itsm-ticket-history). Carry the key facts into the [referral brief template](/resources/change-collision-recovery-referral-brief-template).

## Qualification and the open questions

The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Until SourceX reviews it, nobody knows whether buyers want this joined history, how customer contracts affect records about hosted services, or whether an offer follows.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client can join a past clash from conflict result to the configuration fix, [register as a partner](/register), check the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce its service delivery director.

## Sources

- https://docs.servicenow.com/bundle/paris-it-service-management/page/product/change-management/task/t_RunManualConflictDetection.html
- https://support.pagerduty.com/docs/change-events
- https://support.pagerduty.com/main/docs/servicenow-change-requests-integration-guide
- https://refer.sourcex.si/terms
