You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/04/14 13:27:00 UTC
[jira] [Resolved] (SLING-5410) Identify component where important Metrics can be collected
[ https://issues.apache.org/jira/browse/SLING-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-5410.
-------------------------------------
Resolution: Won't Fix
> Identify component where important Metrics can be collected
> -----------------------------------------------------------
>
> Key: SLING-5410
> URL: https://issues.apache.org/jira/browse/SLING-5410
> Project: Sling
> Issue Type: Task
> Components: Engine
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Major
>
> With SLING-4080 we now have support for collecting various kinds of metrics in performant way.
> As a next step we would need to identify those parts of Sling engine and request processing logic where we can collect important metrics. Such metric should help
> # Sling system administrator to monitor key aspects of Sling
> # Allow us as developers to get insight into critical parts and help in doing further optimization
> Once identified we can then add required metric collection logic to those parts
--
This message was sent by Atlassian Jira
(v8.20.10#820010)