Lightweight Message Queue (formerly MNS) menyediakan serangkaian metrik baru yang menawarkan data lebih terperinci serta metrik tambahan untuk meningkatkan kemampuan troubleshooting. Layanan ini terintegrasi dengan arsitektur Cloud Monitor terbaru guna memastikan data real-time dan akurat demi pengalaman pemantauan yang lebih efisien dan nyaman.
Usage
-
Metrik baru tersedia di wilayah China (Zhangjiakou), China (Chengdu), Korea Selatan (Seoul), dan Thailand (Bangkok). Dukungan untuk wilayah lain akan ditambahkan secara bertahap.
-
Di Cloud Monitor console, pilih untuk membuat aturan alert baru. Titik masuk sebelumnya, Message Service - Queue dan Message Service - Topic, telah dinonaktifkan.
PeringatanAturan alert yang bergantung pada metrik Cloud Monitor lama akan menjadi tidak valid. Untuk mencegah celah pemantauan, Anda harus segera membuat ulang aturan alert di titik masuk baru (Middleware > Lightweight Message Queue (formerly MNS)).
Metrics
Metrik AgeOfOldestMessage (message accumulation delay) dan NumberOfMessagesInvisible (number of invisible messages) untuk sementara tidak tersedia di wilayah berikut: China (Beijing), China (Hangzhou), China (Shanghai), China (Shenzhen), Singapura, dan UEA (Dubai). Hal ini juga berlaku untuk wilayah China East 2 (Shanghai) Finance, China South 1 (Shenzhen) Finance, dan China North 2 (Beijing) Gov 1.
|
Category |
Metric |
MetricName |
Unit |
|
User |
Maximum API QPS |
MaxApiQpsPerUser |
count/s |
|
API QPS usage |
WatermarkOfApiQps |
% |
|
|
Maximum console API QPS |
MaxConsoleApiQpsPerUser |
count/s |
|
|
Console API QPS usage |
WatermarkOfConsoleApiQps |
% |
|
|
Queue |
Message accumulation delay |
AgeOfOldestMessage |
ms |
|
Number of scheduled messages |
NumberOfMessagesDelayed |
count |
|
|
Number of visible messages |
NumberOfMessagesVisible |
count |
|
|
Number of invisible messages |
NumberOfMessagesInvisible |
count |
|
|
Number of Send API calls |
NumberOfSendAPICalls |
count |
|
|
Number of Receive API calls |
NumberOfReceiveAPICalls |
count |
|
|
Number of empty Receive API calls Catatan
Metrik ini mengukur jumlah panggilan Receive API yang tidak mengembalikan pesan. Anda dapat mengonfigurasi long polling untuk mengurangi jumlah permintaan dan menekan biaya. |
NumberOfEmptyReceives |
count |
|
|
Number of Delete API calls |
NumberOfDeleteAPICalls |
count |
|
|
Number of ChangeMessageVisibility API calls |
NumberOfChangeMessageVisibilityAPICalls |
count |
|
|
Number of BatchSend API calls |
NumberOfBatchSendAPICalls |
count |
|
|
Number of BatchReceive API calls |
NumberOfBatchReceiveAPICalls |
count |
|
|
Number of BatchDelete API calls |
NumberOfBatchDeleteAPICalls |
count |
|
|
Topic |
Number of publish requests per minute |
NumberOfPublishAPICallsPerTopic |
count |
|
Subscription |
Number of pushes per subscription |
NumberOfPushPerSubscription |
count |
|
Subscription processing success rate |
ProcessSuccessRatePerSubscription |
% |
|
|
Age of the oldest message in a subscription |
AgeOfOldestVisibleMessagePerSubscription |
ms |
|
|
Number of accumulated messages in a subscription |
NumberOfMessagesVisiblePerSubscription |
count |
Metric differences
Navigation
-
Metrik lama: Di Cloud Monitor console, metrik tersebut berada di bawah .
-
Metrik baru: Di Cloud Monitor console, pilih .
Metrics
|
Category |
New Cloud Monitor |
Old Cloud Monitor |
||
|
Metric |
MetricName |
Metric |
MetricName |
|
|
Queue |
Number of visible messages |
NumberOfMessagesVisible Minimum period: 60s |
Number of active messages |
ActiveMessages Minimum period: 300s |
|
Number of scheduled messages |
NumberOfMessagesDelayed Minimum period: 60s |
Delayed messages |
DelayMessages Minimum period: 300s |
|
|
Number of invisible messages |
NumberOfMessagesInvisible Minimum period: 60s |
Number of inactive messages |
InactiveMessages Minimum period: 300s |
|
|
Number of Send API calls |
NumberOfSendAPICalls |
Send message requests |
SendMessageCount |
|
|
Number of BatchSend API calls |
NumberOfBatchSendAPICalls |
Batch send message requests |
BatchSendMessageCount |
|
|
Number of Receive API calls |
NumberOfReceiveAPICalls |
Receive message requests |
ReceiveMessageCount |
|
|
Number of BatchReceive API calls |
NumberOfBatchReceiveAPICalls |
Batch receive message requests |
BatchReceiveMessageCount |
|
|
Number of Delete API calls |
NumberOfDeleteAPICalls |
Delete message requests |
DeleteMessageCount |
|
|
Number of BatchDelete API calls |
NumberOfBatchDeleteAPICalls |
Batch delete message requests |
BatchDeleteMessageCount |
|
|
Number of ChangeMessageVisibility API calls |
NumberOfChangeMessageVisibilityAPICalls |
Message visibility modifications |
ChangeMessageVisibilityCount |
|
|
Number of empty Receive API calls |
NumberOfEmptyReceives |
N/A |
||
|
Topic |
Number of publish requests per minute |
NumberOfPublishAPICallsPerTopic |
N/A |
|
|
Number of pushes |
N/A. Use the "Number of pushes per subscription" metric instead. |
Number of pushes |
TopicCountNew |
|
|
Push success rate (%) |
N/A. Use the "Subscription processing success rate" metric instead. |
Push success rate (%) |
TopicSuccessRateNew |
|
|
Subscription |
Number of pushes per subscription |
NumberOfPushPerSubscription You can view and monitor this metric at the subscription level. |
N/A |
|
|
Subscription processing success rate |
ProcessSuccessRatePerSubscription You can view and monitor this metric at the subscription level. |
N/A |
||
|
Age of the oldest message in a subscription |
AgeOfOldestVisibleMessagePerSubscription |
N/A |
||
|
Number of accumulated messages in a subscription |
NumberOfMessagesVisiblePerSubscription |
N/A |
||
|
User |
Maximum API QPS |
MaxApiQpsPerUser |
N/A |
|
|
API QPS usage |
WatermarkOfApiQps |
N/A |
||
|
Maximum console API QPS |
MaxConsoleApiQpsPerUser |
N/A |
||
|
Console API QPS usage |
WatermarkOfConsoleApiQps |
N/A |
||
Billing
Fitur Cloud Monitor untuk Lightweight Message Queue (formerly MNS) tidak dikenai biaya.
View metrics
Masuk ke Simple Message Queue (formerly MNS) console. Di panel navigasi kiri, klik Cloud Monitor.
Di bilah navigasi atas, pilih wilayah, seperti China (Hangzhou).
Di halaman Cloud Monitor, pilih resource dan rentang waktu untuk kueri.
Create an alert rule
Buka halaman detail queue atau topic target, lalu klik tab Cloud Monitor.
Di halaman Cloud Monitor, klik Create Alert Rule.
Panel Create Alert Rule di Cloud Monitor console akan muncul.
Di panel Create Alert Rule, konfigurasikan aturan dan pengaturan notifikasi, lalu klik OK. Untuk informasi tentang parameter, lihat Create an alert rule.