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

Add error tracking to TRACKER with new EventKind #450

Open
4 tasks
tusharmath opened this issue Mar 4, 2025 · 6 comments · May be fixed by #452
Open
4 tasks

Add error tracking to TRACKER with new EventKind #450

tusharmath opened this issue Mar 4, 2025 · 6 comments · May be fixed by #452
Labels
💎 Bounty enhancement New feature or request

Comments

@tusharmath
Copy link
Collaborator

Problem

The application currently lacks a mechanism to track errors that occur during runtime. This limits our ability to monitor application health and proactively address issues users are encountering.

Proposed Solution

Extend the EventKind enum to include an ErrorOccurred variant that can capture:

  • Error type/category
  • Error message
  • Context (where the error occurred)
  • Stack trace (if available)

Benefits

This enhancement would allow us to:

  1. Monitor error frequencies in production
  2. Identify patterns in error occurrences
  3. Prioritize fixes based on impact
  4. Measure the effectiveness of error-related fixes

Implementation Details

  1. Add ErrorOccurred(ErrorDetails) variant to EventKind enum
  2. Create an ErrorDetails struct to contain error information
  3. Update name() and value() methods to handle the new variant
  4. Add helper methods to easily dispatch errors from anywhere in the codebase

Acceptance Criteria

  • New ErrorOccurred variant added to EventKind
  • Errors are properly serialized and sent to the tracking system
  • Documentation updated to explain error tracking capabilities
  • Tests added for the new functionality

Note

This change should maintain the current opt-out behavior for tracking, ensuring users who have disabled tracking don't have their errors tracked either.

@tusharmath tusharmath added the enhancement New feature or request label Mar 4, 2025
@tusharmath
Copy link
Collaborator Author

/bounty $25

Copy link

algora-pbc bot commented Mar 4, 2025

💎 $25 bounty • Tailcall Inc.

Steps to solve:

  1. Start working: Comment /attempt #450 with your implementation plan
  2. Submit work: Create a pull request including /claim #450 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

🙏 Thank you for contributing to antinomyhq/forge!
🧐 Checkout our guidelines before you get started.
💵 More about our bounty program.

Attempt Started (GMT+0) Solution
🔴 @loop-index Mar 4, 2025, 10:24:11 AM WIP
🟢 @onyedikachi-david #452

@loop-index
Copy link

loop-index commented Mar 4, 2025

/attempt #450

Algora profile Completed bounties Tech Active attempts Options
@loop-index 1 tailcallhq bounty
Roff, Elixir,
Rust
Cancel attempt

@loop-index
Copy link

@tusharmath for ease of testing, do you have any input examples that consistently cause errors?

@tusharmath
Copy link
Collaborator Author

Use a dumber smaller model, u will get issues eventually.

@onyedikachi-david onyedikachi-david linked a pull request Mar 4, 2025 that will close this issue
Copy link

algora-pbc bot commented Mar 4, 2025

💡 @onyedikachi-david submitted a pull request that claims the bounty. You can visit your bounty board to reward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💎 Bounty enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants