Tracing attributes #1488
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
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-node#1488
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-node:feat/tracing_attrs"
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?
This allows to specify key-value attributes for all spans.
Example:
4b6123c4c4
to933a1b577d
933a1b577d
to8c0714cd40
WIP: Tracing attributesto Tracing attributesPlease, use
go.mod:
as prefix for the first commit, as we already do, without inventing something new.@ -261,3 +261,2 @@
"endpoint": "localhost:9090",
"endpoint": "localhost",
"exporter": "otlp_grpc",
"trusted_ca": "/etc/ssl/tracing.pem"
trusted_ca
andendpoint
changes seem unrelated to the commit.Oh, so we had them here, but they were not tested, am I right?
This config was not covered by tests, so it is required to change the examples to write the tests.
@ -17,0 +25,4 @@
environment:
- COLLECTOR_OTLP_ENABLED=true
- SPAN_STORAGE_TYPE=badger
- BADGER_EPHEMERAL=false
I was under impression, that
BADGER_EPHEMERAL
uses temporary file-system, which is exactly what you do below, although explicitly.Why not just use
true
here?copy-pasted from dev-env, but in dev-env repository persisted volume was used.
fixed
8c0714cd40
tof1556e3c42
New commits pushed, approval review dismissed automatically according to repository settings
New commits pushed, approval review dismissed automatically according to repository settings
I trusted autofill:( fixed