tracing

Currently settings page has a time filter component also. Though there is no use of the time filter component on settings page, as the items in settings page don't change on the basis of time selected.

Expected Behavior: Time filter component should be removed from the settings page

version: v0.4.4

![Image 17-11-2021 at 0 07](https://user-images.githubusercontent.com/504541/142045769-ed24

Is your feature request related to a problem? Please describe.

I fiddled around with bpftrace to write internal documentation for my colleagues on how to use it. I chose tracepoint:syscalls:sys_enter_mkdir as a suitable tracepoint for a simple demo, and wrote this code:

bpftrace -e 'tracepoint:syscalls:sys_enter_mkdir { printf("mkdir %s %o\n", str(args->pathname), args->mode); }

It will be useful to have the help specific to use case.

Existing Behavior:
uftrace --help and uftrace replay --help gives the same help prompt.

New Behavior:
uftrace --help can give the help for entire application.
uftrace replay --help can give the help for uftrace replay only.

Reason:

1. This will help narrow down the options available for subprogra

Feature Request

Crates

• tracing-core

Motivation

The Collect trait currently has several methods with default implementations that return an Option or some other "empty" or "default" type. In many cases, this isn't because it makes sense for those methods to be optional, but because they were added after v0.1.0 was released and making them mandatory would have been a

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