config.yaml

# Select which protocol to use in order to connect to the MQ
# mq: amqp/stomp

# If using amqp protocol
amqp:
  url: amqps://username:password@example.com/vhost
  exchange: shoveled-xrd
  topic:
  token_location: /etc/xrootd-monitoring-shoveler/token

# If using stomp protocol please configure the following commented lines as needed
#stomp:
#  user: username
#  password: password
#  url: messagebroker.org:port
#  topic: mytopic
#  cert: path/to/cert/file
#  certkey: path/to/certkey/file

listen:
  port: 9993
  ip: 0.0.0.0

# Where to foward udp messages, if necessary
# Multiple destinations supported
#outputs:
#  destinations:
#    - 127.0.0.1:1234

# Whether to verify the header of the packet matches XRootD's monitoring
# packet format
verify: true

# Export prometheus metrics
metrics:
  enable: true
  port: 8000

# Directory to store overflow of queue onto disk.
# The queue keeps 100 messages in memory.  If the shoveler is disconnected from the message bus,
# it will store messages over the 100 in memory onto disk into this directory.  Once the connection has been re-established
# the queue will be emptied.  The queue on disk is persistent between restarts, so a persistent directory should be used.
queue_directory: /var/spool/xrootd-monitoring-shoveler/queue

# Mapping configuration
# If map.all is set, all messages will be mapped to the configured origin.
# For example, with the configuration
# map:
#   all: 172.0.0.4
# If a packet comes in with the private ip address of 192.168.0.4, the packet origin will be changed to 172.0.0.4
# The port is always preserved.
# If you want multiple mappings, you can specify multiple map entries.
# For example, with the configuration
# map:
#   192.168.0.5: 172.0.0.5
#   192.168.0.6: 129.93.10.7