<html>
<head>
<title>RabbitMQ Management HTTP Stats</title>
<style>
body { font: 12px Verdana,sans-serif; color: #444; padding: 8px 35px; }
td, th { font: 12px Verdana,sans-serif; color: #444; }
h1 { font-size: 2em; }
h2 { font-size: 1.5em; }
td.path { font-family: monospace; }
th { font-size 1em; font-weight: bold; }
table { border-collapse: collapse; }
table th, table td { vertical-align: top; border: 1px solid #bbb; padding: 5px; }
code { background: #ffa; }
pre { background: black; color: #0f0; padding: 10px; word-wrap: break-word;}
table pre { background: #ffa; color: black; }
</style>
</head>
<body>
<h1>RabbitMQ Management HTTP Stats</h1>
<h2>Introduction</h2>
<p>
Most of the GET requests you can issue to the HTTP API return
JSON objects with a large number of keys. While a few of these
keys represent things you set yourself in a PUT request or AMQP
command (e.g. queue durability or arguments), most of them
represent statistics to do with the object in question. This
page attempts to document them.
</p>
<p>
It should be read in conjunction with the manual page
for <code>rabbitmqctl</code> (see your installation if on Unix / Linux,
or <a href="http://www.rabbitmq.com/man/rabbitmqctl.1.man.html">the
RabbitMQ website</a> for the latest version). Any field which can
be returned by a command of the form <code>rabbitmqctl
list_<i>something</i></code> will also be returned in the
equivalent part of the HTTP API, so all those keys are not
documented here. However, the HTTP API also adds a lot of extra
fields which are not available in <code>rabbitmqctl</code>.
</p>
<h2>_details objects</h2>
<p>
Many fields represent a count of some kind: queue length,
messages acknowledged, bytes received and so on. Such absolute
counts returned by the HTTP API will often have a
corresponding <code>_details</code> object which offers
information on how this count has changed. So for example, from
a queue:
</p>
<pre> "messages": 123619,
"messages_details": {
"avg": 41206.333333333336,
"avg_rate": 1030.1583333333333,
"rate": 24723.8,
"samples": [
{
"sample": 123619,
"timestamp": 1400680560000
},
{
"sample": 0,
"timestamp": 1400680500000
},
{
"sample": 0,
"timestamp": 1400680440000
}
]
}</pre>
<p>
Here we have a <code>messages</code> count (the total messages
in the queue), with some additional data:
</p>
<table>
<tr>
<td><code>avg</code></td>
<td>
The average value for the requested time period (see below).
</td>
</tr>
<tr>
<td><code>avg_rate</code></td>
<td>
The average rate for the requested time period.
</td>
</tr>
<tr>
<td><code>rate</code></td>
<td>
How much the count has changed per second in the most recent
sampling interval.
</td>
</tr>
<tr>
<td><code>samples</code></td>
<td>
Snapshots showing how the value has changed over the
requested time period.
</td>
</tr>
</table>
<p>
<code>avg</code>, <code>avg_rate</code> and <code>samples</code>
will only appear if you request a specific time period by
appending query parameters to the URL. To do this you need to
set an age and an increment for the samples you want. The end of
the range returned will always correspond to the present.
</p>
<p>
Different types of data take different query parameters to
return samples, as in the following table. You can specify more
than one set of parameters if the resource you are requesting
can generate more than one type of sample (for example, queues
can return message rates and queue lengths).
</p>
<table>
<tr>
<td>Messages sent and received</td>
<td><code>msg_rates_age</code> / <code>msg_rates_incr</code></td>
</tr>
<tr>
<td>Bytes sent and received</td>
<td><code>data_rates_age</code> / <code>data_rates_incr</code>
</td>
</tr>
<tr>
<td>Queue lengths</td>
<td><code>lengths_age</code> / <code>lengths_incr</code></td>
</tr>
<tr>
<td>Node statistics (e.g. file descriptors, disk space free)</td>
<td><code>node_stats_age</code> / <code>node_stats_incr</code></td>
</tr>
</table>
<p>
For example,
appending <code>?lengths_age=3600&lengths_incr=60</code> will
return the last hour's data on queue lengths, with a sample for
every minute.
</p>
<h2>message_stats objects</h2>
<p>
Many objects (including queues, exchanges and channels) will
return counts of messages passing through them. These are
included in a <code>message_stats</code> object (which in turn
will contain <code>_details</code> objects for each count, as
described above).
</p>
<p>
These can contain:
</p>
<table>
<tr>
<td><code>publish</code></td>
<td>
Count of messages published.
</td>
</tr>
<tr>
<td><code>publish_in</code></td>
<td>
Count of messages published "in" to an exchange, i.e. not
taking account of routing.
</td>
</tr>
<tr>
<td><code>publish_out</code></td>
<td>
Count of messages published "out" of an exchange,
i.e. taking account of routing.
</td>
</tr>
<tr>
<td><code>confirm</code></td>
<td>
Count of messages confirmed.
</td>
</tr>
<tr>
<td><code>deliver</code></td>
<td>
Count of messages delivered in acknowledgement mode to consumers.
</td>
</tr>
<tr>
<td><code>deliver_noack</code></td>
<td>
Count of messages delivered in no-acknowledgement mode to consumers.
</td>
</tr>
<tr>
<td><code>get</code></td>
<td>
Count of messages delivered in acknowledgement mode in
response to basic.get.
</td>
</tr>
<tr>
<td><code>get_noack</code></td>
<td>
Count of messages delivered in no-acknowledgement mode in
response to basic.get.
</td>
</tr>
<tr>
<td><code>deliver_get</code></td>
<td>
Sum of all four of the above.
</td>
</tr>
<tr>
<td><code>redeliver</code></td>
<td>
Count of subset of messages in <code>deliver_get</code>
which had the redelivered flag set.
</td>
</tr>
<tr>
<td><code>return</code></td>
<td>
Count of messages returned to publisher as unroutable.
</td>
</tr>
</table>
<p>
Only fields for which some activity has taken place will appear.
</p>
<h2>Detailed message stats objects</h2>
<p>
In addition, queues, exchanges and channels can return a
breakdown of message stats for each of their neighbours
(i.e. adjacent objects in the chain: channel -> exchange ->
queue -> channel). This will only happen if
the <code>rates_mode</code> configuration item has been switched
to <code>detailed</code> from its default of <code>basic</code>.
</p>
<p>
As this possibly constitutes a large quantity of data, it is also
only returned when querying a single channel, queue or exchange
rather than a list. Note also that the default sample retention
policy means that these detailed message st
rabbitmq-server-mac-standalone-3.5.7.tar.gz
3星 · 超过75%的资源 需积分: 31 40 浏览量
2015-12-19
16:37:24
上传
评论
收藏 16.68MB GZ 举报 
rabbitmq-server-mac-standalone-3.5.7.tar.gz （1036个子文件） 
rabbit.app 7KB inets.app 3KB kernel.app 3KB stdlib.app 2KB rabbitmq_management.app 2KB sasl.app 2KB ssl.app 1KB os_mon.app 1KB mnesia.app 1KB rabbitmq_federation.app 1KB rabbitmq_auth_backend_ldap.app 1KB cowboy.app 1KB rabbitmq_amqp1_0.app 1KB crypto.app 945B rabbitmq_mqtt.app 932B amqp_client.app 920B rabbitmq_shovel.app 903B rabbitmq_stomp.app 850B xmerl.app 780B rabbitmq_tracing.app 741B rabbitmq_web_dispatch.app 567B rabbitmq_web_stomp.app 512B public_key.app 471B rabbitmq_auth_mechanism_ssl.app 443B rabbitmq_web_stomp_examples.app 442B rabbitmq_management_agent.app 430B asn1.app 317B rabbitmq_federation_management.app 309B rabbitmq_management_visualiser.app 300B rabbitmq_consistent_hash_exchange.app 298B webmachine.app 288B eldap.app 268B rabbitmq_shovel_management.app 267B mochiweb.app 252B sockjs.app 249B rabbitmq_test.app 192B beam 2.92MB OTP-PUB-KEY.beam 511KB erl_parse.beam 292KB xmerl_xsd.beam 224KB xmerl_scan.beam 208KB erl_lint.beam 174KB qlc.beam 150KB qlc_pt.beam 136KB xmerl_sax_parser_latin1.beam 135KB xmerl_sax_parser_utf8.beam 135KB xmerl_sax_parser_utf16le.beam 135KB xmerl_sax_parser_utf16be.beam 135KB xmerl_sax_parser_list.beam 129KB mnesia_schema.beam 125KB dets.beam 119KB mochiweb_charref.beam 115KB dets_v9.beam 112KB sofs.beam 99KB mnesia.beam 99KB rabbit_channel.beam 85KB mnesia_tm.beam 84KB lists.beam 83KB rabbit_variable_queue.beam 83KB disk_log.beam 82KB rabbit_framing_amqp_0_8.beam 82KB ELDAPv3.beam 81KB systools_make.beam 81KB ssl_connection.beam 81KB ssl_handshake.beam 79KB PKCS-FRAME.beam 74KB mnesia_controller.beam 74KB ftp.beam 74KB release_handler.beam 71KB rabbit_msg_store.beam 71KB httpc_handler.beam 69KB file_sorter.beam 68KB xmerl_xpath_parse.beam 68KB global.beam 68KB application_controller.beam 66KB rabbit_amqqueue_process.beam 65KB xmerl_xsd_type.beam 63KB zip.beam 62KB erl_eval.beam 62KB erl_scan.beam 62KB shell.beam 62KB rabbit_reader.beam 62KB tftp_engine.beam 61KB epp.beam 61KB code_server.beam 61KB dets_v8.beam 60KB rabbit_framing_amqp_0_9_1.beam 59KB crypto.beam 59KB dets_utils.beam 59KB disk_log_1.beam 59KB file_handle_cache.beam 57KB rabbit_mgmt_db.beam 55KB inet_db.beam 55KB erl_pp.beam 55KB inet.beam 55KB ssl.beam 54KB mnesia_frag.beam 54KB rabbit_misc.beam 54KB ssl_cipher.beam 54KB ets.beam 53KB共 1036 条
- 1
- 2
- 3
- 4
- 5
- 6
- 11
资源评论
Y-v-Y2019-09-24安装顺利，使用正常
yang_guanghua2017-03-13可以使用额
tomas家的小拨浪鼓
- 粉丝: 8
- 资源: 38
