tracing

Requirement - what kind of business use case are you trying to solve?

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

Probl

Enables minimum set of checkers initially
- gofmt
- goimports
- staticcheck
- misspell

TODO: Each of these require some code changes so, it's ideal to add one after other

• gosec
• govet
• errcheck
• gocritic
• revive
• deadcode
• gosimple
• ineffassign
• depguard
• errorlint
• structcheck
• varcheck
• unused

Seems we have some language features not fully documented (like bitshift operators in #1322).

Would be good to go through language grammar and make sure everything is in the reference guide.

This would allow doing e.g.

$ magic-trace attach -p $(pidof foo) -trigger bar sleep 5

like perf.

Feature Request

tokio-rs/valuable#88 came because I realized that tracing-subscriber, specifically the json formatter, missed some of the logged events.

Crates

tracing-subscriber

Motivation

Logs, and traces, carry information. It is good to know that some of it was lost. In my case what failed to serialize was the error which caused abnormal

Currently, uftrace produces failed-tests.txt after running runtest.py
which contians failed test results.

Problem is, failed-tests.txt can be overwritten when we run runtest.py again.
I think it's better to rename failed-tests.txt to failed-tests.txt.old when runtest.py is executed again
to see how results are different than the latest results.

Also, I think we can make a diff command out

Out of scope during Twitch Series but a nice to have feature that can be implemented

Booking is not currently using Subscription, and it could be done by leveraging parametrized Subscriptions.

Tasks to complete in order to implement this feature:

• Modify onUpdateBooking Subscription to include customer and status
• Implement onUpdateBooking subscription in the Fron

The recently added flags in timescale/promscale#578 are yet to be updated in prom-migrator's readme which can be found here.

Requirement - what kind of business use case are you trying to solve?

When running the SPM demo, see the charts asap.

Problem - what in Jaeger blocks you from solving the requirement?

it takes a few minutes before the charts start drawing any lines.

Proposal - what do you suggest to solve the problem or improve the existing situation?

The shortest time interval is 1hr, but