[ 
https://issues.apache.org/jira/browse/SLING-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107005#comment-17107005
 ] 

Harsh Chiki commented on SLING-9389:
------------------------------------

[~marett], 

thanks for looking into it.

 

> Is it correct that your requirement is to measure the end to end distribution 
>latency for each package on the source service (author) ?
Yes.

 

> If so, could you also clarify if it's a requirement for you to have the 
>information in the event, or if you could not have the information exposed as 
>a metric.


 * The idea is to capture a metric (using Sling Metrics) exposing the end to 
end distribution behavior (AEM to BP in this context).
 * IIUC if the information is captured within SCD as a metric (if that is the 
other option you are putting on the table) - the information would not come 
down to the consumers of SCD apparently. 
 ** Since our scenario is AEM to BP publish - we wanted to essentially monitor 
the distribution from AEM to BP - end to end.
 ** Nothing wrong (in fact likely good to capture metrics in SCD), I am afraid 
if there are multiple Distribution Agents (and flows) the statistics would get 
skewed. It will be difficult (I guess impossible) to figure out the metrics per 
flow (AEM to BP as in this case). Do you think this problem stands true, and if 
we have a solution?



 

Please let us know.

 

\cc: [~ashishc], [~shgu...@adobe.com]

> Distribution Event Packages should contain queue item creation time
> -------------------------------------------------------------------
>
>                 Key: SLING-9389
>                 URL: https://issues.apache.org/jira/browse/SLING-9389
>             Project: Sling
>          Issue Type: Improvement
>          Components: Content Distribution
>            Reporter: Harsh Chiki
>            Assignee: Timothee Maret
>            Priority: Major
>         Attachments: image-2020-04-30-10-28-58-011.png, scdapi.patch, 
> scdcore.patch
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Currently the Distribution Event package contains the following details:
>  * Distribution Component Name
>  * Distribution Component Kind
>  * Distribution Type
>  * Distribution Paths
>  
> Improvement aims at adding the queue item creation time, essentially when the 
> the item was creation for the first time, and enqueue into the queue. The 
> value does not change over retries (on failure).
>  
> The purpose to get this detail is to be able to capture metrics at the 
> consumer level. The consumers could have an event handler, which can capture 
> the duration which turns out to be (NOW MINUS queue item creation time thrown 
> in the distribution event package); NOW being the current time in the event 
> handler (consumer).
>  
> \cc: [~shgu...@adobe.com], [~ashishc]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to