chore(katana): update example

[kariy]

Summary by CodeRabbit

• New Features
  • Updated command parameters for the katana service to enhance configuration clarity.
  • Introduced explicit options for HTTP server and metrics collection addresses and ports.

These changes improve the ease of use and configuration for users managing the katana service.

[coderabbitai]

Walkthrough

Ohayo, sensei! The docker-compose.yml file for the katana service has been updated to change the command parameters for defining the HTTP server's address and port. The previous --host and --port options are now replaced with --http.addr and --http.port. Additionally, the metrics configuration has been enhanced to specify the address and port for metrics collection using --metrics.addr and --metrics.port. The structure of the file remains unchanged for other services.

Changes

File Path	Change Summary
crates/katana/monitoring/docker-compose.yml	Updated command parameters for katana service: changed from --host and --port to --http.addr and --http.port, and added metrics configuration with --metrics.addr and --metrics.port.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Katana
    participant Metrics

    User->>Katana: Start service with new parameters
    Katana->>Metrics: Initialize metrics collection
    Metrics->>Katana: Metrics address and port set

Loading

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 85c0b02 and 3e8d2a5.

📒 Files selected for processing (1)

• crates/katana/monitoring/docker-compose.yml (1 hunks)

🔇 Additional comments (1)

crates/katana/monitoring/docker-compose.yml (1)

13-14: Ohayo! The command parameter updates look good, sensei!

The new parameter structure with --http.addr/--http.port and --metrics.addr/--metrics.port provides better clarity and follows a more consistent naming pattern.

Let's verify that the exposed ports match the new configuration:

✅ Verification successful

Ohayo! Port mappings are perfectly aligned with the command configuration, sensei!

The exposed ports in the docker-compose.yml file match exactly with the command parameters:

• Port 5050 is mapped for HTTP (--http.port 5050)
• Port 9001 is mapped for metrics (--metrics.port 9001)

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify port mappings match the command configuration
# Check if the ports defined in the 'ports' section match those in the command

# Expected output should show matching port mappings (5050:5050 and 9001:9001)
rg -A 2 'ports:' crates/katana/monitoring/docker-compose.yml

Length of output: 217

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.35%. Comparing base (85c0b02) to head (3e8d2a5).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2703      +/-   ##
==========================================
- Coverage   56.36%   56.35%   -0.01%     
==========================================
  Files         411      411              
  Lines       52770    52770              
==========================================
- Hits        29742    29737       -5     
- Misses      23028    23033       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles