Skip to content

Latest commit

 

History

History

filereceiver

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
internal/metadata
internal/metadata
 
 
testdata
testdata
 
 
Makefile
Makefile
 
 
README.md
README.md
 
 
config.go
config.go
 
 
config_test.go
config_test.go
 
 
doc.go
doc.go
 
 
factory.go
factory.go
 
 
factory_test.go
factory_test.go
 
 
file_reader.go
file_reader.go
 
 
file_reader_test.go
file_reader_test.go
 
 
go.mod
go.mod
 
 
go.sum
go.sum
 
 
metadata.yaml
metadata.yaml
 
 
receiver.go
receiver.go
 
 
receiver_test.go
receiver_test.go
 
 
replay_timer.go
replay_timer.go
 
 
replay_timer_test.go
replay_timer_test.go
 
 

README.md

File Receiver

Status
Stability development: metrics, traces, logs
Distributions contrib
Issues Open issues Closed issues
Code Owners @pmcollins, @djaglowski

The File Receiver reads the output of a File Exporter, converting that output to metrics, and sending the metrics down the pipeline.

Currently, the only file format supported is the File Exporter's JSON format. Reading compressed output, rotated files, or telemetry other than metrics are not supported at this time.

Getting Started

The following setting is required:

  • path [no default]: the file in the same format as written by a File Exporter.

The following setting is optional:

  • throttle [default: 1]: a determines how fast telemetry is replayed. A value of 0 means that it will be replayed as fast as the system will allow. A value of 1 means that it will be replayed at the same rate as the data came in, as indicated by the timestamps on the input file's telemetry data. Higher values mean that the replay speed will be slower by a multiple of the throttle value. Values can be decimals, e.g. 0.5 means that telemetry will be replayed at 2x the rate indicated by the telemetry's timestamps.

Example

receivers:
  file:
    path: my-telemetry-file
    throttle: 0.5