Repository navigation
Integrations nav - #54
Merged
Merged
Conversation
The INTEGRATIONS section header is non-collapsible, so the six category groups (Chat, Cloud, Data, Infrastructure, SDKs, Ticketing) sat permanently expanded under it, making the sidebar long. Keep Overview visible and move every integration under a single collapsible "All integrations" group, alphabetical. Page files keep their category folders; only the nav grouping changes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Document the PostgreSQL integration (Production, Data category): the monitoring role and pg_monitor grant, the Alloy postgres_exporter config with the labelling and credential-handling notes, how to confirm data arrived, troubleshooting, and what the dashboard deliberately omits. Modeled on the product's installation guide and the Proxmox VE page. Adds it to the All integrations nav group. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Document the iDRAC integration (Production, Infrastructure category): the read-only BMC account, running idrac_exporter with the localhost binding and no-default-entry security notes, the multi-target Alloy scrape with its relabel rules and interval reasoning, confirming data, and troubleshooting. Modeled on the product's installation guide. Adds it to the All integrations nav group. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
PHP now provisions dashboards and alerts in production, so add it to the provisioning table (8 dashboards, 10 rules) with a note on its library dashboards and runtime/SDK-pipeline alert split. Generalize the Ruby-only exception to the no-dashboard SDKs now in the catalog - Ruby, Rust, C++, Swift, and Erlang - and soften the intro accordingly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Nest the integration pages back under category groups - Chat, Cloud, Data, Infrastructure, SDKs, Ticketing - inside the single "All integrations" group, so the section stays compact (Overview + All integrations) while the pages are grouped on expand. PostgreSQL files under Data and iDRAC under Infrastructure. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Per Mikey, the docs should not cover the legacy integrations. Rewrite the Jira page as a Coming soon page (the new Jira is not yet installable), dropping the legacy setup steps and Legacy-toggle instructions, and remove the paragraph documenting the Legacy toggle and legacy view from the integrations landing page. Co-Authored-By: Claude Opus 4.8 <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.