Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove unnecessary logs and add Ender metrics #2133

Merged
merged 2 commits into from
Aug 21, 2024
Merged

Remove unnecessary logs and add Ender metrics #2133

merged 2 commits into from
Aug 21, 2024

Conversation

Christopher-Li
Copy link
Contributor

@Christopher-Li Christopher-Li commented Aug 21, 2024

Changelist

[Describe or list the changes made in this PR]

Test Plan

[Describe how this PR was tested (if applicable)]

Author/Reviewer Checklist

  • If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
  • If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
  • If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
  • If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
  • If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
  • Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

  • New Features

    • Enhanced monitoring for Kafka batch processing with metrics reporting on batch sizes and send durations.
    • Added detailed logging for message processing, improving observability and debugging capabilities.
    • Introduced timing metrics for order book price mapping to aid in performance tracking.
  • Bug Fixes

    • Removed verbose logging in batch processing, simplifying logs while maintaining essential functionality.
  • Refactor

    • Streamlined logging output in batch and synchronous handler processing.

@Christopher-Li Christopher-Li requested a review from a team as a code owner August 21, 2024 18:37
Copy link
Contributor

coderabbitai bot commented Aug 21, 2024

Walkthrough

The recent changes enhance observability and performance tracking within the indexing system, particularly with the Kafka producer and message processing. New metrics tracking has been integrated for batch sizes and send durations, while logging has been refined for clarity and insight. Overall, these updates aim to streamline operations, maintain essential functionalities, and support efficient monitoring and debugging processes.

Changes

Files Change Summary
indexer/packages/kafka/src/... Enhanced BatchKafkaProducer with metrics tracking using stats for batch sizes and send durations, improving observability and performance tracking.
indexer/services/ender/src/lib/... Removed detailed logging in BatchedHandlers and SyncHandlers to simplify output while retaining core functionalities and reporting metrics.
indexer/services/ender/src/lib/on-message.ts Added detailed logging in onMessage to capture contextual information during message processing, enhancing debugging and monitoring capabilities.
indexer/services/ender/src/lib/candles-generator.ts Introduced a timing mechanism in getOrderbookMidPriceMap to log execution duration, enhancing performance tracking without altering core logic.

Sequence Diagram(s)

sequenceDiagram
    participant Producer
    participant Kafka
    participant Consumer

    Producer->>Kafka: Send batch of messages
    Kafka->>Producer: Acknowledge receipt
    Producer->>Producer: Track metrics (size, duration)
    Consumer->>Kafka: Fetch messages
    Kafka->>Consumer: Deliver messages
    Consumer->>Consumer: Process messages
    Consumer->>Consumer: Log processing details
Loading

🐇 In the meadow, where data flows,
Metrics dance, as the rabbit knows!
Messages sent with a hop and a skip,
Observability’s here, let’s take a trip!
Logs are light, but insights are bright,
A happy change, oh what a delight! ✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c2099b9 and 2aef590.

Files selected for processing (4)
  • indexer/packages/kafka/src/batch-kafka-producer.ts (3 hunks)
  • indexer/services/ender/src/lib/batched-handlers.ts (1 hunks)
  • indexer/services/ender/src/lib/on-message.ts (1 hunks)
  • indexer/services/ender/src/lib/sync-handlers.ts (1 hunks)
Files skipped from review due to trivial changes (2)
  • indexer/services/ender/src/lib/batched-handlers.ts
  • indexer/services/ender/src/lib/sync-handlers.ts
Additional comments not posted (4)
indexer/packages/kafka/src/batch-kafka-producer.ts (3)

1-1: Import of stats is appropriate.

The addition of stats is necessary for the new metrics functionality.


69-69: Initialization of startTime is correct.

Capturing the start time before sending the batch is necessary for timing metrics.


87-88: Metrics tracking with stats.gauge and stats.timing is well-implemented.

These additions provide valuable insights into batch processing performance.

indexer/services/ender/src/lib/on-message.ts (1)

76-83: Logging enhancement in onMessage is comprehensive.

The logger.info call captures essential details for monitoring message processing.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2aef590 and 1a5c7dc.

Files selected for processing (3)
  • indexer/packages/kafka/src/batch-kafka-producer.ts (3 hunks)
  • indexer/services/ender/src/lib/batched-handlers.ts (2 hunks)
  • indexer/services/ender/src/lib/candles-generator.ts (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • indexer/services/ender/src/lib/batched-handlers.ts
Additional comments not posted (3)
indexer/packages/kafka/src/batch-kafka-producer.ts (2)

1-1: Import changes look good.

The addition of the stats module is appropriate for the new metrics functionality.


Line range hint 69-88: Metrics integration looks good.

The stats.gauge and stats.timing calls effectively enhance observability by tracking batch size and send duration.

Consider verifying the impact of these metrics on performance, especially under high load.

Run the following script to check for any potential performance issues related to the new metrics:

Verification successful

No Immediate Performance Concerns Found for Metrics Integration

The search did not reveal any performance-related comments or TODOs in the codebase concerning the new metrics in batch-kafka-producer.ts. However, consider conducting manual performance testing under high load conditions to ensure these metrics do not introduce latency.

  • File: indexer/packages/kafka/src/batch-kafka-producer.ts
  • Line: 82-91
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the impact of metrics on performance.

# Test: Search for any performance-related comments or TODOs in the codebase.
rg --type ts 'performance|TODO'

Length of output: 24444

indexer/services/ender/src/lib/candles-generator.ts (1)

Line range hint 537-554: Timing metrics integration looks good.

The addition of stats.timing effectively tracks the execution time of the getOrderbookMidPriceMap function, aiding in performance monitoring.

Consider verifying the accuracy of the timing metrics to ensure they reflect the actual execution time.

Run the following script to check for any discrepancies in the timing metrics:

@adamfraser adamfraser merged commit 3c13930 into main Aug 21, 2024
15 checks passed
@adamfraser adamfraser deleted the cl_logging branch August 21, 2024 19:26
@Christopher-Li
Copy link
Contributor Author

@mergify backport indexer/release/v6.x

Copy link
Contributor

mergify bot commented Aug 21, 2024

backport indexer/release/v6.x

❌ No backport have been created

  • Backport to branch indexer/release/v6.x failed

GitHub error: Branch not found

@Christopher-Li
Copy link
Contributor Author

@mergify backport release/indexer/v6.x

Copy link
Contributor

mergify bot commented Aug 21, 2024

backport release/indexer/v6.x

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Aug 21, 2024
Christopher-Li added a commit that referenced this pull request Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

3 participants