feat(analytics): adding metric api for dispute analytics

[harsh-sharma-juspay]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

adding metric api for dispute analytics
Http Method: POST
URL Path /analytics/v1/metric/dispute

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Hit the URL given below and should get sample response mentioned in the comment

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable

[harsh-sharma-juspay]

Curl:

curl --location 'http://localhost:8080/analytics/v1/metrics/disputes' \
--header 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:121.0) Gecko/20100101 Firefox/121.0' \
--header 'Accept: */*' \
--header 'Accept-Language: en-US,en;q=0.5' \
--header 'Accept-Encoding: gzip, deflate, br' \
--header 'Referer: https://app.hyperswitch.io/' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiM2NhODdjNTUtYTI1YS00YjRmLWE3MWUtMjM4NzU1MTA5NDBlIiwibWVyY2hhbnRfaWQiOiJtZXJjaGFudF8xNzA4MDc1MjcyIiwicm9sZV9pZCI6Im9yZ19hZG1pbiIsImV4cCI6MTcwOTI3OTEzNiwib3JnX2lkIjoib3JnX0s2TkNFa0R1dHNqNUFuazJOVjl6In0.q1cSGvuJYnOrrVhkwtlKyrQL7alo706d4UYwokatvPY' \
--header 'api-key: hyperswitch' \
--header 'Connection: keep-alive' \
--data '[
    {
        "timeRange": {
            "startTime": "2024-02-17T18:30:00Z",
            "endTime": "2024-02-29T17:34:00Z"
        },
        "groupByNames": [
            "connector"
        ],
        "source": "BATCH",
        "metrics": [
            "dispute_status_metric",
            "total_amount_disputed",
            "total_dispute_lost_amount"
            
        ],
        "delta": true
    }
]'

[harsh-sharma-juspay]

{
    "queryData": [
        {
            "disputes_challenged": 0,
            "disputes_won": 1,
            "disputes_lost": 0,
            "total_amount_disputed": 1040,
            "total_dispute_lost_amount": null,
            "total_dispute": 1,
            "dispute_stage": null,
            "connector": "checkout",
            "time_range": {
                "start_time": "2024-02-17T18:30:00.000Z",
                "end_time": "2024-02-29T17:34:00.000Z"
            },
            "time_bucket": "2024-02-17 18:30:00"
        }
    ],
    "metaData": [
        {
            "current_time_range": {
                "start_time": "2024-02-17T18:30:00.000Z",
                "end_time": "2024-02-29T17:34:00.000Z"
            }
        }
    ]
}

[harsh-sharma-juspay]

[lsampras]

is this rate or count?
should it be challenged_count/total instead

[harsh-sharma-juspay]

it have total count as well so if rate have to be display FE can convert count to rate percentage

[lsampras]

rest looks good