Tracing: add jaeger and fix service configs #13
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-dev-env#13
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-dev-env:feat/tracing"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
22a2fef00f
to3a6519e2f4
3a6519e2f4
to2e3b3e401c
WIP: [#XX] dev-env: Tracingto Tracing: add jaeger and fix service configs@ -21,0 +23,4 @@
tracing:
enabled: true
exporter: otlp_grpc
endpoint: "192.168.130.120:4317"
I would rather update configs together with image version. Maybe we will change configuration format a bit before merge?
Speaking of config format, just wonder, how configuration is going to look when service dumps trace into the file? Is it new
exporter
constant?yes, it will be new
exporter
output to standard output is also currently supported. In this case, the config looks like this:
reverted config file changes
2e3b3e401c
to93435bfb63