Save trace data to an external database #79
drmorr0
started this conversation in
Feature Requests and Future Work
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Right now the tracer just saves everything in memory, and only dumps out requested data "on-demand" when a user makes an
exportAPI call. Maybe the trace should actually be written to a "real" TSDB? Or, maybe it just keeps a certain time window in memory, and then saves a trace of everything to a random S3 bucket after that time window has fallen off?If we write to an external datastore, what datastore should we use?
Related: #60, #80
Beta Was this translation helpful? Give feedback.
All reactions