![]() # receiver configuration for different protocols For a production deployment, enable only the receivers you need.Īdditional documentation and more advanced configuration options are available in the receiver README. The following configuration enables all available receivers with their default configuration. # This value may need to be increased if you have large tracesįor more information on configuration options, see here.ĭistributors receive spans and forward them to the appropriate ingesters. # Max gRPC message size that can be received # Register instrumentation handlers (/metrics, etc.) String prefix for all http api endpoints. # and returns only tag values that match the query. # If filtering is enabled, the API accepts a query parameter `q` containing a TraceQL query, Setting to true enables query filtering in tag value search API `/api/v2/search//values`. Setting to true enables multitenancy and requires X-Scope-OrgID header on all requests. For more information on configuration options, see here. You can find more about other supported syntax here. Where default_value is the value to use if the environment variable is undefined. To do this, pass -config.expand-env=true and use: $ You can use environment variable references in the configuration file to set values that need to be configurable during deployment. Use environment variables in the configuration ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |