Skip to content
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

slog-to-otel doesn't handle upgrade plan slog entries #8272

Closed
mhofman opened this issue Aug 29, 2023 · 1 comment · Fixed by #10357
Closed

slog-to-otel doesn't handle upgrade plan slog entries #8272

mhofman opened this issue Aug 29, 2023 · 1 comment · Fixed by #10357
Assignees
Labels
bug Something isn't working telemetry

Comments

@mhofman
Copy link
Member

mhofman commented Aug 29, 2023

Describe the bug

The stacking of upgrade slog entries seem to cause the slog-to-otel logic to error

To Reproduce

See logs

Expected behavior

Slog traces with all spans and no errors

Platform Environment

agoric-upgrade-11 on emerynet

Screenshots

Error tracing slog: {
type: 'cosmic-swingset-upgrade-finish',
blockHeight: 1260068,
blockTime: 1693317619,
time: 1693318166.071951,
monotime: 306.1746670629978} (Error#1)
Error#1: Check failed
at Object.pop (packages/telemetry/src/slog-to-otel.js:448:11)
at slogSender (packages/telemetry/src/slog-to-otel.js:918:15)
at wrappedSlogSender (packages/telemetry/src/slog-to-otel.js:1072:7)
at slogSender (packages/telemetry/src/make-slog-sender.js:154:11)
at process.<anonymous> (packages/telemetry/src/slog-sender-pipe-entrypoint.js:117:15)
at process.emit (node:events:514:28)
Error tracing slog: {
type: 'cosmic-swingset-begin-block',
blockHeight: 1260068,
blockTime: 1693317619,
inboundQueueStats: {
cosmic_swingset_inbound_queue_length: 0,
cosmic_swingset_inbound_queue_add: 0,
cosmic_swingset_inbound_queue_remove: 0
},
time: 1693318166.078734,
monotime: 306.1814518990517
} (Error#2)
Error#2: Check failed
at Object.begin (packages/telemetry/src/kv-string-store.js:28:7)
at slogSender (packages/telemetry/src/slog-to-otel.js:930:30)
at wrappedSlogSender (packages/telemetry/src/slog-to-otel.js:1072:7)
at slogSender (packages/telemetry/src/make-slog-sender.js:154:11)
at process.<anonymous> (packages/telemetry/src/slog-sender-pipe-entrypoint.js:117:15)
at process.emit (node:events:514:28)
@mhofman mhofman added bug Something isn't working telemetry labels Aug 29, 2023
@mhofman mhofman self-assigned this Aug 29, 2023
@mhofman
Copy link
Member Author

mhofman commented Dec 22, 2023

Potential idea to avoid further regression of this kind: duplicate / move the check for unknown slog entries from the deployment / loadgen integration test, to the docker upgrade test.

mhofman added a commit that referenced this issue Oct 29, 2024
@mergify mergify bot closed this as completed in 0ffdf00 Oct 29, 2024
@mergify mergify bot closed this as completed in #10357 Oct 29, 2024
mergify bot added a commit that referenced this issue Oct 29, 2024
closes: #10332 
closes: #8272
refs: #9569

## Description

Adds slog events for the bundle install and timer poll run triggers.
Add more context to the bridge and deliver inbound triggers.
Fixes the otel trace processing of upgrade events.

### Security Considerations
None

### Scaling Considerations
This adds a little more data to our slogs, but relatively minor compared to the amount of data we already generate.

### Documentation Considerations
None

### Testing Considerations

The integration test has limited coverage of the otel slog processor. I will repurpose #9569 to add testing in a3p, but in the mean time this change cannot affect operations and at worse the modification are not sufficient to our needs.

### Upgrade Considerations
Requires a chain software upgrade but the changes do not affect consensus and could be locally cherry-picked.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working telemetry
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant