-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[Jaeger-V2] Add configurable index data layout and rollover frequency #5790
Changes from all commits
47c0a63
4ce1b97
037f479
2e86cd2
cf818b8
890daa3
3e65f6b
f99515e
b712a72
b9cebd6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,10 +20,35 @@ extensions: | |
backends: | ||
some_storage: | ||
elasticsearch: | ||
index_prefix: "jaeger-main" | ||
indices: | ||
JaredTan95 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
spans: | ||
prefix: "jaeger-main" | ||
date_layout: "2006-01-02" | ||
rollover_frequency: "day" | ||
shards: 5 | ||
replicas: 1 | ||
services: | ||
prefix: "jaeger-main" | ||
date_layout: "2006-01-02" | ||
rollover_frequency: "day" | ||
shards: 5 | ||
replicas: 1 | ||
dependencies: | ||
prefix: "jaeger-main" | ||
date_layout: "2006-01-02" | ||
rollover_frequency: "day" | ||
shards: 5 | ||
replicas: 1 | ||
sampling: | ||
date_layout: "2006-01-02" | ||
rollover_frequency: "day" | ||
shards: 5 | ||
replicas: 1 | ||
another_storage: | ||
elasticsearch: | ||
index_prefix: "jaeger-archive" | ||
indices: | ||
spans: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Q: is the services index being built at all when the storage is in the archive mode? I don't think it should be, but in this configuration There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @yurishkuro my apologies i don't have a lot of context here but how should we proceed with this? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we need to check in the code if writing/reading to/from Archive storage relies exclusively on spans index, or if it uses any other indices. If the latter, then we need to override the prefix to |
||
prefix: "jaeger-archive" | ||
|
||
receivers: | ||
otlp: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: we may want to rethink if we still want a single field in the config for index prefix, which would apply if the individual index options didn't override it explicitly. This would simplify the configuration while maintaining the flexibility.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yurishkuro is this still something we want to address?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be a good usability improvement - perhaps under Indices we can have a "defaults" entry that will apply unless overwritten by the more specific entries like
spans:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yurishkuro this PR is already pretty big (31 files changed). thoughts on getting this PR in and tackling this in a follow-up PR under #6059. There's some follow-up work that needs to be done there anyway for aligning the config with OTEL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw, it might be a good idea to try out Sapling and do stacked PRs, to avoid precisely this problem (at work we always use stacked PRs)