Skip to content

Improve documentation content and organization#1883

Merged
pavangudiwada merged 2 commits intoupdate-integrations-pagefrom
improve-docs-content
Jul 29, 2025
Merged

Improve documentation content and organization#1883
pavangudiwada merged 2 commits intoupdate-integrations-pagefrom
improve-docs-content

Conversation

@pavangudiwada
Copy link
Copy Markdown
Contributor

  • Update main page alert features to match README with better descriptions
  • Revamp architecture page with detailed component explanations and data flow
  • Add links to Pro Features and pricing in Open Source vs SaaS comparison
  • Add community tutorial by Naren P on Kubernetes monitoring automation

- Update main page alert features to match README with better descriptions
- Revamp architecture page with detailed component explanations and data flow
- Add links to Pro Features and pricing in Open Source vs SaaS comparison
- Add community tutorial by Naren P on Kubernetes monitoring automation
@pavangudiwada pavangudiwada requested a review from aantn July 29, 2025 10:48
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jul 29, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The documentation was updated across several files. A new community tutorial was added, the architecture overview was extensively rewritten for clarity and detail, SaaS feature references were improved with explicit links, and the main feature list was reframed with updated terminology and descriptions. No code or API changes were made.

Changes

Cohort / File(s) Change Summary
Community Tutorials Update
docs/community-tutorials.rst
Added a new tutorial entry titled "Enhancing Kubernetes Monitoring Automation with Robusta" with author and link; no other modifications.
Architecture Documentation Overhaul
docs/how-it-works/architecture.rst
Rewrote and expanded the architecture documentation: detailed modular overview, explicit component roles, new sections on data flow, extended/optional features, and security/networking.
SaaS Features Cross-Referencing
docs/how-it-works/oss-vs-saas.rst
Added direct links to "Robusta Pro Features" and pricing documentation; appended a "Learn More" section; no factual changes.
Feature List Revision
docs/index.rst
Updated and reframed the main feature list: changed feature names and descriptions to emphasize new terminology and focus.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6e56877 and d68f32b.

📒 Files selected for processing (4)
  • docs/community-tutorials.rst (1 hunks)
  • docs/how-it-works/architecture.rst (1 hunks)
  • docs/how-it-works/oss-vs-saas.rst (2 hunks)
  • docs/index.rst (1 hunks)
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch improve-docs-content

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Comment thread docs/how-it-works/architecture.rst Outdated
Comment thread docs/index.rst Outdated
@pavangudiwada pavangudiwada merged commit f4a96e1 into update-integrations-page Jul 29, 2025
5 of 6 checks passed
@pavangudiwada pavangudiwada deleted the improve-docs-content branch July 29, 2025 14:12
@coderabbitai coderabbitai Bot mentioned this pull request Jul 30, 2025
aantn added a commit that referenced this pull request Jul 30, 2025
* docs: reorganize integrations page to focus on alert forwarding

- Remove sinks/destinations from integrations overview
- Restructure page to highlight "Forward Alerts to Robusta"
- Add dedicated section for Prometheus, Nagios, and SolarWinds
- Simplify description to focus on alert forwarding and AI analysis

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: move sinks from Integrations to Notifications & Routing section

- Move sinks reference from Integrations nav to Notifications & Routing nav
- Place sinks as first item in Notifications & Routing section
- Remove sinks from Integrations section to reduce confusion
- Keep logical grouping of alert destinations with notification routing

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: fix integration page hierarchy and remove redundancy

- Redesign integrations overview to be truly high-level with categories
- Rename "Integrating with Prometheus" to "Alert Sources" for broader scope
- Remove duplicate content between overview and subpages
- Focus overview on integration categories rather than detailed setup
- Update navigation labels to match new page structure
- Make user journey clearer: overview → specific alert source setup

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: major reorganization - separate Alert Sources, AI Analysis, and Automation

- Rename "Integrations" section to "Alert Sources" - much clearer purpose
- Create dedicated "AI Analysis" section for Holmes GPT only
- Move KRR, Popeye, and data export to "Automation" section
- Update Alert Sources overview to focus purely on monitoring integrations
- Remove mixed content categories that confused users
- Improve logical flow: Alert Sources → AI Analysis → Notifications → Automation

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: improve notifications navigation with proper hierarchy

- Create new notifications overview page as entry point
- Reorder navigation: Overview → Configuring Sinks → Sink Reference
- Fix information hierarchy so users start with concepts, not specific sinks
- Prevent sphinx menu expansion pushing basic setup pages down
- Add clear getting started flow and common workflows
- Update sink reference title to match new structure

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: move Nagios and SolarWinds to top-level Alert Sources

- Move Nagios and SolarWinds from Prometheus subpages to top-level Alert Sources
- Remove confusing navigation hierarchy where non-Prometheus systems appeared under Prometheus
- Clean up Prometheus page to focus purely on Prometheus/AlertManager integrations
- Remove "Other Alerting Systems" section since they're now top-level
- Create clearer navigation: Overview → Prometheus → Nagios → SolarWinds

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: make Alert Sources overview more concise and actionable

- Remove verbose explanations and get straight to the point
- Lead with clear action: "Choose your monitoring system"
- Make card descriptions more direct and useful
- Add practical note about webhook compatibility for other systems
- Cut word count by ~60% while improving clarity

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: remove negative labels like 'legacy' and 'enterprise'

- Change 'Legacy systems' to 'Nagios monitoring'
- Change 'Enterprise monitoring' to 'SolarWinds monitoring'
- Keep descriptions neutral and product-focused
- Avoid terms that might make users feel bad about their tech choices

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: add helpful link to webhook documentation for other systems

- Link 'HTTP webhooks' to webhook triggers documentation
- Provides users with concrete next steps if their system isn't listed
- Makes the fallback option actionable rather than just informational

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: fix webhook link to point to correct API documentation

- Link HTTP webhooks to exporting-data.rst which contains POST /api/alerts endpoint
- This is the correct endpoint for sending alerts from any system via HTTP
- Previous link was to webhook triggers which is for different use case

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: move webhook API to Alert Sources section where it belongs

- Move exporting-data.rst from Automation to Alert Sources as "Custom Webhooks"
- This contains the POST /api/alerts endpoint for sending alerts TO Robusta
- Makes it discoverable for users wanting to integrate custom monitoring systems
- Logical placement with other alert source integrations

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: switch from horizontal tabs to left sidebar navigation

- Remove navigation.tabs and navigation.tabs.sticky features
- Add navigation.sections and navigation.expand for better sidebar
- This provides more room for additional top-level sections
- Makes navigation more scalable for future section additions

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* switch to sidebar navigation

* clarify on pro features

* put robusta pro features in the right place

* docs

* Update index.rst

* fixes

* Improve documentation content and organization (#1883)

* Improve documentation content and organization

- Update main page alert features to match README with better descriptions
- Revamp architecture page with detailed component explanations and data flow
- Add links to Pro Features and pricing in Open Source vs SaaS comparison
- Add community tutorial by Naren P on Kubernetes monitoring automation

* Updated Robusta signup link

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Pavan Gudiwada <25551553+pavangudiwada@users.noreply.github.com>
Co-authored-by: Pavan Gudiwada <pavangudiwada@users.noreply.github.com>
@coderabbitai coderabbitai Bot mentioned this pull request Oct 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants