tracing

Requirement

As a user downloading Jaeger images from Docker Hub, I want to be able to read a description and basic usage in the Docker Hub repositories.

Problem

Right now most of Jaeger's Docker Hub repositories contain neither description nor the readme.

Proposal

Use Docker Hub API to push the README files from the respective cmd/*** dirs when publishing Docker images.

Example

The current overview section in the application detail page has 4 charts which need to move from promQL to query-builder APIs. Below are the charts on that page:

1. Application latency
2. Requests
3. Error Percentage
4. Top Endpoints

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

Due to #1498, graphviz test is broken now as follows.

$ ./runtest.py -vdp -O0 207
      ...
t207_dump_graphviz: diff result of -pg -O0
--- expect      2022-07-30 22:48:43.990733694 +0100
+++ result      2022-07-30 22:48:43.990733694 +0100
@@ -1,12 +1,7 @@
-digraph "/tmp/test_abc_bJ93Xv/t-abc" {

-splines=ortho;
-concentrate=true;
-node [shape="rect",fontsize="7",style="filled"]

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.

It seems to me that UTC is selected for on the wire representation of time as well as in the database (jaegertracing/jaeger#712), which sort of makes sense, at least with a somewhat naive handling of timezones. However, I think that the Jaeger UI should support displaying times in the timezone local to the user, i.e. of the browser as to reduce the mental load when viewing