Introduced twTasks.processing.triggersLimit gauge to show how many triggers we can keep in memory for a bucket.

[onukristo]

Context

Introduced twTasks.processing.triggersLimit gauge to show how many triggers we can keep in memory for a bucket.

Checklist

• Change meets or does not compromise the Baseline Security Requirements

[Copilot]

Pull Request Overview

This PR introduces a new metrics gauge twTasks.processing.triggersLimit to expose the maximum number of triggers that can be kept in memory for each bucket. This adds observability to help monitor and understand the memory constraints for trigger processing.

• Added new gauge metric to track triggers limit per bucket
• Refactored bucket properties retrieval to avoid duplicate calls
• Updated version and changelog documentation

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
TasksProcessingService.java	Refactored bucket properties access and registered new triggers limit gauge
ICoreMetricsTemplate.java	Added interface method for registering triggers limit gauge
CoreMetricsTemplate.java	Implemented triggers limit gauge registration with metric constant
gradle.properties	Bumped version from 1.51.1 to 1.51.2
CHANGELOG.md	Added changelog entry for the new triggers limit gauge

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}