[ENH]: Resiliency for local observability

[tazarov]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • Added rate-limiter, batching and Zipkin Storage (MariaDB/MySQL) to make the local observability stack more resilient to failures

Test plan

How are these changes tested?

Manual test

Documentation Changes

N/A

[tazarov]

• [ENH]: Resiliency for local observability #1931 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tazarov and the rest of your teammates on Graphite

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[beggers]

Do we need this? have users asked for it?

[tazarov]

@beggers, I was supporting a user where we had to do some tracing but for Zipkin kept crashing so we had to do this change. So decided to contribute it back to our local observatory.

It is not strictly needed, but for tracing non-trivial use cases it is really helpful.

[beggers]

Seems quite reasonable. Just a small request for documentation :^)