[
https://issues.apache.org/jira/browse/SLING-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125354#comment-17125354
]
Timothee Maret edited comment on SLING-9389 at 6/3/20, 10:01 PM:
-----------------------------------------------------------------
bq. The idea is to capture a metric (using Sling Metrics) exposing the end to
end distribution behavior (AEM to BP in this context).
[~harshchiki] I think we should do exactly what your requirement describes: add
Sling metrics in the implementations to monitor end to end latency. I think
that we could achieve that without extending the event API.
It's possible to dissociate metrics by agent, use case, etc. See for instance
the
[Bookeeper|https://github.com/apache/sling-org-apache-sling-distribution-journal/blob/4190c2befc6da8277e12ba019b8c41087cb217e1/src/main/java/org/apache/sling/distribution/journal/impl/subscriber/BookKeeper.java#L114-L115]
which emits metrics by subscriber agent.
bq. the information would not come down to the consumers of SCD apparently.
It would come via the Sling metrics rather than the SCD API. Would that be
satisfactory for your use case ?
was (Author: marett):
bq. The idea is to capture a metric (using Sling Metrics) exposing the end to
end distribution behavior (AEM to BP in this context).
[~harshchiki] I think we should do exactly what your requirement describes: add
Sling metrics in the implementations to monitor end to end latency. I think
that we could achieve that without extending the event API.
It's possible to dissociate metrics by agent, use case, etc. See for instance
the
[Bookeeper|https://github.com/apache/sling-org-apache-sling-distribution-journal/blob/4190c2befc6da8277e12ba019b8c41087cb217e1/src/main/java/org/apache/sling/distribution/journal/impl/subscriber/BookKeeper.java#L114-L115]
which emits metrics by subscriber agent.
bq. the information would not come down to the consumers of SCD apparently.
It would come via the Sling metrics rather than the SCD API. Would that be
satisfactory for your use case ?
> 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: 1h 40m
> 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)
