You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Vikas Kumar (Jira)" <ji...@apache.org> on 2025/01/05 16:00:00 UTC

[jira] [Assigned] (RANGER-2233) KMS API - add monitoring endpoints /status, /metrics

     [ https://issues.apache.org/jira/browse/RANGER-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikas Kumar reassigned RANGER-2233:
-----------------------------------

    Assignee: Vikas Kumar

> KMS API - add monitoring endpoints /status, /metrics
> ----------------------------------------------------
>
>                 Key: RANGER-2233
>                 URL: https://issues.apache.org/jira/browse/RANGER-2233
>             Project: Ranger
>          Issue Type: New Feature
>          Components: kms
>    Affects Versions: 1.1.0
>            Reporter: Hari Sekhon
>            Assignee: Vikas Kumar
>            Priority: Major
>
> Ranger KMS API needs to add monitoring API endpoints such as /status that shouldn't require a super keyadmin credential. In fact if it was read-only anonymous would probably be fine.
>  
> The current API documented here only concerns itself with keys and doesn't address operational management:
> [http://ranger.apache.org/kms/apidocs/index.html]
>  
> The /status endpoint and similar should do as comprehensive as check of the health of the Ranger KMS as possible. In one example, /var/log/ filling up stops KMS working, and this should be detected with /status giving a status field showing bad health.
> /metrics could also be added around the number of operations tried, succeeded, failed, number of keys etc.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)