Konstantin BogomolovandgVisor bot 832a40527a Add profiling metric flags to output metric data to local TSV file. ...

The idea behind conditionally compiled metrics originally was to use them in
hotpaths for profiling purposes. This CL makes that possible by outputting
declared metrics in TSV format, which can be used to track custom events at
runtime in relatively high resolution.

Usage:
    1. Optionally enable compilation of runsc conditionally-compiled metrics
       by passing in condmetric_profiling to the Go tags.
    2. Add these flags to runsc:
    - [Required] --profiling-metrics-log=/tmp/some.csv
    - [Optional] --profiling-metrics=/task/syscalls,/task/faults
      - If this flag is not specified it will monitor all
        conditionally-compiled metrics by default.
    - [Optional] --profiling-metrics-rate-us=10000

Some future improvements:
    - Flag to output a metric-difference between timestamps instead of
      constant accumulation.
    - Output a gnuplot command along with the data.
    - Current monitoring resolution is limited by what time.Sleep allows.
      This can be overcome by spinning/yielding when lower monitoring
      rates are requested.

PiperOrigin-RevId: 560849611

2023-08-28 16:28:09 -07:00

..

BUILD

Add profiling metric flags to output metric data to local TSV file.

2023-08-28 16:28:09 -07:00

cli_test.go

Make all custom flag.Value implementations idempotent.

2023-07-31 14:53:21 -07:00

main.go

Add profiling metric flags to output metric data to local TSV file.

2023-08-28 16:28:09 -07:00