[SLING-5410] Identify component where important Metrics can be collected

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: Engine
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 07/Jan/16 10:31
• Updated: 14/Apr/23 13:26
• Resolved: 14/Apr/23 13:26

Description

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

1. Sling system administrator to monitor key aspects of Sling
2. 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

Issue Links

• relates to: SLING-4080 API to capture/measure application-level metrics
• relates to: SLING-6735 Metric Count Authenticated and Anonymous Request
• relates to: SLING-6729 Metrik mark ResourceTypes
• relates to: SLING-6730 Metrik Time Sling needs to get a Resource
• relates to: SLING-6731 Metric increment counter when no resource is found
• relates to: SLING-6732 Metric Request per Second Sling has to handle
• relates to: SLING-6733 Metric duration of a request
• relates to: SLING-6734 Metrics create a Histogram of all filters
• relates to: SLING-6736 Metrics mark and count HTTP-Responses