file sink

출처: HashiCorp Boundary docs

The file sink writes Boundary audit, observation, system, and telemetry events to a local file, and supports automatic rotation by size, duration, or file count.

sink {
    name = "obs-sink"
    description = "Observations sent to a file"
    event_types = ["observation"]
    format = "cloudevents-json"
    file {
      path = "/var/log/boundary"
      file_name = "events.ndjson"
    }
  }

The sink stanza may be specified more than once to make Boundary send events to multiple sinks; however, each file sink must have a unique path + file_name .

Common parameters

These parameters are shared across all sink types: common sink parameters

file parameters

These parameters are only valid for a file sink.

file_name - Specifies the file name for the sink.
path - Optionally specifies the directory path for the sink. The directory must exist and be writable by the Boundary service user.
rotate_bytes - Optionally specifies the number of bytes that should trigger rotation of a file sink.
rotate_duration - Optionally specifies how often a file sink should be rotated.
rotate_max_files - Optionally specifies how many historical rotated files should be kept for a file sink.

Edit this page on GitHub