failure-exporter limited to only 50 results

[rmarting]

Testing the integration with Jira Atlassian I found that exporter is limited to only 50 results.

Checking the log of failure-exporter pod you could see that the Query API endpoint add variables to limit the maximum number of results:

---> Running application from Python script (failure/app.py) ...
Initializing Logger wit LogLevel: DEBUG
07-15-2021 13:31:00 INFO     ===== Starting Failure Collector =====
07-15-2021 13:31:00 INFO     Server: https://****************
07-15-2021 13:31:00 INFO     User: **************************
07-15-2021 13:31:00 DEBUG    Starting new HTTPS connection (1): ****************:443
07-15-2021 13:31:00 DEBUG    https://****************:443 "GET /rest/api/2/serverInfo HTTP/1.1" 200 None
07-15-2021 13:31:01 DEBUG    https://****************:443 "GET /rest/api/2/field HTTP/1.1" 200 None
07-15-2021 13:31:01 DEBUG    Starting new HTTPS connection (1): ****************:443
07-15-2021 13:31:01 DEBUG    https://****************:443 "GET /rest/api/2/serverInfo HTTP/1.1" 200 None
07-15-2021 13:31:01 DEBUG    https://****************:443 "GET /rest/api/2/field HTTP/1.1" 200 None
07-15-2021 13:31:04 DEBUG    https://****************:443 "GET /rest/api/2/search?jql=type%3Dbug+and+priority%3Dhighest&startAt=0&validateQuery=True&maxResults=50 HTTP/1.1" 200 None

The number of issues found is limite to only 50 entries, but my Jira instance manages hundred of projects with thousands of issues. In my case, the issues that I want to match in Pelorus do not appear in the results, so the Failure Rate metric is not updated for my use case.

How could I set up that value? It could be great to allow to setup the maximum number of issues, or at least execute that query for each project created in Jira. Other idea could be allow to set up the projects in Jira to extract metrics.

Maybe adding some properties in the deployment such as:

• MAX_RESULTS: Maximun number of results to query
• PROJECT: Literal or expression to define which projects in Jira should be checked to get metrics.

[etsauer]

hi @rmarting yes this definitely looks like a bug to me. It appears that at one point we did add an optional PROJECT propery, but we never implemented it. https://github.com/konveyor/pelorus/blob/master/exporters/failure/app.py#L31

[rmarting]

@etsauer I took some time to create a PR that could improve this issue in a simple way. I am not an python expert developer, however I think this first approach could resolve it. For my use case, it is working as expected and my Pelorus platform is getting the failure rates for the projects wanted.

HTH.

[KevinMGranger]

#308 adds support for PROJECTS, but we'll keep this open until the limit is fixed.

[kpiwko]

I'm not familiar with JIRA client in Python, however MAX_RESULTS would not be a proper fix as this number is limited by JIRA API itself. Some kind of implementation of paging based on ResultList would be needed.