traces

Documentation

Index

• func ReadFromChannel(ctx context.Context, r ReadDecorator) (node.StartFunc[[]request.Span], error)
• type InstanceIDConfig
• type ReadDecorator

Functions

func ReadFromChannel

func ReadFromChannel(ctx context.Context, r ReadDecorator) (node.StartFunc[[]request.Span], error)

Types

type InstanceIDConfig

type InstanceIDConfig struct {
	// HostnameDNSResolution is true if Beyla uses the DNS to resolve the local hostname or
	// false if it uses the local hostname.
	HostnameDNSResolution bool `yaml:"dns" env:"BEYLA_HOSTNAME_DNS_RESOLUTION"`
	// OverrideHostname can be optionally set to avoid resolving any hostname and using this
	// value. Beyla will anyway attach the process ID to the given hostname for composing
	// the instance ID.
	OverrideHostname string `yaml:"override_hostname" env:"BEYLA_HOSTNAME"`
	// OverrideInstanceID can be optionally set to avoid Beyla composing the instance ID
	// and use this value. If you are managing multiple processes from a single Beyla instance,
	// all the processes will have the same Instance ID.
	OverrideInstanceID string `yaml:"override_instance_id" env:"BEYLA_INSTANCE_ID"`

	// InternalIDCacheLen will need to be increased if the number of instrumented processes by
	// a single instance is larger than defaultIDCacheLen
	InternalIDCacheLen int `yaml:"internal_cache_len" env:"BEYLA_INSTANCE_ID_INTERNAL_CACHE_LEN"`
}

InstanceIDConfig configures how Beyla will get the Instance ID of the traces/metrics from the current hostname + the instrumented process PID

type ReadDecorator

type ReadDecorator struct {
	TracesInput <-chan []request.Span

	InstanceID InstanceIDConfig
}

ReadDecorator is the input node of the processing graph. The eBPF tracers will send their traces to the ReadDecorator's TracesInput, and the ReadDecorator will decorate the traces with some basic information (e.g. instance ID) and forward them to the next pipeline stage