Inspect Quick Start

This document is a guide on how to get started with Component Inspection depending on your needs:

I want to learn more about Inspect concepts

Read Getting Started with Inspect and the README.

I want to know how to use the iquery tool

Read the iquery manual. For detailed examples of usage, see Getting Started with Inspect.

This document provides a simplified example of iquery below.

I have an existing or new component, and I want to support inspection.

Continue reading this document.

Quick Start

See below for the quick start guide in your language of choice.



This section assumes you are writing an asynchronous component and that some part of your component (typically looks like this:

async::Loop loop(&kAsyncLoopConfigAttachToCurrentThread);
auto component_context = sys::ComponentContext::Create();
// ...

This sets up an async loop, creates a ComponentContext wrapping handles provided by the runtime, and then runs that loop following some other initialization work.

Add the following include

#include <lib/sys/inspect/cpp/component.h>

Change your initialization code to look like the following:

async::Loop loop(&kAsyncLoopConfigAttachToCurrentThread);
auto component_context = sys::ComponentContext::Create();
auto inspector =
inspect::Node& root_node = inspector->root();
// ...

You are now using Inspect! To add some data and see it in action, try adding the following:

// Important: Make sure to hold on to hello_world_property and don't let it go out of scope.
auto hello_world_property = root_node.CreateStringProperty("hello", "world");

See Viewing Inspect Data below to view what you are now exporting.

See Supported Data Types for a full list of data types you can try.

Want to test your Inspect integration? Include lib/inspect/testing/cpp/inspect.h in your unit test for a full set of matchers. See this example of how it is used.

Read on to learn how Inspect is meant to be used in C++.

Dynamic Value Support

Certain features, such as LazyProperty, LazyMetric, and ChildrenCallback are deprecated, but a replacement is on the way (CF-761). If you determine that you need one of these data types, you may use the deprecated API by replacing the setup code with the following:

#include "src/lib/inspect_deprecated/inspect.h"

// Legacy work required to expose an inspect hierarchy over FIDL.
auto root = component::ObjectDir::Make("root");
fidl::BindingSet<fuchsia::inspect::deprecated::Inspect> inspect_bindings_;
auto root_node = inspect::Node(root);

C++ Library Concepts

Now that you have a root_node you may start building your hierarchy. This section describes some important concepts and patterns to help you get started.

  • A Node may have any number of key/value pairs called Properties.
  • The key for a Value is always a UTF-8 string, the value may be one of the supported types below.
  • A Node may have any number of children, which are also Nodes.

The code above gives you access to a single node named "root". hello_world_property is a Property that contains a string value (aptly called a StringProperty).

  • Values and Nodes are created under a parent Node.

Class Node has creator methods for every type of supported value. hello_world_property was created using CreateStringProperty. You could create a child under the root node by calling root_node.CreateChild("child name"). Note that names must always be UTF-8 strings.

  • Values and Nodes have strict ownership semantics.

hello_world_property owns the Property. When it is destroyed (goes out of scope) the underlying Property is deleted and no longer present in your component's Inspect output. This is true for Metrics and child Nodes as well.

  • Inspection is best-effort.

Due to space limitations, the Inspect library may be unable to satisfy a Create request. This error is not surfaced to your code: you will receive a Node/Metric/Property object for which the methods are no-ops.

  • Pattern: Pass in child Nodes to child objects.

It is useful to add an inspect::Node argument to the constructors for your own classes. The parent object, which should own its own inspect::Node, may then pass in the result of CreateChild(...) to its children when they are constructed:

class Child {
    Child(inspect::Node my_node) : my_node_(std::move(my_node)) {
      // Create metrics and properties on my_node_.

    inspect::Node my_node_;
    inspect::StringProperty some_property_;
    // ... more properties and metrics

class Parent {
    // ...

    void AddChild() {
      // Note: inspect::UniqueName returns a globally unique name with the specified prefix.

    std::vector<Child> children_;
    inspect::Node my_node_;



This section assumes you are writing an asynchronous component and that some part of your component (typically looks similar to this:

async fn main() -> Result<(), Error> {
  let mut fs = ServiceFs::new_local();

Add the following to your initialization code:

// This creates the root of an inspect tree.
let inspector = inspect::Inspector::new();

// This exports the VMO to the default path for reading at the standard
// location "/root.inspect".
inspector.export(&mut fs);

// This will give you a reference to the root node of the inspect tree.
let root = inspector.root();

Don't forget to use fuchsia_inspect as inspect;!

Now you can use inspect! For example try the following:

let hello_world_property = inspect.create_string("hello", "world!");

See this example for further learning of other types offered by the API.

To test your inspect code, you can use assert_inspect_tree:

assert_inspect_tree!(inspector, root: {
  child1: {
    some_property_name: 1.0,
    another_property: "example",
    children: {},

Learn more about testing inspect.

See the docs to learn about other methods offered by the Rust API.

See Viewing Inspect Data below to view what you are now exporting.

See Supported Data Types for a full list of data types you can try.

Rust Library Concepts

Refer to C++ Library Concepts, as similar concepts apply in Rust.


This example obtains and adds several data types and nested children to the root Inspect node.

flutter_app("inspect_mod") {
  deps = [


import 'package:fuchsia_inspect/inspect.dart' as inspect;
class RootIntentHandler extends IntentHandler {
  void handleIntent(Intent intent) {
    var inspectNode = inspect.Inspect().root;


import 'package:fuchsia_inspect/inspect.dart' as inspect;

class InspectExampleApp extends StatelessWidget {
  final inspect.Node _inspectNode;

  InspectExampleApp(this._inspectNode) {
    _inspectNode.stringProperty('greeting').setValue('Hello World');
    _inspectNode.doubleProperty('double down')..setValue(1.23)..add(2);
    _inspectNode.byteDataProperty('bytes').setValue(ByteData(4)..setUint32(0, 0x01020304));
  Widget build(BuildContext context) {
    return MaterialApp(
      home: _InspectHomePage(
          inspectNode: _inspectNode.child('home-page')),

You can call delete() on a Node or Property when you're done with it. Deleting a node deletes everything under it.

delete() can also be triggered by a Future completing or broadcast Stream closing:

var answerFuture = _answerFinder.getTheAnswer();
var wait = _inspectNode.stringProperty('waiting')..setValue('for a hint');

stream.listen((_) {}, onDone: node.delete);

// FIDL proxies contain a future that completes when the connection closes:
final _proxy = my_fidl_import.MyServiceProxy();

Viewing Inspect Data

You can use the iquery tool to view the Inspect data you exported from your component by looking through the Hub.

This section assumes you have SSH access to your running Fuchsia system and that you started running your component. We will use the name my_component.cmx as a placeholder for the name of your component.

Find your Inspect endpoint

Try the following:

# This prints all Inspect endpoints on the system.
$ iquery --find /hub

# This filters the above list to only print your component.
$ iquery --find /hub | grep my_component.cmx

Under the listed directories you will see some paths including "system_objects." This Inspect data is placed there by the Component Runtime itself.

Your component's endpoint will be listed as <path>/my_component.cmx/<id>/out/inspect/root.inspect.

Read your Inspect data

Navigate to the out/ directory that was printed above, and run:

$ iquery --recursive root.inspect

# OR, if you used Dynamic Values:
$ iquery --recursive .

This will print out the following if you followed the suggested steps above:

  hello = world

Supported Data Types

Type Description Notes
IntMetric A metric containing a signed 64-bit integer. All Languages
UIntMetric A metric containing an unsigned 64-bit integer. Not supported in Dart
DoubleMetric A metric containing a double floating-point number. All Languages
{Int,Double,UInt}Array An array of metric types, includes typed wrappers for various histograms. Same language support as base metric type
StringProperty A property with a UTF-8 string value. All Languages
ByteVectorProperty A property with an arbitrary byte value. All Languages
Node A node under which metrics, properties, and more nodes may be nested. All Languages
Link Instantiates a complete tree of Nodes dynamically. IN PROGRESS(CF-761): This will replace Lazy metrics, properties, and children