Cortex Service status does not show alertmanager as "running"

[babvin]

config file:

cat single-process-config-blocks-local.yaml

# Configuration for running Cortex in single-process mode.
# This should not be used in production.  It is only for getting started
# and development.

# Disable the requirement that every request to Cortex has a
# X-Scope-OrgID header. `fake` will be substituted in instead.
auth_enabled: false

server:
  http_listen_port: 9009

  # Configure the server to allow messages up to 100MB.
  grpc_server_max_recv_msg_size: 104857600
  grpc_server_max_send_msg_size: 104857600
  grpc_server_max_concurrent_streams: 1000

distributor:
  shard_by_all_labels: true
  pool:
    health_check_ingesters: true

ingester_client:
  grpc_client_config:
    # Configure the client to allow messages up to 100MB.
    max_recv_msg_size: 104857600
    max_send_msg_size: 104857600
    grpc_compression: gzip

ingester:
  lifecycler:
    # The address to advertise for this ingester.  Will be autodiscovered by
    # looking up address on eth0 or en0; can be specified if this fails.
    # address: 127.0.0.1

    # We want to start immediately and flush on shutdown.
    min_ready_duration: 0s
    final_sleep: 0s
    num_tokens: 512

    # Use an in memory ring store, so we don't need to launch a Consul.
    ring:
      kvstore:
        store: inmemory
      replication_factor: 1

blocks_storage:
  tsdb:
    dir: /tmp/cortex/tsdb

  bucket_store:
    sync_dir: /tmp/cortex/tsdb-sync

  # You can choose between local storage and Amazon S3, Google GCS and Azure storage. Each option requires additional configuration
  # as shown below. All options can be configured via flags as well which might be handy for secret inputs.
  backend: filesystem # s3, gcs, azure or filesystem are valid options
# s3:
#   bucket_name: cortex
#   endpoint: s3.dualstack.us-east-1.amazonaws.com
    # Configure your S3 credentials below.
    # secret_access_key: "TODO"
    # access_key_id:     "TODO"
#  gcs:
#    bucket_name: cortex
#    service_account: # if empty or omitted Cortex will use your default service account as per Google's fallback logic
#  azure:
#    account_name:
#    account_key:
#    container_name:
#    endpoint_suffix:
#    max_retries: # Number of retries for recoverable errors (defaults to 20)
  filesystem:
    dir: ./data/tsdb

compactor:
  data_dir: /tmp/cortex/compactor
  sharding_ring:
    kvstore:
      store: inmemory

frontend_worker:
  match_max_concurrent: true

ruler:
  enable_api: true

ruler_storage:
  backend: local
  local:
    directory: /tmp/cortex/rules
alertmanager:
  data_dir: /data/alertmanager
  external_url: http://localhost:9005/alertmanager
alertmanager_storage:
  backend: local
  local:
    path: /tmp/cortex

Unable to load the config:

cortextool alertmanager load /root/alertmanager.yml --id fake --address http://localhost:9005/alertmanager
ERRO[0000] error during request to cortex api            error="Post \"http://localhost:9005/alertmanager/api/v1/alerts\": dial tcp [::1]:9005: connect: connection refused" method=POST url="http://localhost:9005/alertmanager/api/v1/alerts"
cortextool: error: Post "http://localhost:9005/alertmanager/api/v1/alerts": dial tcp [::1]:9005: connect: connection refused, try --help
sles15sp4:/srv/cortex/docs/configuration # 

[friedrichg]

you need to include alertmanager in target, it's not included in the 'all' target

# Comma-separated list of Cortex modules to load. The alias 'all' can be used in
# the list to load a number of core modules and will enable single-binary mode.
# Use '-modules' command line flag to get a list of available modules, and to
# see which modules are included in 'all'.
# CLI flag: -target
[target: <string> | default = "all"]

For example

target: alertmanager

and you need to enable experimental alertmanager api to use cortex-tools

# Enable the experimental alertmanager config api.
# CLI flag: -experimental.alertmanager.enable-api
[enable_api: <boolean> | default = false]

And the port you seem to be using is 9009 so the command should be

cortextool alertmanager load /root/alertmanager.yml --id fake --address http://localhost:9009