InfraNestInfraNest
Confluence

Confluence integration

Publish every incident review to Confluence

Your team writes the review in InfraNest: what happened, the impact, why, and what you will change. Finish it with Confluence ticked and the page appears in your Confluence space, under one Incident reviews page so the space stays tidy. It works through the same Atlassian connection as Jira, and you do not need Jira to use it.

Start freeSee pricing

On Pro and up · 14-day Pro trial, no credit card · InfraNest for Jira and Confluence

  • Reviews published to the space you choose
  • Filed under one Incident reviews page
  • The review’s place shown on the incident
  • One Atlassian connection for Jira and Confluence
Confluencenorthwind.atlassian.net

Operations / Incident reviews

2026-09-28 · API latency spike after a deploy (#4)

Published from the team's review in InfraNest. Change the review there: publishing again updates this page.

Open the incident in InfraNest

Summary

  • What failed: API health
  • Impact: Major
  • Started: 2026-09-28 14:54 UTC
  • Resolved: 2026-09-28 15:16 UTC
  • Lasted: 22 minutes
  • Nobody acknowledged it.

What happened

API response times climbed from about 120 ms to over 4 seconds eight minutes after release 2.31 reached production. Sam rolled the release back, and latency was normal again 22 minutes after it started.

Impact

For 22 minutes most API requests took several seconds and about 6% timed out. Checkout and the dashboard were slow but stayed up; no data was lost.

Why it happened

The release included a migration that added an index without a lock timeout. On the primary database it waited behind long-running reads and held its connections open, so the pool ran out and requests queued behind it.

What we change

  • Run schema migrations with a lock timeout, so a slow one fails instead of holding the primary database.
  • Alert when the connection pool on db-01 passes 80%, before latency reaches users.
  • Add a pre-deploy check that flags migrations expected to run longer than a minute.

Write the review once, and Confluence gets the page

The review on a resolved incident is the record. Choose a default space once and every new review has Confluence ticked under Also publish to, so finishing the review publishes the page. You can untick it, or pick another space, on any single review. The page is filled in from the review and from what InfraNest recorded about the incident.

  • What happened, impact, why, and what you will change
  • Every follow-up listed on the page, done or still open
  • Ticked by default once you choose a space, and easy to untick
  • Publishing again updates the same page as a new version
From the review to the page
OnceChoose Operations as the default space
ReviewConfluence already ticked under Also publish to
Finish reviewThe page is published in Operations
Edit the reviewThe same page updated, as a new version

Untick Confluence, or pick another space, on any single review.

Every review under one page, in the space you choose

The first time InfraNest publishes, it creates an Incident reviews page in the space and puts every review under it, so the page tree stays tidy. Prefer a page your team already keeps postmortems under, or the top of the space? Pick it beside the space. If someone deletes or moves the parent page, InfraNest makes it again the next time it publishes, and the review says so.

  • An Incident reviews page created for you, or one you already have
  • Team spaces listed first, then personal ones
  • The parent page made again if it goes missing
  • Pages already published stay in Confluence
Where a review goes
SpaceOperations
Under page“Incident reviews” (we create it)
Page2026-09-28 · API latency spike after a deploy (#4)

Change the review in InfraNest: the page is rewritten from it each time.

The incident shows where its review lives

The incident’s Follow-up panel lists the review with its state, its owner and a chip for each place it is published, Confluence among them. Once the incident is over, it also names what is still open, such as a follow-up issue nobody has finished. A postmortem someone wrote in Confluence can be linked instead: InfraNest shows its title, when it was last edited and whether it is still a draft, and never copies its text.

  • The review’s state and owner, beside its tickets
  • A chip that opens the Confluence page
  • What is still open, named after the incident
  • Write-ups made in Confluence linked, never copied
Follow-up
  • Review4 of 4 parts filled · 3 follow-ups, 1 done
    DonePriya Raghunathan
    2026-09-28 · API latency spike after a deploy (#4)edited last month

One Atlassian connection for Jira and Confluence

Confluence works through your Atlassian connection, the same one Jira uses. Already connected Jira? Allow Confluence once and sign in again; it stays the same connection, and nothing it set up changes. No Jira on your site? Connect Confluence on its own. To publish without opening the review, add Publish the incident review to a rule, such as when an incident resolves.

  • Allow Confluence once on the Jira connection you have
  • Works on a site with Confluence and no Jira
  • Publish the incident review from any rule — see how rules are built
  • No review written yet? The rule starts one from the timeline
Atlassian · northwind.atlassian.net
JiraReady
ConfluenceReady · default space Operations
Incident resolvedPublish the incident review

One sign-in covers both products on the same site.

Publish your next review to Confluence

On Pro and up, with a 14-day trial and no credit card. Connect your Atlassian site and choose a default space.

Start freeRead the setup guide

Connect Confluence through your Atlassian site

Sign in with Atlassian once and approve Jira and Confluence together, or allow Confluence on the Jira connection you already have. Then choose the space your team keeps postmortems in.

  1. 1

    Connect Confluence

    Open Integrations in the sidebar, click Confluence, then Connect Confluence and sign in with Atlassian.

  2. 2

    Allow Confluence if Jira connected first

    If Jira was already connected, click Allow Confluence and sign in once more to reach Confluence from the same connection.

  3. 3

    Choose a default space

    Pick the space your team keeps postmortems in under Default space, so every new review is ready to publish there.

That’s it — Confluence is connected.

Full setup guide

Set up with AI

I use Confluence, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: Sign in with Atlassian, or an API token. Walk me through creating that in Confluence: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.

Open in Claude Open in ChatGPT

Often connected together

CloudflareCloudflareDNS · SSL · Domains · AutomationGitHubGitHubAutomationWebhookWebhookNotifications · Automation

Questions about the Confluence integration

#Do I need Jira to use this?

No. A site that has Confluence and no Jira connects the same way through the Confluence tile, and reviews publish to its spaces exactly as they would alongside Jira.

#What happens if I edit the published page directly in Confluence?

Those changes won't stick. The page is rewritten from the review each time it's published, so the review in InfraNest is the record to edit, not the Confluence page.

#What if the sign-in to Atlassian is revoked or expires?

Publishing will stop and InfraNest will say Confluence needs to be allowed or reconnected again. Pages already published stay in Confluence; nothing is removed.

#Can InfraNest create or move Confluence pages itself?

InfraNest creates the incident review pages it publishes, and an "Incident reviews" parent page the first time it needs one, but it only writes pages tied to reviews - it doesn't manage other Confluence content.

#What do I need before connecting Confluence?

You need an Atlassian account that can sign in to the site (or a Jira API token already connected on that site); see the setup guide.

Write the review once, and let Confluence keep the record

Create your account (it starts with 14 days of Pro), connect your Atlassian site, and choose a default space. Your spaces and pages stay exactly as they are.

Start free

Free plan · No credit card required · Set up in minutes