Documentation
¶
Index ¶
- func ConstructMetricsSender(t *testing.T, receiver string) testbed.MetricDataSender
- func ConstructReceiver(t *testing.T, exporter string) testbed.DataReceiver
- func ConstructTraceSender(t *testing.T, receiver string) testbed.DataSender
- func CreateConfigYaml(sender testbed.DataSender, receiver testbed.DataReceiver, ...) string
- type PipelineDef
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func ConstructMetricsSender ¶
func ConstructMetricsSender(t *testing.T, receiver string) testbed.MetricDataSender
ConstructMetricsSender creates a testbed metrics sender from the passed-in metrics sender identifier.
func ConstructReceiver ¶
func ConstructReceiver(t *testing.T, exporter string) testbed.DataReceiver
ConstructReceiver creates a testbed receiver from the passed-in recevier identifier.
func ConstructTraceSender ¶
func ConstructTraceSender(t *testing.T, receiver string) testbed.DataSender
ConstructTraceSender creates a testbed trace sender from the passed-in trace sender identifier.
func CreateConfigYaml ¶
func CreateConfigYaml( sender testbed.DataSender, receiver testbed.DataReceiver, processors map[string]string, pipelineType string, ) string
CreateConfigYaml creates a yaml config for an otel collector given a testbed sender, testbed receiver, any processors, and a pipeline type. A collector created from the resulting yaml string should be able to talk the specified sender and receiver.
Types ¶
type PipelineDef ¶
type PipelineDef struct { Receiver string Exporter string TestName string DataSender testbed.DataSender DataReceiver testbed.DataReceiver ResourceSpec testbed.ResourceSpec }
PipelineDef holds the information necessary to run a single testbed configuration.
func LoadPictOutputPipelineDefs ¶
func LoadPictOutputPipelineDefs(fileName string) ([]PipelineDef, error)
LoadPictOutputPipelineDefs generates a slice of PipelineDefs from the passed-in generated PICT file. The result should be a set of PipelineDefs that covers all possible pipeline configurations.
Directories
¶
Path | Synopsis |
---|---|
[testbed exporter] -> [otelcol receiver] -> [otelcol exporter] -> [testbed receiver] -> [test harness] the difference being the testHarness, which is connected to [testbed receiver] as its metrics consumer, listening for datapoints.
|
[testbed exporter] -> [otelcol receiver] -> [otelcol exporter] -> [testbed receiver] -> [test harness] the difference being the testHarness, which is connected to [testbed receiver] as its metrics consumer, listening for datapoints. |