Недостающие очереди от RabbitMQ Metricbeat - PullRequest
0 голосов
/ 25 июня 2019

Похоже, что только небольшая часть очередей в моем кластере RabbitMQ переходит в Elasticsearch через Metricbeat.

Когда я запрашиваю RabbitMQ /api/overview, я вижу 887 очередей:

object_totals: {
consumers: 517,
queues: 887,
exchanges: 197,
connections: 305,
channels: 622
},

Когда я запрашиваю у RabbitMQ /api/queues (что и происходит с Metricbeat), я также считаю 887 очередей.

Когда я получаю уникальный счет поля rabbitmq.queue.name в Elasticsearch, я вижу только 309 очередей.


Я не вижу ничего в выводе отладки, который выделялся бы мне. Это просто обычные сообщения запуска уровня INFO, за которыми следует информация публикации:

root@rabbitmq:/etc/metricbeat# metricbeat -e
2019-06-24T21:13:33.692Z    INFO    instance/beat.go:571    Home path: [/usr/share/metricbeat] Config path: [/etc/metricbeat] Data path: [/var/lib/metricbeat] Logs path: [/var/log/metricbeat]
2019-06-24T21:13:33.692Z    INFO    instance/beat.go:579    Beat ID: xxx
2019-06-24T21:13:33.692Z    INFO    [index-management.ilm]  ilm/ilm.go:129  Policy name: metricbeat-7.1.1
2019-06-24T21:13:33.692Z    INFO    [seccomp]   seccomp/seccomp.go:116  Syscall filter successfully installed
2019-06-24T21:13:33.692Z    INFO    [beat]  instance/beat.go:827    Beat info   {"system_info": {"beat": {"path": {"config": "/etc/metricbeat", "data": "/var/lib/metricbeat", "home": "/usr/share/metricbeat", "logs": "/var/log/metricbeat"}, "type": "metricbeat", "uuid": "xxx"}}}
2019-06-24T21:13:33.692Z    INFO    [beat]  instance/beat.go:836    Build info  {"system_info": {"build": {"commit": "3358d9a5a09e3c6709a2d3aaafde628ea34e8419", "libbeat": "7.1.1", "time": "2019-05-23T13:23:10.000Z", "version": "7.1.1"}}}
2019-06-24T21:13:33.692Z    INFO    [beat]  instance/beat.go:839    Go runtime info {"system_info": {"go": {"os":"linux","arch":"amd64","max_procs":4,"version":"go1.11.5"}}}
[...]
2019-06-24T21:13:33.694Z    INFO    [beat]  instance/beat.go:872    Process info    {"system_info": {"process": {"capabilities": {"inheritable":null,"permitted":["chown","dac_override","dac_read_search","fowner","fsetid","kill","setgid","setuid","setpcap","linux_immutable","net_bind_service","net_broadcast","net_admin","net_raw","ipc_lock","ipc_owner","sys_module","sys_rawio","sys_chroot","sys_ptrace","sys_pacct","sys_admin","sys_boot","sys_nice","sys_resource","sys_time","sys_tty_config","mknod","lease","audit_write","audit_control","setfcap","mac_override","mac_admin","syslog","wake_alarm","block_suspend","audit_read"],"effective":["chown","dac_override","dac_read_search","fowner","fsetid","kill","setgid","setuid","setpcap","linux_immutable","net_bind_service","net_broadcast","net_admin","net_raw","ipc_lock","ipc_owner","sys_module","sys_rawio","sys_chroot","sys_ptrace","sys_pacct","sys_admin","sys_boot","sys_nice","sys_resource","sys_time","sys_tty_config","mknod","lease","audit_write","audit_control","setfcap","mac_override","mac_admin","syslog","wake_alarm","block_suspend","audit_read"],"bounding":["chown","dac_override","dac_read_search","fowner","fsetid","kill","setgid","setuid","setpcap","linux_immutable","net_bind_service","net_broadcast","net_admin","net_raw","ipc_lock","ipc_owner","sys_module","sys_rawio","sys_chroot","sys_ptrace","sys_pacct","sys_admin","sys_boot","sys_nice","sys_resource","sys_time","sys_tty_config","mknod","lease","audit_write","audit_control","setfcap","mac_override","mac_admin","syslog","wake_alarm","block_suspend","audit_read"],"ambient":null}, "cwd": "/etc/metricbeat", "exe": "/usr/share/metricbeat/bin/metricbeat", "name": "metricbeat", "pid": 30898, "ppid": 30405, "seccomp": {"mode":"filter","no_new_privs":true}, "start_time": "2019-06-24T21:13:33.100Z"}}}
2019-06-24T21:13:33.694Z    INFO    instance/beat.go:280    Setup Beat: metricbeat; Version: 7.1.1
2019-06-24T21:13:33.694Z    INFO    [publisher] pipeline/module.go:97   Beat name: metricbeat
2019-06-24T21:13:33.694Z    INFO    instance/beat.go:391    metricbeat start running.
2019-06-24T21:13:33.694Z    INFO    cfgfile/reload.go:150   Config reloader started
2019-06-24T21:13:33.694Z    INFO    [monitoring]    log/log.go:117  Starting metrics logging every 30s
[...]
2019-06-24T21:13:43.696Z    INFO    filesystem/filesystem.go:57 Ignoring filesystem types: sysfs, rootfs, ramfs, bdev, proc, cpuset, cgroup, cgroup2, tmpfs, devtmpfs, configfs, debugfs, tracefs, securityfs, sockfs, dax, bpf, pipefs, hugetlbfs, devpts, ecryptfs, fuse, fusectl, pstore, mqueue, autofs
2019-06-24T21:13:43.696Z    INFO    fsstat/fsstat.go:59 Ignoring filesystem types: sysfs, rootfs, ramfs, bdev, proc, cpuset, cgroup, cgroup2, tmpfs, devtmpfs, configfs, debugfs, tracefs, securityfs, sockfs, dax, bpf, pipefs, hugetlbfs, devpts, ecryptfs, fuse, fusectl, pstore, mqueue, autofs
2019-06-24T21:13:44.696Z    INFO    pipeline/output.go:95   Connecting to backoff(async(tcp://xxx))
2019-06-24T21:13:44.711Z    INFO    pipeline/output.go:105  Connection to backoff(async(tcp://xxx)) established
2019-06-24T21:14:03.696Z    INFO    [monitoring]    log/log.go:144  Non-zero metrics in the last 30s    {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":130,"time":{"ms":131}},"total":{"ticks":1960,"time":{"ms":1965},"value":1960},"user":{"ticks":1830,"time":{"ms":1834}}},"handles":{"limit":{"hard":1048576,"soft":1024},"open":12},"info":{"ephemeral_id":"xxx","uptime":{"ms":30030}},"memstats":{"gc_next":30689808,"memory_alloc":21580680,"memory_total":428076400,"rss":79917056}},"libbeat":{"config":{"module":{"running":0},"reloads":2},"output":{"events":{"acked":7825,"batches":11,"total":7825},"read":{"bytes":66},"type":"logstash","write":{"bytes":870352}},"pipeline":{"clients":4,"events":{"active":313,"published":8138,"retry":523,"total":8138},"queue":{"acked":7825}}},"metricbeat":{"rabbitmq":{"connection":{"events":2987,"failures":10,"success":2977},"exchange":{"events":1970,"success":1970},"node":{"events":10,"success":10},"queue":{"events":3130,"failures":10,"success":3120}},"system":{"cpu":{"events":2,"success":2},"filesystem":{"events":7,"success":7},"fsstat":{"events":1,"success":1},"load":{"events":2,"success":2},"memory":{"events":2,"success":2},"network":{"events":4,"success":4},"process":{"events":18,"success":18},"process_summary":{"events":2,"success":2},"socket_summary":{"events":2,"success":2},"uptime":{"events":1,"success":1}}},"system":{"cpu":{"cores":4},"load":{"1":0.48,"15":0.28,"5":0.15,"norm":{"1":0.12,"15":0.07,"5":0.0375}}}}}}

Я думаю, что если возникла проблема с получением очереди, я должен увидеть ошибку в журналах выше согласно https://github.com/elastic/beats/blob/master/metricbeat/module/rabbitmq/queue/data.go#L94-L104

Вот metricbeat.yml:

metricbeat.config.modules:
  path: ${path.config}/modules.d/*.yml
  reload.enabled: true
  reload.period: 10s

setup.template.settings:
  index.number_of_shards: 1
  index.codec: best_compression

name: metricbeat

fields:
  environment: development

processors:
- add_cloud_metadata: ~

output.logstash:
  hosts: ["xxx"]

Вот modules.d/rabbitmq.yml:

- module: rabbitmq
  metricsets: ["node", "queue", "connection", "exchange"]
  enabled: true
  period: 2s
  hosts: ["xxx"]
  username: xxx
  password: xxx

1 Ответ

0 голосов
/ 29 июня 2019

Я решил это, обновив Elastic Stack с 7.1.1 до 7.2.0.

...