This page is for the owner. It lists the steps to create the read-only credentials that the operational-signal adapters (O37.2) will read Sentry, PostHog and Datadog with, one Product at a time. The steps are the registration runbooks of sentry/2, posthog/2 and datadog/1 in src/service-kinds.ts, written out for one Product. Only you carry them out. No agent signs in, accepts terms, pays, creates a key or handles a value.
Nothing reads with these credentials yet. No adapter, recipe or acquisition exists, so a credential you create now sits in its vault until a later, separately reviewed step reads it with your grant. Create one only when that step is near.
Before you start
- One vault per Product. Each credential lives only in the Product's own 1Password vault,
sf-<product>, in an item of its own. None of them goes to GitHub or any CI store: the adapters read through the Factory, not from CI. - Least privilege. Grant only the read permissions listed below. Datadog's unscoped API key can also submit data and must remain vault-only. It is limited to this Product's organisation or project, and you rotate it within 90 days.
- Values stay with you. Paste a value only into its 1Password item, in the 1Password app. Never paste it into a terminal, chat, an agent session or the dashboard.
- Order of tools. Each step uses the first tool in this order that can do it safely: the vendor's agentic CLI, its official API, its classic CLI, then its website. None of the three vendors is known to have an agentic CLI that makes read credentials, and the API and the classic CLI would print a new credential where an agent could read it, so each credential is made on the vendor's website. The vault is made with
op, which prints no secret.
Make the vault (once per Product)
op vault create sf-<product>
Run it in your own terminal, signed in to 1Password. If the vault already exists, skip this. Then tell the coordinator the vault's id, which op vault get sf-<product> --format json prints and which is not a secret, so the Factory can bind the vault to the Product.
Sentry: event-read-token
An internal integration's token belongs to the organisation, not to you, and holds only the permissions you choose. Do not use a personal token, which acts as you, or an organisation auth token, which carries only org:ci for uploads.
- Sign in at
https://sentry.ioand open the Product's organisation. - Go to Settings > Developer Settings > Custom Integrations > Create New Integration > Internal Integration. Name it for the Product's signal reads.
- Set Issue & Event to Read and Project to Read. Read access to the organisation is optional. Leave everything else at No Access, and add no webhooks. Save.
- Under Tokens, create a token and copy it.
- In the 1Password app, in
sf-<product>, create an API Credential titledsentry default event-read-tokenand paste the token into a concealed field namedevent-read-token. - Note today's date: rotate within 90 days.
PostHog: query-read-key
A personal API key acts as the user who made it, so its scopes are the only limit on it.
- Sign in at the PostHog region the Product uses (
https://eu.posthog.comorhttps://us.posthog.com). - Open your account settings, then Personal API keys > Create personal API key. Name it for the Product.
- Limit it to the Product's organisation and project. Under scopes, choose Query: Read; Project: Read and Error tracking: Read are optional. Leave every other scope at No access. Create it and copy the key.
- In the 1Password app, in
sf-<product>, create an API Credential titledposthog default query-read-keyand paste the key into a concealed field namedquery-read-key. - Note today's date: rotate within 90 days.
Datadog: read-app-key and read-api-key
Datadog's read APIs need two keys together. The application key belongs to a service account and holds only read scopes. The API key has no scopes at all and could also send data, so keep this one for reads only.
- Sign in at the Product's Datadog site (for example
https://app.datadoghq.eu). - In the organisation settings, open Service Accounts > New Service Account. Name it for the Product's signal reads and give it only the Datadog Read Only Role.
- In that service account, choose New Key under application keys. Name it for the Product, limit its scopes to
metrics_readandtimeseries_query(and, if logs are wanted,logs_read_data;events_readis optional), create it and copy it. - In the 1Password app, in
sf-<product>, create an API Credential titleddatadog default read-app-keyand paste the key into a concealed field namedread-app-key. - In the organisation settings, open API Keys > New Key. Name it for the Product's signal reads, create it and copy it.
- In the 1Password app, create an API Credential titled
datadog default read-api-keyand paste the key into a concealed field namedread-api-key. - Note today's date: rotate both within 90 days.
What the Factory checks
When the coordinator lists the vault (op item list --vault <id> --format json, the only op command the Factory runs, and you launch it), each item shows as present by its title, version and last-edit date. Fields are never listed, so the Factory knows the item exists, not that its value works. That stays unknown until a reviewed read, with your grant, uses it.
Rotate
- Sign in at the vendor's website.
- Create a replacement with the same permissions: a new token on the Sentry integration, a new PostHog personal API key, or a new Datadog key. The old one keeps working.
- In the 1Password app, replace the field's value in the same item.
- Revoke the old credential at the vendor's website, and tell the coordinator the date.
Not established
- The vendor screens and scope names above follow the vendors' public documentation as understood on 2 October 2026. They were not checked against a live account.
- Whether any vendor CLI could do one of these steps without printing the credential is not established. A reviewed revision would add such a step only after a drill shows it safe.
- The Service access reference has the full contract and its limits.
