Are there any available options to identify a queue and retrieve its count?
Hey there @kindhearted-deer, thanks for posting. Please read the “Troubleshooting” and “How to Ask for Help” buttons below. If you would like a 1:1 support session from the KumoMTA team, details are at the “Book a Support Session” button below.
you can use kcli using queue summary
any other way. because i need to sych this data to clickhouse.
you can also use the /metrics endpoint
Both are great answers, thank you.
If you need that as a feed, you can look at the Prometheus integration too:
I want ip wise & domain wise queue count. checking with metrics endpoint , this is only provide domain wise queue. Is there any option to full fill my rquirement ? @faithful-ostrich @yearning-hyena
What is not adequate about the answers you received?
I require queue counts based on IP addresses, which differs from the current setup that provides counts based on tenants and domains.
Current Queue Counts by Tenant and Domain:
SCHEDULED QUEUE COUNT
pool-2@bulk.domain.io 59582
Show me your output from the /metrics.json endpoint and then tell me what it is lacking.
Because the kcli queue summary command has what you are asking:
kcli --endpoint http://127.0.0.1:8000 queue-summary
{
SITE SOURCE PROTO D T C Q
(alt1|alt2|alt3|alt4)?.gmail-smtp-in.l.google.com hdfc.s-ip102 smtp_client 0 0 5 995
(alt1|alt2|alt3|alt4)?.gmail-smtp-in.l.google.com hdfc.s-ip103 smtp_client 0 0 5 995
...
}
`[root@kumomta kumomta]# /opt/kumomta/sbin/kcli --endpoint http://127.0.0.1:8000 queue-summary
SITE SOURCE PROTO D T C Q
_dc-mx.4180b92c0e82.bulk.domain.io 146.10.100.10_1282 smtp_client 8795 0 165 995
_dc-mx.4180b92c0e82.bulk.domain.io unspecified smtp_client 1790 0 10 0
SCHEDULED QUEUE COUNT
pool-2@bulk.domain.io 64256 `
`[root@kumomta kumomta]# curl -i ‘http://localhost:8000/metrics.json’ -H 'Content-Type:
{“connection_count”:{“help”:“number of active connections”,“type”:“gauge”,“value”:{“service”:{“esmtp_listener”:0,“smtp_client”:176,“smtp_client:146.10.100.10_1282->_dc-mx.4180b92c0e82.bulk.domain.io@smtp_client”:166,“smtp_client:unspecified->_dc-mx.4180b92c0e82.bulk.domain.io@smtp_client”:10}}},“message_count”:{“help”:“total number of Message objects”,“type”:“gauge”,“value”:84236},“ready_count”:{“help”:“number of messages in the ready queue”,“type”:“gauge”,“value”:{“service”:{“smtp_client:146.10.100.10_1282->_dc-mx.4180b92c0e82.bulk.domain.io@smtp_client”:972,“smtp_client:unspecified->_dc-mx.4180b92c0e82.bulk.domain.io@smtp_client”:0}}},“scheduled_count”:{“help”:“number of messages in the scheduled queue”,“type”:“gauge”,“value”:{“queue”:{“pool-2@bulk.domain.io”:64256}}},“total_messages_delivered”:{“help”:“total number of messages ever delivered”,“type”:“counter”,“value”:{“service”:{“smtp_client”:10611,“smtp_client:146.10.100.10_1282->_dc-mx.4180b92c0e82.bulk.domain.io@smtp_client”:8819,“smtp_client:unspecified->_dc-mx.4180b92c0e82.bulk.domain.io@smtp_client”:1792}}},“total_messages_fail”:{“help”:“total number of message delivery attempts that permanently failed”,“type”:“counter”,“value”:{“service”:{“smtp_client”:0,“smtp_client:146.10.100.10_1282->_dc-mx.4180b92c0e82.bulk.domain.io@smtp_client”:0,“smtp_client:unspecified->_dc-mx.4180b92c0e82.bulk.domain.io@smtp_client”:0}}},“total_messages_transfail”:{“help”:“total number of message delivery attempts that transiently failed”,“type”:“counter”,“value”:{“service”:{“smtp_client”:0,“smtp_client:146.10.100.10_1282->_dc-mx.4180b92c0e82.bulk.domain.io@smtp_client”:0,“smtp_client:unspecified->_dc-mx.4180b92c0e82.bulk.domain.io@smtp_client”:0}}}}`
@yearning-hyena I need SCHEDULED QUEUE count . Not ready queue count
If you see the queue summary in the bottom there is a schedule queue you can check from that
I want ip wise & domain wise scheduled queue count. Current scheduled queue count is not ip wise
Messages in the scheduled queue are not queued by IP, so they cannot be reported by IP. IP only becomes a factor in the ready queue.
Ok