[
https://issues.apache.org/jira/browse/ATLAS-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paresh Devalia updated ATLAS-4867:
----------------------------------
Description:
Metrics API : http://<>/api/atlas/admin/metrics
1. There is some information in the Metrics API response, which is not been
used like Count of the typeAndSubTypes, Active, deleted, Shell
Approach:
Identify time taken by the above counts
Take reading of metric api
Take reading of metric api without the above counts
!Screenshot from 2024-02-05 20-30-39.png!
was:
Metrics API : http://<>/api/atlas/admin/metrics
1. There is some information in the Metrics API response, which is not been
used like Count of the typeAndSubTypes, Active, deleted, Shell
Approach:
Identify time taken by the above counts
Take reading of metric api
Take reading of metric api without the above counts
!Screenshot from 2024-02-05 20-30-39.png!
2. Also we can get the total number of count of vertices and edges present in
graph
This helps in estimating the time on Reindexing Patch.
Also it may be helpful while debugging the escalations
Approach:
Embed this count in MetricUtil
Or
Create seperate API
h3.
> Improve Metrics API
> -------------------
>
> Key: ATLAS-4867
> URL: https://issues.apache.org/jira/browse/ATLAS-4867
> Project: Atlas
> Issue Type: Bug
> Components: atlas-intg
> Reporter: Paresh Devalia
> Assignee: Paresh Devalia
> Priority: Major
> Attachments: Screenshot from 2024-02-05 20-30-39.png
>
>
> Metrics API : http://<>/api/atlas/admin/metrics
> 1. There is some information in the Metrics API response, which is not been
> used like Count of the typeAndSubTypes, Active, deleted, Shell
> Approach:
> Identify time taken by the above counts
> Take reading of metric api
> Take reading of metric api without the above counts
> !Screenshot from 2024-02-05 20-30-39.png!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
