Event tracker fixes

[tphakala]

• Event tracker functionality was using hard coded interval values, fixed code to use realtime.interval value instead
• MQTT publish action frequency was not controlled by event tracker

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces modifications to event tracking mechanisms across multiple files in the internal/analysis/processor package. The changes focus on refining the event tracking logic for various actions like logging, database operations, bird weather submissions, and MQTT publishing. A new EventTrackerConfig struct is introduced to provide more flexible configuration of event intervals. The Processor initialization is updated to pass a time-based interval to the EventTracker, allowing more dynamic control over event handling timing.

Changes

File	Change Summary
internal/analysis/processor/actions.go	Inverted event tracking conditions for LogAction, DatabaseAction, BirdWeatherAction, and MqttAction. Actions now only execute if the corresponding event is tracked.
internal/analysis/processor/eventtracker.go	Added EventTrackerConfig struct with interval configurations. Updated NewEventTracker to accept a duration parameter and include MQTTPublish in event handlers.
internal/analysis/processor/processor.go	Modified New function to pass a time-based interval to EventTracker derived from settings.Realtime.Interval.

Sequence Diagram

sequenceDiagram
    participant Processor
    participant EventTracker
    participant Actions
    
    Processor->>EventTracker: Initialize with interval
    EventTracker-->>Processor: Configured tracker
    
    Actions->>EventTracker: Check event tracking
    alt Event is tracked
        Actions->>Actions: Execute action
    else Event not tracked
        Actions-->>Actions: Early return
    end

Loading

Poem

🐰 Hop, hop, tracking events with glee,
Intervals set, actions flow free
Milliseconds dance, logic refined
Efficiency leaps, code intertwined
A rabbit's code, precise and bright! 🕒

---

📜 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 ec4bc1e and 2905037.

📒 Files selected for processing (3)

• internal/analysis/processor/actions.go (3 hunks)
• internal/analysis/processor/eventtracker.go (1 hunks)
• internal/analysis/processor/processor.go (1 hunks)

Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[tphakala]

Fixes #351