Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Run, tap, or top the Worker

Usage example: observability-pipelines-worker <COMMAND>

If you are using a containerized environment, use the docker exec or kubectl exec command to get a shell into the container to run the command.

CommandDescription
runRun the observability pipeline worker.
tapTap a pipeline to observe events from source or transform components. See tap options.
topLists the components of the pipeline and provides statistics such as input and output data rates for each component.

Tap options

Usage example: observability-pipelines-worker tap <OPTIONS> <COMPONENT_ID>

OptionsDescriptions
-i, --interval <INTERVAL>Interval to sample events at, in milliseconds (default: 500).
-u, --url <URL>GraphQL API server endpoint.
-l, --limit <LIMIT>Maximum number of events to sample each interval (default: 100).
-f, --format <FORMAT>Encoding format for events printed to screen.
default: json
possible values: json, yaml, logfmt
--outputs-of <OUTPUTS_OF>Source or processor IDs whose outputs you want to observe (comma-separated; accepts glob patterns).
--inputs-of <INPUTS_OF>Processor or destination IDs whose inputs you want to observe (comma-separated; accepts glob patterns).
-q, --quietQuiet output includes only events.
-m, --metaInclude metadata such as the event’s associated component ID.
-n, --no-reconnectWhether to reconnect if the underlying API connection drops. By default, tap attempts to reconnect if the connection drops.
-d, --duration-ms <DURATION_MS>Specifies a duration (in milliseconds) to sample logs (for example, specifying 10000 samples logs for 10 seconds then exits).

Further reading

Documentation, liens et articles supplémentaires utiles: