An annotation and its plain ASCII string key.
Annotations are short strings, e.g., the board name or the build version.
Annotations about the device’s state.
An attachment and its plain ASCII string key.
Attachments are larger objects, e.g., log files. They may be binary or text data.
Data known to a component, but not exposed to the platform, to attach to feedback reports.
A Stream of incoming requests for fuchsia.feedback/ComponentDataRegister.
Represents a crash report.
A Stream of incoming requests for fuchsia.feedback/CrashReporter.
Product information to report to the crash server.
A Stream of incoming requests for fuchsia.feedback/CrashReportingProductRegister.
A Stream of incoming requests for fuchsia.feedback/DataProviderController.
A Stream of incoming requests for fuchsia.feedback/DataProvider.
A Stream of incoming requests for fuchsia.feedback/DeviceIdProvider.
Parameters for the DataProvider::GetAnnotations() method.
Parameters for the DataProvider::GetSnapshot() method.
Information about why a device last rebooted.
A Stream of incoming requests for fuchsia.feedback/LastRebootInfoProvider.
Represents a crash report for a native exception out of which the client has built a minidump.
Represents a crash report for a runtime exception, applicable to most languages.
An encoded image of the screen.
Snapshot about the device’s state.
Registers data useful to attach in feedback reports (crash, user feedback or bug reports).
Provides the ability to file crash reports.
Allows a component to choose a different crash reporting product to file crashes for that
component under.
Used to externally control the data provider, say when disk space is becoming scarce or user
privacy settings change.
Provides data useful to attach to feedback reports, e.g., a crash report filed by the system, a
user feedback report filed by a user or a bug report filed by a developer.
Provides the device’s feedback ID.
“Memory” refers to a non-persistent location, e.g. a memory-backed
filesystem.
The encoding used for the image.
Get information about why a device last shutdown. The term reboot is used instead of shutdown
since many developers phrase their questions about shutdowns in terms of reboots and most
components are interested in knowing why the system just rebooted.
Reasons why a device last rebooted.
Represents a specific crash report.