![]() ![]() Processors can be found by combining the list foundįor detailed processor configuration, see the Processors are enabled viaĪ basic example of the default processors is provided below. Which the processor provides a default configuration are overridden.Ĭonfiguring a processor does not enable it. With default settings, but many require configuration. The processors: section is how processors are configured. Processors are run on data between being received and being exported. Receivers : # Data sources: logs fluentforward : endpoint : 0.0.0.0 : 8006 # Data sources: metrics hostmetrics : scrapers : cpu : disk : filesystem : load : memory : network : process : processes : paging : # Data sources: traces jaeger : protocols : grpc : thrift_binary : thrift_compact : thrift_http : # Data sources: traces kafka : protocol_version : 2.0.0 # Data sources: traces, metrics opencensus : # Data sources: traces, metrics, logs otlp : protocols : grpc : http : # Data sources: metrics prometheus : config : scrape_configs : - job_name : otel-collector scrape_interval : 5s static_configs : - targets : # Data sources: traces zipkin : Processors A basic example of receivers is provided below.įor detailed receiver configuration, see the One or more receivers must be configured. Receiver provides a default configuration are overridden.Ĭonfiguring a receiver does not enable it. Configuration parameters specified for which the ![]() Wants to change the default configuration then such configuration must beĭefined in this section. With default settings so simply specifying the name of the receiver is enough toĬonfigure it (for example, zipkin:). The receivers: section is how receivers are configured. Receivers : otlp : protocols : grpc : exporters : otlp : endpoint : .local:443 service : extensions : pipelines : traces : receivers : processors : exporters : ReceiversĪ receiver, which can be push or pull based, is how data gets into theĬollector. Versioning and stability for OpenTelemetry clients.Semantic conventions for GraphQL Server.Semantic conventions for database client calls.Semantic conventions for Compatibility components.Performance Benchmark of OpenTelemetry API.Performance and Blocking of OpenTelemetry API.Metric Requirement Levels for Semantic Conventions.Semantic Conventions for Feature Flag Evaluations.Semantic Convention for event attributes. ![]() Mapping Arbitrary Data to OTLP AnyValue.Attribute Requirement Levels for Semantic Conventions. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |