Burial | Clarify submission logging and monitors

[wayne-weibel]

Issue Description

clarify existing logs to specify info vs error, correct payload (claim_id, user_account_uuid, class name, etc), and update Burials DataDog dashboard

---

Tasks

• [ ] use existing logging examples to clarify Burial submission logging

Acceptance Criteria

• [ ] logs will indicate its type - info vs error
• [ ] logs will contain necessary payload for identifying and debugging a specific submission

• [ ] datadog monitors will be updated (or added) to monitor these logs

[mjknight50]

A good example of this is the inconsistency of how we log errors e.g. Logging:

• Burials —> raise Common::Exceptions::ValidationErrors, claim
• Pension —> raise Common::Exceptions::ValidationErrors, claim.errors

Also, logging when jobs are started, attempted, and thrown.

[mjknight50]

Hold this one back until https://github.com/department-of-veterans-affairs/va.gov-team/issues/90177 is completed.

[matt4su]

@balexandr - Is this work covered by ticket #91824? Might be a dupe?

[balexandr]

@matt4su I think its worth going through to compare between pensions and burials per Matt's inconsistency above

[wayne-weibel]

@balexandr does the work being done here make #90212 a duplicate?

[balexandr]

@wayne-weibel The work done under this ticket has been strictly in DD. No code changes.

[wayne-weibel]

This is looking good. A few more widgets to add though (can crib from pension)

The important one is:

These are helpful for reporting

[balexandr]

@wayne-weibel They've all been added and updated for Burial