Alert-to-runbook-revision metadata packet: the fields a partner can share about Datadog, PagerDuty and Confluence records without opening them

Short answer

A referral partner can collect a short metadata packet: which monitoring, paging and wiki tools hold the alert-to-runbook-revision chain, the years each covers, the object types, a volume band, how each link between tools is made, who owns each system, and what nobody knows yet. Every entry describes the records from the outside. Nothing is copied from inside a notification, a page, a write-up or a procedure, and an operations lead can usually answer the whole form in one conversation.

Visual briefFull-size diagram
A metadata packet fills in field by field (systems, years, volume band, joins, owner, unknowns) while a locked stack of alerts, incidents and runbooks beside it stays closed.
Illustrative packet. Every field describes the records from the outside; the raw alerts, incidents and runbooks are never opened.

This packet belongs to the alert-to-runbook-revision records guide, which explains how the links work. This page is the form itself. Once it is filled, the completeness checklist helps you judge whether the answers describe a trail worth discussing.

The packet rule: describe the container, not the contents

Every field answers one of five questions: what, how much, how long, which system, who owns it. If an answer would require someone to open an item and read it, the field does not belong on the form.

Allowed on the formKept off the form
"Monitoring tool in use since 2020"Check names, queries or thresholds
"Thousands of paging events a year"Event titles, notes or responder names
"Write-ups carry a reference number since 2021"Any write-up text or stated cause
"Procedure edits usually have a comment"Procedure steps, commands or host names
"Notes may mention customers: unknown"Which customers, or any customer data

The right-hand column is not a list of things to handle carefully. It lists things a partner never requests. The Confluence inventory template applies the same line to a single wiki.

Packet fields, block by block

Fill in one block per tool, then one block for the links between them. The third column says where the sponsor usually finds each answer without opening anything.

BlockFieldWhere the answer comes fromUsually confirmed by
MonitoringTool and years in use, earlier tools if anyAdmin settings, contract datesReliability lead
MonitoringObject types retained: checks, trigger and recovery eventsProduct configurationReliability lead
PagingTool and years in use; event history retained?Account settings, retention policyOn-call manager
PagingVolume band per yearAccount reporting dashboardsOn-call manager
WikiSpace for procedures and write-ups; first yearSpace settings, oldest page datePlatform manager
WikiVolume band of procedures and write-upsSpace page countsPlatform manager
LinksMonitoring check to paging eventIntegration configurationReliability lead
LinksPaging event to write-upWrite-up template fieldsPlatform manager
LinksWrite-up to procedure editTeam habit on edit commentsPlatform manager
LinksDoes a recovery close the paging event automatically?Notification templatesReliability lead
GapsWhat is unknown, and who could find outThe sponsor's own judgmentNamed per item

Two fields carry most of the value. The years tell SourceX how deep the history runs; the joins tell it whether those years form one connected story or three separate piles. The PagerDuty incident export page covers what that tool's own records contain.

A filled packet (Illustrative)

A fictional 300-person payments software company, answered by its SRE lead and platform engineering manager in one call. Every value is Illustrative.

Packet fieldEntryOwner who can confirm
MonitoringDatadog since 2020; an earlier tool for 2017 to 2019SRE lead
PagingPagerDuty since 2018; incident log entries retainedOn-call manager
KnowledgeConfluence runbooks and postmortems since 2017Platform engineering manager
Volume bandThousands of incidents; a few hundred postmortems; about 150 runbook pagesSRE lead
Monitoring-to-paging linkPaging handle on most production monitorsSRE lead
Paging-to-write-up linkIncident number field in the postmortem template since 2021Platform engineering manager
Write-up-to-procedure linkVersion comments on runbook edits: inconsistentUnknown until reviewed
Recovery behaviorRecovery messages include the paging handleSRE lead
Monitoring migrationNo mapping kept between old and new monitorsSRE lead
UnknownWhether incident notes include customer dataGeneral counsel

Read the packet the way a reviewer would. Alerts and incidents are joined by design from 2020. Incidents and postmortems are joined by a template field only from 2021. The procedure link depends on habit and is uneven. The 2017 to 2019 alert history exists but sits in a tool with no mapping to the current one. That is an honest, specific description of nearly a decade of operating history, and it took no record access to write.

Fields that change how the packet is read

Three entries look minor and are not.

Recovery behavior. Datadog's PagerDuty integration resolves the linked incident automatically when a monitor recovers, if the paging handle is in the recovery message. Datadog builds that message with conditional variables such as {{#is_recovery}}, so the sponsor can answer from the message templates without opening an alert. If recoveries auto-resolve, some incidents will have closed while the fault was still present, and the real cause sits only in postmortems. The missing context page shows what that looks like in a single export.

Incident log retention. PagerDuty keeps a log of what happened to each incident: integration event data, notifications, who acknowledged or resolved it, automatic actions, reassignments and notes. Whether that log is still held for older years decides whether response steps can be reconstructed, so ask for the earliest year it covers.

Version comments. Confluence page history lists each version's date, author and comment. A comment that cites a postmortem or an incident number is the only thing that ties a runbook change to its cause. "Usually", "sometimes" and "rarely" are all useful answers; so is "since the template changed in 2022". The checklist for document revision histories covers version records in more depth.

Write each answer at the confidence the sponsor gave it. "Unknown until reviewed" is a complete entry, provided it names who could find out.

Who answers the packet, and what it does not decide

The SRE lead, on-call manager and platform engineering manager answer the fields. None of them can authorize a licensing discussion: that is the CEO, usually with the CTO and general counsel involved, because incident notes and runbooks can mention customers, vendors and security controls. Context on why operational records like these matter to AI developers is in the AI agents in ITSM guide.

Before the packet goes anywhere, confirm the company baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license, 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.

The packet does not decide whether the company's rights cover the records, what must be removed for security, whether a buyer wants this kind of history, or what the company would be paid. SourceX settles those under the company's own agreement. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. It does not claim a connector for Datadog, PagerDuty or Confluence, and a partner should not promise one. Sign the Channel Partner Agreement before you submit an introduction; attribution goes to the first valid introduction within the 90-day window.

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 the SRE lead can fill in this packet and an officer will take the first call, register as a partner, check the company against who qualifies, and read the terms before you send it.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can I paste a sample alert or runbook into the packet to show what the records look like?

No. A sample is content, and content is exactly what the packet keeps out. Describe the object type and the join instead, for example 'runbook pages with version comments since 2021', and let the company decide later, under an agreement, what anyone sees.

What if the sponsor only knows rough numbers?

Rough is right. Volume bands such as hundreds, thousands or tens of thousands are what the packet asks for. Exact counts would require someone to query the records, which is the company's job after an agreement, not the partner's before an introduction.

Who should hold the finished packet?

The sponsor who answered it and you. Share it with SourceX only when the company agrees to an introduction, and keep it free of host names, customer names, credentials and anything copied from an incident.

Sources

  1. docs.datadoghq.com/integrations/pagerduty
  2. docs.datadoghq.com/monitors/notify/variables
  3. developer.pagerduty.com/docs/88922dc5e1ad1-overview-v2-webhooks
  4. support.atlassian.com/confluence-cloud/docs/create-edit-and-publis…
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment