You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Timothee Maret (JIRA)" <ji...@apache.org> on 2019/05/28 19:43:00 UTC

[jira] [Commented] (SLING-8443) Simplify journal_available metric

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

Timothee Maret commented on SLING-8443:
---------------------------------------

Thanks [~cschneider]! Merged your PR.

> Simplify journal_available metric
> ---------------------------------
>
>                 Key: SLING-8443
>                 URL: https://issues.apache.org/jira/browse/SLING-8443
>             Project: Sling
>          Issue Type: Improvement
>          Components: Content Distribution
>    Affects Versions: Content Distribution Journal Core 0.1.0
>            Reporter: Christian Schneider
>            Assignee: Timothee Maret
>            Priority: Major
>             Fix For: Content Distribution Journal Core 0.1.2
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current implementation creates a Gauge service "by hand" using the OSGi API. It also uses the marker service to detect the journal availability which requires an optional dynamic service reference.
> I propose to change this to a DS component and uses a simple reference to JournalAvailableChecker which is in the same package anyway.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)