You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
closes: #10332closes: #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.
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
The text was updated successfully, but these errors were encountered: