github.com/muhammadn/cortex@v1.9.1-0.20220510110439-46bb7000d03d/docs/configuration/single-process-config-blocks.yaml (about)

     1  
     2  # Configuration for running Cortex in single-process mode.
     3  # This should not be used in production.  It is only for getting started
     4  # and development.
     5  
     6  # Disable the requirement that every request to Cortex has a
     7  # X-Scope-OrgID header. `fake` will be substituted in instead.
     8  auth_enabled: false
     9  
    10  server:
    11    http_listen_port: 9009
    12  
    13    # Configure the server to allow messages up to 100MB.
    14    grpc_server_max_recv_msg_size: 104857600
    15    grpc_server_max_send_msg_size: 104857600
    16    grpc_server_max_concurrent_streams: 1000
    17  
    18  distributor:
    19    shard_by_all_labels: true
    20    pool:
    21      health_check_ingesters: true
    22  
    23  ingester_client:
    24    grpc_client_config:
    25      # Configure the client to allow messages up to 100MB.
    26      max_recv_msg_size: 104857600
    27      max_send_msg_size: 104857600
    28      grpc_compression: gzip
    29  
    30  ingester:
    31    lifecycler:
    32      # The address to advertise for this ingester.  Will be autodiscovered by
    33      # looking up address on eth0 or en0; can be specified if this fails.
    34      # address: 127.0.0.1
    35  
    36      # We want to start immediately and flush on shutdown.
    37      join_after: 0
    38      min_ready_duration: 0s
    39      final_sleep: 0s
    40      num_tokens: 512
    41  
    42      # Use an in memory ring store, so we don't need to launch a Consul.
    43      ring:
    44        kvstore:
    45          store: inmemory
    46        replication_factor: 1
    47  
    48  storage:
    49    engine: blocks
    50  
    51  blocks_storage:
    52    tsdb:
    53      dir: /tmp/cortex/tsdb
    54  
    55    bucket_store:
    56      sync_dir: /tmp/cortex/tsdb-sync
    57  
    58    # You can choose between local storage and Amazon S3, Google GCS and Azure storage. Each option requires additional configuration
    59    # as shown below. All options can be configured via flags as well which might be handy for secret inputs.
    60    backend: s3 # s3, gcs, azure or filesystem are valid options
    61    s3:
    62      bucket_name: cortex
    63      endpoint: s3.dualstack.us-east-1.amazonaws.com
    64      # Configure your S3 credentials below.
    65      # secret_access_key: "TODO"
    66      # access_key_id:     "TODO"
    67  #  gcs:
    68  #    bucket_name: cortex
    69  #    service_account: # if empty or omitted Cortex will use your default service account as per Google's fallback logic
    70  #  azure:
    71  #    account_name:
    72  #    account_key:
    73  #    container_name:
    74  #    endpoint_suffix:
    75  #    max_retries: # Number of retries for recoverable errors (defaults to 20)
    76  # filesystem:
    77  #   dir: ./data/tsdb
    78  
    79  compactor:
    80    data_dir: /tmp/cortex/compactor
    81    sharding_ring:
    82      kvstore:
    83        store: inmemory
    84  
    85  frontend_worker:
    86    match_max_concurrent: true
    87  
    88  ruler:
    89    enable_api: true
    90    enable_sharding: false
    91  
    92  ruler_storage:
    93    backend: local
    94    local:
    95      directory: /tmp/cortex/rules