Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Caseflow Corp/VBMS Data Integration | AMO Bi-Weekly Reporting #12510

Closed
pkarman opened this issue Oct 30, 2019 · 3 comments · Fixed by #12629 or #13108
Closed

Caseflow Corp/VBMS Data Integration | AMO Bi-Weekly Reporting #12510

pkarman opened this issue Oct 30, 2019 · 3 comments · Fixed by #12629 or #13108
Assignees
@pkarman
Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-intake Team: Delta 🔺

Comments

@pkarman
Copy link
Contributor

pkarman commented Oct 30, 2019 •
edited by msj0nes
Loading

User story

As an AMO member, I need to improve accuracy in tracking and reporting claim data via a bi-weekly report reflecting Intake stats.

Acceptance criteria

  • A new cron job uses the ClaimReviewAsyncStatsReporter to send CSV output to the #caseflow-vbms-intake channel, similar to how MonthlyMetricsReportJob works.
  • Job should also report current number of stuck SC and HLR async jobs.

Goals

  • Improved user confidence in accuracy and comprehensiveness of records being viewed in Caseflow
  • Improved accuracy in tracking claim data
  • Improved accuracy in reporting claim data
@pkarman pkarman self-assigned this Nov 1, 2019
@pkarman pkarman mentioned this issue Nov 6, 2019
Merged
1 task
@jimruggiero jimruggiero added the Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. label Nov 12, 2019
va-bot pushed a commit that referenced this issue Nov 20, 2019
@pkarman
Add AMO metrics report (#12629)
d39a1c3 
Resolves #12510 

### Description
New report for AMO, sending related stats to the relevant Slack channel.

Refactors the existing monthly metrics tests to share example code, and fixes off-by-one date math. This SQL:

```sql
select * from supplemental_claims where establishment_submitted_at <= Time.zone.today
```
will treat "today" as "midnight" and skip everything up til `now()`. So we ask for "tomorrow (at midnight)" to include things that happened today.

### Documentation Updates
- [x] Topline File Descriptions Added or Updated as Needed
@pkarman
Copy link
Contributor Author

pkarman commented Nov 20, 2019

Still needs:

Job should also report current number of stuck SC and HLR async jobs.

@pkarman pkarman reopened this Nov 20, 2019
@pkarman
Copy link
Contributor Author

pkarman commented Dec 19, 2019

Relevant thread https://dsva.slack.com/archives/CFBLH2LR4/p1571861537093100

@pkarman pkarman mentioned this issue Jan 8, 2020
Merged
va-bot pushed a commit that referenced this issue Jan 10, 2020
@pkarman
AMO metrics job (#13108)
c8529a9 
Resolves #12510 

### Description
Adds AMO stats cron API entry.

Adds number of stuck jobs to report.

Background: https://dsva.slack.com/archives/CFBLH2LR4/p1578066110054800
@msj0nes msj0nes changed the title AMO bi-weekly intake numbers Caseflow Corp/VBMS Data Integration | AMO Bi-Weekly Reporting Feb 4, 2020
@msj0nes
Copy link

msj0nes commented Apr 10, 2020

Status

PI Planning Notes - Caseflow level work is complete via 'AMO metrics job' . OIT is working with BGS on anything additional that may be needed. New work will be addressed via new roadmap entry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pkarman pkarman

Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-intake Team: Delta 🔺
Projects
None yet
Milestone
No milestone
3 participants
@pkarman @msj0nes @jimruggiero