Observability, Alerting, and Automated Throttle Escalation [LOW] #1643

Activity

1. HayimShaul

   added this to the Q2/26 milestone on May 3, 2026
2. HayimShaul

   added

   security

   on May 3, 2026
3. HayimShaul

   added a parent issue on May 3, 2026

   • [EPIC] Security By Design #1206
4. SurbhiAgarwal1 commented on May 14, 2026

   

   SurbhiAgarwal1

   on May 14, 2026

   Contributor

   More actions

   Hi @HayimShaul, I would like to work on this issue.

   After reviewing the current metrics infrastructure and the Security By Design epic, my understanding is that the goal here is to introduce lightweight but extensible observability and automated defensive throttling around Signer and Verifier operations.

   Proposed approach:

   • Instrument Signer and Verifier service operations using the existing token/core/common/metrics infrastructure.

   • Capture metrics such as:

     • request/call rate
     • operation latency
     • success/error counts
     • cache hit/miss ratio
     • throttle escalation events

   • Introduce middleware/interceptor-style wrappers so instrumentation remains decoupled from business logic.

   • Add structured audit logging for:

     • caller identity/principal
     • operation type
     • timestamp
     • outcome/error
     • escalation/throttle action applied

   • Define configurable anomaly thresholds (burst rate, sustained error rate, excessive retries, etc.) through policy/configuration instead of hardcoded values.

   • Implement an initial automated escalation mechanism that can:

     • temporarily reduce quotas
     • apply cooldown windows
     • temporarily block abusive callers
     • emit alerting metrics/events for operators

   • Keep the escalation logic extensible so future integrations with external monitoring/alerting systems can be added without changing core service logic.

   I’ll first review the existing metrics abstractions and identify the best integration points before proposing concrete implementation changes.
5. adecaro

   modified the milestones: Q2/26, Q3/26 on Jun 2, 2026
6. AkramBitar

   added

   V1_Hight

   and removed

   V1_Hight

   on Jun 23, 2026
7. AkramBitar

   assigned

   HayimShaul

   on Jun 28, 2026
8. HayimShaul

   added 5 commits that reference this issue on Aug 4, 2026

   feat(identity): observe and escalate signature throttling

   ...

   This issue will close once commit d7f9b1b is merged into the 'main' branch.

   d7f9b1b

   feat(identity): observe and escalate signature throttling

   ...

   This issue will close once commit 746cbae is merged into the 'main' branch.

   746cbae

   feat(identity): observe and escalate signature throttling

   ...

   This issue will close once commit 2933b99 is merged into the 'main' branch.

   2933b99

   feat(identity): observe and escalate signature throttling

   ...

   This issue will close once commit c199202 is merged into the 'main' branch.

   c199202

   feat(identity): observe and escalate signature throttling

   ...

   This issue will close once commit 52bce9e is merged into the 'main' branch.

   52bce9e
9. HayimShaul

   added a commit that references this issue on Aug 18, 2026

   feat(identity): observe and escalate signature throttling

   ...

   This issue will close once commit 1e0b204 is merged into the 'main' branch.

   1e0b204
10. 17 remaining items

    Load more
11. Effi-S

    added a commit that references this issue on Sep 23, 2026

    feat(identity): observe and escalate signature throttling

    ...

    This issue will close once commit 19e6c3a is merged into the 'main' branch.

    19e6c3a
12. AkramBitar

    added a commit that references this issue on Sep 23, 2026

    feat(identity): observe and escalate signature throttling

    ...

    This issue will close once commit 4606958 is merged into the 'main' branch.

    4606958
13. Effi-S

    added 7 commits that reference this issue on Sep 23, 2026

    feat(identity): observe and escalate signature throttling

    ...

    This issue will close once commit 71159b4 is merged into the 'main' branch.

    71159b4

    feat(identity): observe and escalate signature throttling

    ...

    This issue will close once commit 3fcaf0f is merged into the 'main' branch.

    3fcaf0f

    feat(identity): observe and escalate signature throttling

    ...

    This issue will close once commit bd50b5b is merged into the 'main' branch.

    bd50b5b

    feat(identity): observe and escalate signature throttling

    ...

    This issue will close once commit 7c63f60 is merged into the 'main' branch.

    7c63f60

    feat(identity): observe and escalate signature throttling

    ...

    This issue will close once commit b89646f is merged into the 'main' branch.

    b89646f

    feat(identity): observe and escalate signature throttling

    ...

    This issue will close once commit 023c006 is merged into the 'main' branch.

    023c006

    feat(identity): observe and escalate signature throttling

    ...

    This issue will close once commit af111cb is merged into the 'main' branch.

    af111cb
14. Effi-S

    modified the milestones: Q3/26, Q4/26 on Oct 1, 2026
15. Effi-S

    linked a pull request that will close this issuefeat(identity): activate signature observability in drivers, with metrics and docs (3/3 of #2084) #2441on Oct 5, 2026
16. Effi-S

    linked a pull request that will close this issuefeat(identity): escalating signature-throttle policy and instrumentation seam (2/3 of #2084) #2440on Oct 5, 2026
17. Effi-S

    linked a pull request that will close this issuefeat(identity): rate-limiter buckets and signature-observation vocabulary (1/3 of #2084) #2439on Oct 5, 2026
18. Effi-S

    assigned

    SurbhiAgarwal1

    on Oct 21, 2026