Get desktop application:
View/edit binary Protocol Buffers messages
A `PollOp` describes each poll operation that completes within the async application.
Used in:
The numeric ID of the op's `Metadata`. This identifies the `Metadata` that describes the `tracing` span corresponding to this op. The metadata for this ID will have been sent in a prior `RegisterMetadata` message.
The resources's ID.
the name of this op (e.g. poll_elapsed, new_timeout, reset, etc.)
Identifies the task context that this poll op has been called from.
Identifies the async op ID that this poll op is part of.
Whether this poll op has returned with ready or pending.
Static data recorded when a new resource is created.
Used in:
The resources's ID. This uniquely identifies this resource across all *currently live* resources. This is also the primary way any operations on a resource are associated with it
The numeric ID of the resources's `Metadata`.
The resources's concrete rust type.
The kind of resource (e.g timer, mutex)
The location in code where the resource was created.
The ID of the parent resource.
Is the resource an internal component of another resource? For example, a `tokio::time::Interval` resource might contain a `tokio::time::Sleep` resource internally.
The kind of resource (e.g. timer, mutex).
Used in:
Every resource is either a known kind or an other (unknown) kind.
`known` signals that this kind of resource is known to the console API.
`other` signals that this kind of resource is unknown to the console API.
`Known` collects the kinds of resources that are known in this version of the API.
Used in:
`TIMER` signals that this is a timer resource, e.g. waiting for a sleep to finish.
A resource state update. Each `ResourceUpdate` contains any resource data that has changed since the last update. This includes: - any new resources that were created since the last update - the current stats for any resource whose stats changed since the last update - any new poll ops that have been invoked on a resource
Used in:
A list of new resources that were created since the last `ResourceUpdate` was sent.
Any resource stats that have changed since the last update.
A list of all new poll ops that have been invoked on resources since the last update.
A count of how many resource events (e.g. polls, creation, etc) were not recorded because the application's event buffer was at capacity. If everything is working normally, this should be 0. If it is greater than 0, that may indicate that some data is missing from this update, and it may be necessary to increase the number of events buffered by the application to ensure that data loss is avoided. If the application's instrumentation ensures reliable delivery of events, this will always be 0.
Task runtime stats of a resource.
Used in:
Timestamp of when the resource was created.
Timestamp of when the resource was dropped.
State attributes of the resource. These are dependent on the type of the resource. For example, a timer resource will have a duration while a semaphore resource may have permits as an attribute. These values may change over time as the state of the resource changes. Therefore, they live in the runtime stats rather than the static data describing the resource.