You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "complone (via GitHub)" <gi...@apache.org> on 2023/05/18 01:29:15 UTC
[GitHub] [rocketmq-eventbridge] complone opened a new issue, #104: feat: Definition of monitoring indicators
complone opened a new issue, #104:
URL: https://github.com/apache/rocketmq-eventbridge/issues/104
#### Background&Motivation
Due to the summary of the previous meetings, we have obtained the back pressure mechanism based on the PID algorithm in spark, and passed the test to deliver events through eventbus, so we need to define monitoring indicators and collect indicators based on opentelemry
#####What needs to be done
In the current startup process of rocketmq-eventbridge, when we start to set up a synchronization task and fill in the corresponding source..transform.sink, the task is always isolated with the identifier of runnerName, which means that we need to count the indicator dimensions Should use runnerName as label.
After starting the program, in the starting thread, there will be three threads executing in sequence (EventSubcuriber, EventBusListener, EventRuleTransfer, EventTargetPusher). If the user posts an event, I will explain the indicators we care about in the three threads one by one:
In the EventBusListener thread, because it is located at the most upstream of pulling messages, and according to the PID algorithm, it is necessary to calculate the oscillation formula for the downstream feedback indicators to control the backpressure effect under large traffic, so two key indicators need to be set:
- Calculate the number of consumed messages/s based on the number of elements in the blocking queue and the delay of each call to the poll method (time sampling from the start of EventSubcuriber)
- Take the runnerName as the unit, record the number of elements pushed to the downstream blocking queue, and the production time (calculate the sampling time from the start of the EventSubcuriber) to calculate the number of production messages/s
- The traffic fluctuation when the synchronization task event corresponding to each runnerName fails to retry (if the delay is too high, the number of retries needs to be adjusted)
In the EventRuleTransfer thread, due to subscribing to related event rules and needing to maintain the TransForm operation in each of the above task processing links, the user needs to know whether the operation is successful or failed, and the following indicators are defined:
- Calculate the delay of each transform operation when calling asynchronously
- Consume TPS from the upstream blocking queue, that is, the number of consumed messages/s
- Percentile delay when retrying in units of runnerName
- The TPS delivered to the downstream blocking queue, that is, the number of production messages/s
#####Why do this
##### What benefits are bred
#####How to achieve it
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-eventbridge] complone commented on issue #104: feat: Definition of monitoring indicators
Posted by "complone (via GitHub)" <gi...@apache.org>.
complone commented on issue #104:
URL: https://github.com/apache/rocketmq-eventbridge/issues/104#issuecomment-1553906535
Thank you very much for your reply! I will try my best to complete the design of the proposal and the related indicator definition form this week
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-eventbridge] Jashinck commented on issue #104: feat: Definition of monitoring indicators
Posted by "Jashinck (via GitHub)" <gi...@apache.org>.
Jashinck commented on issue #104:
URL: https://github.com/apache/rocketmq-eventbridge/issues/104#issuecomment-1552778888
>
MetricesName, eventbridge_eventrule_trigger_latency -> eventbridge_eventtarget_trigger_latency
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-eventbridge] complone commented on issue #104: feat: Definition of monitoring indicators
Posted by "complone (via GitHub)" <gi...@apache.org>.
complone commented on issue #104:
URL: https://github.com/apache/rocketmq-eventbridge/issues/104#issuecomment-1552294683
At present, due to work reasons, the proposal has not been completed, and I hope to give suggestions on this Friday
@2011shenlin @Jashinck
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-eventbridge] complone commented on issue #104: feat: Definition of monitoring indicators
Posted by "complone (via GitHub)" <gi...@apache.org>.
complone commented on issue #104:
URL: https://github.com/apache/rocketmq-eventbridge/issues/104#issuecomment-1553906646
> can refer to：
>
> The label of Metrics：
>
> account_id account ID
> name resource name
> source Source type
> target Target type
> status 0: failed，1: succeed
> Metrics details:
>
> Metrics Type Metrics Name Unit Desc Label
> counter eventbridge_eventbus_in_events_total count the event count of putted to event bus. account_id,name,status
> gauge eventbridge_eventrule_latency_seconds second the latency of event rule subscription account_id,name
> counter eventbridge_eventrule_filter_events_total count the event count of event rule filted account_id,name,status
> histogram eventbridge_eventrule_trigger_latency millisecond trigger target latency: le_100_ms,le_300_ms,le_500_ms,le_1_s,le_3_s,le_5_s,le_overflow account_id,name,status
Thank you very much for your reply! I will try my best to complete the design of the proposal and the related indicator definition form this week
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-eventbridge] 2011shenlin commented on issue #104: feat: Definition of monitoring indicators
Posted by "2011shenlin (via GitHub)" <gi...@apache.org>.
2011shenlin commented on issue #104:
URL: https://github.com/apache/rocketmq-eventbridge/issues/104#issuecomment-1552565611
The label of Metrics：
| account_id | account ID |
| --- | --- |
| name | resource name|
| source | Source type|
| target | Target type|
| status | 0: failed，1: succeed |
Metrics details:
| Metrics Type | Metrics Name | Unit | Desc | Label |
| --- | --- | --- | --- | --- |
| counter | eventbridge_eventbus_in_events_total | count | the event count of putted to event bus. | account_id,name,status |
| gauge | eventbridge_eventrule_latency_seconds (+) | second | the latency of event rule subscription| account_id,name |
| counter | eventbridge_eventrule_filter_events_total | count | the event count of event rule filted | account_id,name,status |
| histogram | eventbridge_eventrule_trigger_latency | millisecond | trigger target latency: le_100_ms,le_300_ms,le_500_ms,le_1_s,le_3_s,le_5_s,le_overflow | account_id,name,status |
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org