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 a generic error handling guide #298

Open
darach opened this issue Jun 2, 2023 · 0 comments
Open

Add a generic error handling guide #298

darach opened this issue Jun 2, 2023 · 0 comments
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation information-architecture Info model, heirarchy or topology

Comments

@darach
Copy link
Member

darach commented Jun 2, 2023

Experienced production tremor users who have grown up with tremor and how it
can manage, compensate, drop or process runtime errors have had the benefit
of face time with tremor maintainers.

We need to document the development and production practices as a guide as
it can be confusing for new adopters and users of tremor and the documentation
we have produced in this regard is weak to this date.

The guide should cover ( post a comment to add to this list, dear readers ):

  • Configuring rust logging levels on the command line
  • Configuring and redirecting errors via the error port and connectors
  • Other common runtime error handling strategies

The guide should not cover QoS, FT, HA as this is a separate topic and requires
an application or system flow model and set of needs to be useful.

@darach darach added bug Something isn't working documentation Improvements or additions to documentation information-architecture Info model, heirarchy or topology labels Jun 2, 2023
@darach darach self-assigned this Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation information-architecture Info model, heirarchy or topology
Projects
None yet
Development

No branches or pull requests

1 participant