RabbitMqConsumer Monitoring
This section describes the types, names, and meanings of RabbitMqConsumer metrics collected by APM.
Category |
Metric |
Name |
Description |
Unit |
Data Type |
Default Aggregation Mode |
---|---|---|---|---|---|---|
Exception (exception: exception statistics of RabbitMqConsumer calls) |
exceptionType |
Exception Type |
Exception type |
- |
ENUM |
LAST |
causeType |
Exception Class |
Exception class |
- |
ENUM |
LAST |
|
count |
Count |
Number of times the exception has occurred |
- |
INT |
SUM |
|
message |
Exception Message |
Message returned when the exception has occurred |
- |
STRING |
LAST |
|
stackTrace |
Exception Stack |
Exception stack information |
- |
CLOB |
LAST |
|
Push-mode consumption monitoring (pushConsume: APM counts statistics about push-mode message consumption.) |
pushConsumeIdentifier |
Identifier |
Push-mode consumption identifier |
- |
ENUM |
LAST |
concurrentMax |
Max. Concurrency |
Maximum number of messages for concurrent consumption |
- |
INT |
MAX |
|
errorCount |
Errors |
Number of message consumption errors |
- |
INT |
SUM |
|
errorTraceId |
Error Trace ID |
ID of the trace that encounters an error in a collection period |
- |
STRING |
LAST |
|
invokeCount |
invokeCount |
Number of consumption call times |
- |
INT |
SUM |
|
consumedMsgCount |
consumedMsgCount |
Number of messages that have been consumed |
- |
INT |
SUM |
|
consumedBytes |
Bytes Consumed |
Number of bytes that have been consumed |
- |
INT |
SUM |
|
maxSingleMsgBytes |
Max. Bytes Consumed |
Maximum number of bytes consumed each time |
- |
INT |
MAX |
|
manualAckCount |
ACK Messages |
Number of ACK messages |
- |
INT |
SUM |
|
rejectCount |
Rejected Messages |
Number of rejected messages |
- |
INT |
SUM |
|
requeueCount |
Re-queued Messages |
Number of re-queued messages |
- |
INT |
SUM |
|
lastError |
Error Message |
Information about the error that has occurred during message consumption |
- |
STRING |
LAST |
|
maxTime |
Max. RT |
Maximum response time for consuming messages |
- |
INT |
MAX |
|
runningCount |
Ongoing Executions |
Number of messages that are being consumed at the time of collection |
- |
INT |
SUM |
|
slowTraceId |
Slow Trace ID |
ID of the slowest trace in a collection period |
- |
STRING |
LAST |
|
totalTime |
Total RT |
Total response time for consuming messages |
- |
INT |
SUM |
|
range1 |
0–10 ms |
Number of requests with 0–10 ms response time |
- |
INT |
SUM |
|
range2 |
10–100 ms |
Number of requests with 10–100 ms response time |
- |
INT |
SUM |
|
range3 |
100–200 ms |
Number of requests with 100–200 ms response time |
- |
INT |
SUM |
|
range4 |
200–1000 ms |
Number of requests with 200–1000 ms response time |
- |
INT |
SUM |
|
range5 |
1–10s |
Number of requests with 1–10s response time |
- |
INT |
SUM |
|
range6 |
> 10s |
Number of requests with response time longer than 10s |
- |
INT |
SUM |
|
unackedMsgCount |
Unacked Messages in Channel |
Number of unacknowledged messages in the channel |
- |
INT |
LAST |
|
Connection monitoring (connectionConsume: APM counts message consumption statistics by connection.) |
connection |
connection |
Consumer connection information |
- |
ENUM |
LAST |
connectionCount |
Current Connections |
Current number of connections |
- |
INT |
LAST |
|
channelCount |
Current Channels |
Current number of channels |
- |
INT |
LAST |
|
connectionCreated |
Created Connections |
Number of connections that have been created |
- |
INT |
SUM |
|
connectionClosed |
Destroyed Connections |
Number of connections that have been destroyed |
- |
INT |
SUM |
|
channelCreated |
Created Channels |
Number of channels that have been created |
- |
INT |
SUM |
|
channelClosed |
Destroyed Channels |
Number of channels that have been destroyed |
- |
INT |
SUM |
|
concurrentMax |
Max. Concurrency |
Maximum number of messages for concurrent consumption |
- |
INT |
MAX |
|
errorCount |
Errors |
Number of message consumption errors |
- |
INT |
SUM |
|
errorTraceId |
Error Trace ID |
ID of the trace that encounters an error in a collection period |
- |
STRING |
LAST |
|
invokeCount |
invokeCount |
Number of consumption call times |
- |
INT |
SUM |
|
consumedMsgCount |
consumedMsgCount |
Number of messages that have been consumed |
- |
INT |
SUM |
|
consumedBytes |
Bytes Consumed |
Number of bytes that have been consumed |
- |
INT |
SUM |
|
maxSingleMsgBytes |
Max. Bytes Consumed |
Maximum number of bytes consumed each time |
- |
INT |
MAX |
|
manualAckCount |
ACK Messages |
Number of ACK messages |
- |
INT |
SUM |
|
rejectCount |
Rejected Messages |
Number of rejected messages |
- |
INT |
SUM |
|
requeueCount |
Re-queued Messages |
Number of re-queued messages |
- |
INT |
SUM |
|
lastError |
Error Message |
Information about the error that has occurred during message consumption |
- |
STRING |
LAST |
|
maxTime |
Max. RT |
Maximum response time for consuming messages |
- |
INT |
MAX |
|
runningCount |
Ongoing Executions |
Number of messages that are being consumed at the time of collection |
- |
INT |
SUM |
|
slowTraceId |
Slow Trace ID |
ID of the slowest trace in a collection period |
- |
STRING |
LAST |
|
totalTime |
Total RT |
Total response time for consuming messages |
- |
INT |
SUM |
|
range1 |
0–10 ms |
Number of requests with 0–10 ms response time |
- |
INT |
SUM |
|
range2 |
10–100 ms |
Number of requests with 10–100 ms response time |
- |
INT |
SUM |
|
range3 |
100–200 ms |
Number of requests with 100–200 ms response time |
- |
INT |
SUM |
|
range4 |
200–1000 ms |
Number of requests with 200–1000 ms response time |
- |
INT |
SUM |
|
range5 |
1–10s |
Number of requests with 1–10s response time |
- |
INT |
SUM |
|
range6 |
> 10s |
Number of requests with response time longer than 10s |
- |
INT |
SUM |
|
unackedMsgCount |
Unacked Messages |
Number of messages that have not been acknowledged in a connection |
- |
INT |
LAST |
|
Total monitoring (total: APM counts message consumption statistics by client.) |
concurrentMax |
Max. Concurrency |
Maximum number of messages for concurrent consumption |
- |
INT |
MAX |
errorCount |
Errors |
Number of message consumption errors |
- |
INT |
SUM |
|
errorTraceId |
Error Trace ID |
ID of the trace that encounters an error in a collection period |
- |
STRING |
LAST |
|
invokeCount |
invokeCount |
Number of consumption call times |
- |
INT |
SUM |
|
consumedMsgCount |
consumedMsgCount |
Number of messages that have been consumed |
- |
INT |
SUM |
|
consumedBytes |
Bytes Consumed |
Number of bytes that have been consumed |
- |
INT |
SUM |
|
maxSingleMsgBytes |
Max. Bytes Consumed |
Maximum number of bytes consumed each time |
- |
INT |
MAX |
|
manualAckCount |
ACK messages |
Number of ACK messages |
- |
INT |
SUM |
|
rejectCount |
Rejected Messages |
Number of rejected messages |
- |
INT |
SUM |
|
requeueCount |
Re-queued Messages |
Number of re-queued messages |
- |
INT |
SUM |
|
lastError |
Error Message |
Information about the error that has occurred during message consumption |
- |
STRING |
LAST |
|
maxTime |
Max. RT |
Maximum response time for consuming messages |
- |
INT |
MAX |
|
runningCount |
Ongoing Executions |
Number of messages that are being consumed at the time of collection |
- |
INT |
SUM |
|
slowTraceId |
Slow Trace ID |
ID of the slowest trace in a collection period |
- |
STRING |
LAST |
|
totalTime |
Total RT |
Total response time for consuming messages |
- |
INT |
SUM |
|
range1 |
0–10 ms |
Number of requests with 0–10 ms response time |
- |
INT |
SUM |
|
range2 |
10–100 ms |
Number of requests with 10–100 ms response time |
- |
INT |
SUM |
|
range3 |
100–200 ms |
Number of requests with 100–200 ms response time |
- |
INT |
SUM |
|
range4 |
200–1000 ms |
Number of requests with 200–1000 ms response time |
- |
INT |
SUM |
|
range5 |
1–10s |
Number of requests with 1–10s response time |
- |
INT |
SUM |
|
range6 |
> 10s |
Number of requests with response time longer than 10s |
- |
INT |
SUM |
|
unackedMsgCount |
Unacked Messages |
Number of unacknowledged messages on the client |
- |
INT |
LAST |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot