Integrations update - #49
Merged
Merged
Conversation
Replace the per-category status tables with Material grid cards: the three live integrations get their own cards linking to their pages, and the remaining categories are grouped into compact coming-soon cards. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Add OpsPilot MCP and OpenTrace, which were missing entirely, and move AWS and the Go, .NET, Java, Node.js, and Python SDKs to available. Jira is still coming soon, not available. Add Unix and Windows under Infrastructure, document the Install and Add to Slack buttons, the status filter, the Legacy toggle, and the per-category counts, and note that FusionReactor is installed outside the catalog. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Card backgrounds were hard-coded to white in both palettes, so cards rendered as white blocks with low-contrast text on the slate theme. Use a raised translucent surface in dark mode, and define the per-scheme border and hover colours that the hover rule already referenced but which were never set. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Most integrations install in one click; those needing configuration carry their steps in the UI. Installing auto-loads default dashboards and alerts onto the account, and each integration's detail view covers how to use it. Close the page by inviting requests for integrations that are not yet listed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Describe the header and the Overview, Permission tiers, Capabilities, Versions, and Changelog panels, replacing the abstract description of where to find usage information. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Covers what connected assistants can read and act on, the supported clients, and the Read-only and Read + Act permission tiers, including that Read-only applies organisation-wide. Add it to the nav under Chat and link it from the Integrations Hub card. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Installing opens a dialog naming the account and offering a permission tier. Record that tiers and their defaults vary by integration, that Capabilities names what an integration provisions, and that the Versions upgrade column and dated changelog entries carry that detail. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Jira is marked Coming soon in the main catalog because the new integration has not shipped, but the legacy one still exists behind the Legacy toggle. Say so on both the Hub and the Jira page, and include the toggle in the setup steps. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
FusionReactor is managed automatically and cannot be modified or removed, rather than being installed outside the catalog as previously stated. List what it provides. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The button is Add to Slack, not Connect, and it opens Slack's own workspace sign-in asking for the workspace URL. Note that OpsPilot can also be addressed from Slack directly. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Slack asks you to sign in to the workspace before authorising OpsPilot; the method depends on how the workspace is configured. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Cover choosing the workspace, the permissions OpsPilot requests, and where to review or change them before allowing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Covers what OpenTrace adds to OpsPilot's answers, that each person connects their own account and it is used only in their conversations, and its single Read-only tier. Add a Data group to the nav and link it from the Integrations Hub card. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
AWS covers the IAM permissions each tier needs, installing once per region, and the two dashboards that read metrics AWS does not publish by default. SDK Integrations covers what the language SDKs provision, in one page rather than one per language, linking out to the existing OpenTelemetry instrumentation pages. Also enable pymdownx.tabbed, which the theme's content.tabs.link feature already depended on. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Connecting the workspace posts nothing until the bot is invited, so replace the default-channel and Save steps with the invite and situation-posting flow. Add the permission tiers, the slash commands, per-person account linking for DMs, that OpsPilot only reads messages mentioning it, and a way to check the connection works. Correct the contact point path to Alerting > Notifications. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Document the install dialog, the Your installation panel, and the Manage integration view, including that narrowing a permission tier applies at once while widening means reinstalling. Record that SDK alert rules ship paused and what each language installs, that dashboards are tagged and shared data sources adopted rather than owned, and that the detail view now uses Installation guide, Versions, and Licenses tabs. Add per-category screenshots in tabs, and qualify every use of "catalog" as the integration catalog to keep it distinct from the Service Catalog. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Both are new in the catalog, and both break the pattern the Hub described: they provision dashboards only and collect nothing themselves, so their dashboards stay empty until Grafana Alloy is configured. Cover the Alloy and exporter setup, the values that silently blank a dashboard when wrong, and the troubleshooting cases. Move Unix to available, add iDRAC and TrueNAS SCALE to the Infrastructure list, and qualify the claim that installing an integration always brings working monitoring. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Unix provisions a host dashboard fed by Alloy's node_exporter collector, with the rootfs mount and job_name naming that decide whether it reports the host or the container. Correct the Proxmox VE config against the real guide: the __param_* keys are quoted and take no trailing underscores, the scrape timeout is 10s, and the exporter host is a placeholder. Both pages now use the lowercase authorization header. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Add the Node.js and Python figures, which show the alert-rule count is not fixed - Node.js ships three and Python five, against four for the others - so drop the claim that every SDK installs four. Record Automatic as a third upgrade type alongside Initial version and Manual, and describe the Licenses tab from what it shows rather than its label. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The page stopped at "each person connects their own client" without saying how. Cover the Connect dialog, the full-access and read-only addresses, the per-client buttons, organisation-wide setup for Claude Team and Enterprise owners, and how the connection choice and the install's tier interact - the stricter of the two wins. Deliberately omit the MCP address, as the product guide does: OpsPilot runs in more than one environment and a written-down address names only one of them. Also record Add instance for integrations that support more than one installation, and the Manage button on an installation row. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The per-language links promised more than they deliver: these dashboards need runtime instrumentation, and the Go, Node.js and Python instrumentation guides never mention it, so following one and finding empty dashboards was a likely outcome. Say what the dashboards need, send people to each integration's Installation guide for the steps, and keep the OTel guides as related reading rather than the route. Use the column for the alert group instead, which is information the table did not carry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Windows ships as installable and needs more setup than the other collector-based integrations: Alloy runs as a Windows service, memory is not a default collector, and the service collector alone emits around 3,750 series on a typical server against a couple of hundred for everything else combined. Cover the relabel rules that cut that to about 500, the collectors that can take Alloy down when what they measure is not installed, and the standalone windows_exporter alternative. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
User MCPs is a separate surface from the catalog: personal account connections the agent uses only in chat, never in scheduled work or on anyone else's behalf. That explains the two-step model on OpenTrace - the organisation installs the integration, each person connects their own account - so say where that second step happens. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Six bare uses of "catalog" had crept back in since the earlier pass, which reads ambiguously against the Service Catalog. Also correct where the Legacy toggle sits on the Jira page - it is at the right-hand end of the category tabs, not the top right. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Both were swept into the previous commit by staging the directory. The 460px capture was rejected as too low-resolution to read, and integrations-view.png is byte-identical to ticketing-view.png. Neither is referenced by any page. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Nathan confirmed the model: MCP integrations are connected per person rather than set up once per organisation, and the chat-only boundary is deliberate - MCP is not used for organisation-wide integrations. The page lists every MCP integration whether connected or not, with a status filter covering connected, not connected, and needs attention for a stale authorisation. Disconnecting wipes that connection's data. Add a table distinguishing User MCPs from OpsPilot MCP, which point in opposite directions and are easily confused. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
All four opened on a one-line description and then a caveat about what the integration does not do, so a reader met the limitation before the benefit. Add a sentence or two up front on what each dashboard gives you and why it is worth the setup, as the style guide asks - value first, then how to get it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The page said disconnecting wipes a connection's data. What was actually described was uninstalling, which is a different action by a different person, and data deletion is not something to paraphrase loosely. Hold it until the behaviour is confirmed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Remove the page layout and status filter detail, the claim about the chat-only boundary being permanent, and the comparison table with OpsPilot MCP. What remains is the part that holds: these are connected per person rather than set up for the organisation, and are used only in that person's chat. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The Jira page still explains that it covers the legacy integration and how to reach it, so the Hub does not need to as well. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The Ruby OpenTelemetry SDK does not officially support metrics, so the pattern every other SDK integration follows does not apply to it. Traces and span metrics still arrive. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Recaptured now the category holds eleven integrations rather than seven, including Docker, Proxmox VE, Unix and Windows as installable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.