Confluence Cloud

MuleSoft architecture docs in Confluence with MuleSight™

When architecture documentation lags behind deployments, give reviewers Anypoint context beside the design decisions. Embed refreshable Exchange, Runtime Manager, and API Manager snapshots, compare environments, and review security posture without leaving Confluence.

MuleSight™ by Flowdence™

Snapshot Macros

Put Anypoint snapshots beside your architecture decisions

Add the source link, choose a macro display, and publish the page. Use detailed cards for design docs, compact views for status pages, and refresh actions when freshness matters.

Exchange

Embed Exchange asset metadata - type, publish status, version, and last updated.

  • Asset name
  • Type
  • Publish status
  • Version
  • Last updated
Runtime Manager

Embed deployment snapshots - application status, version, target, and public endpoint.

  • Deployment name
  • App status
  • Artifact version
  • Target name/type
  • Public endpoint
API Manager

Pin API instances - status, version, security summary, and Exchange mapping.

  • API name
  • Status
  • Version
  • Security summary
  • API Instance ID
Powered by Atlassian Rovo

MuleSight Specialist Rovo Agent

Ask about app statuses, API policies, and cached Exchange endpoint methods and paths in Confluence. MuleSight Rovo actions need the current space context; refresh the relevant data when freshness matters.

  • Space-scoped answers

    Actions return a context-required response when the space context is missing

  • Cache-based endpoint context

    Seed missing endpoint data by opening an Exchange Endpoints macro and refreshing

  • On-demand refresh

    Can refresh datasets and API security data when you ask for it

Built on Atlassian Rovo

AI agent for Confluence space-context questions

MuleSight SpecialistRovo Agent
Live
Ask about your MuleSoft environment...

Features

MuleSoft context for architecture and operations teams

Link-to-Snapshot Macros

Turn Exchange, Runtime Manager, and API Manager links into refreshable snapshot cards beside your architecture narrative and runbooks.

Snapshot macros guide

Global Landing Page

Centralized dashboard with environment health, recent drift events, and shortcuts to every MuleSight surface in your space.

Landing page tour

Environment Comparison

Compare API Manager and CloudHub resources across selected environments. Review differences in presence, version, and status, then export CSV or HTML.

Comparison dashboard

API Security Posture

Scan API protection posture per environment. View policies, SLA tiers, contracts, and security drift across your API landscape.

API Security Posture guide

Diagnostics

Probe MuleSoft endpoints, surface 403 and timeout failures per dataset, and check OAuth scope coverage to debug snapshot failures fast.

Diagnostics reference

MuleSight Rovo Agent

Ask your Rovo AI agent about MuleSoft state directly in Confluence — drift, policies, deployments, and more, grounded in MuleSight data.

Rovo agent guide

Ops Dashboard

Review scheduled sync state, last sync, drift signature state, incident watchers, and published Ops pages in Confluence.

Ops Dashboard guide

Secure Connected App Model

Uses MuleSoft Connected App client credentials. Secrets stored with Forge encrypted storage. Egress limited to anypoint.mulesoft.com.

Configuration guide

Upcoming Modules

MuleSight roadmap — preview the next dashboards, integrations, and AI experiences arriving for MuleSoft teams in Confluence.

Roadmap preview

What is Drift?

In MuleSight, drift means the same logical resource differs across selected environments by presence (deployed vs not deployed), version (artifact version), or status (e.g., RUNNING vs STOPPED).

Security drift is intentionally non-noisy: it compares only enabled policies by template identity, ignores disabled policies and version differences, and treats contract counts as informational only.

Presence

Deployed in one env, missing in another

Version

Different artifact versions across envs

Status

RUNNING vs STOPPED, ACTIVE vs INACTIVE

Is MuleSight right for your architecture docs?

What belongs on a MuleSoft architecture page?

Keep your design rationale in Confluence and add Exchange asset, Runtime Manager application, and API Manager instance cards as supporting context. For architecture reviews and operational handoffs, combine detailed snapshots with an Environment Summary. API consumers can use the Exchange Endpoints display for cached methods and paths. MuleSight supplies context, not an automatically written architecture document.

Choose a snapshot macro and display mode

How do teams review deployment differences?

Select the organization, environments, and API Manager or CloudHub dataset in Environment Comparison. Filter to drifted resources to inspect presence, version, and status differences, then export the filtered CSV or HTML for release review. These are cached snapshots: refresh before relying on them for a time-sensitive decision.

Review drift filters and export steps

Does security posture mean enforcement?

No. MuleSight provides read-only visibility into MuleSoft policies, SLA tiers, contracts, and environment differences. It does not enforce API policies or change deployments. Use the posture view to discuss gaps with platform and security owners; remediation remains in your MuleSoft operational process.

Inspect API security posture and evidence exports

What is needed before snapshots can load?

Configure a MuleSoft Connected App client ID, client secret, and organization ID for the Confluence space. Review the required OAuth scopes, test the saved connection, and validate dashboard data. Dataset toggles and the sync interval control what is collected and how often; diagnostics help investigate missing access or failed refreshes.

Check configuration and Connected App scopes

Plan your first architecture page

Check the Connected App setup with your MuleSoft platform owner, then choose the source links and snapshot displays that support your architecture review.