Make it easier to review status of all outbound pushes

[michaelkohn]

As a system admin, I would like to be able to monitor outbound push tasks from the web app so that I don’t have to dig through logs.

Right now, unprocessed and failed task:outbound:.. docs can be found in the medic-sentinel database. For failed tasks, you have to search in the log files to try to figure out the issue. If the task was successful, you have to look for mark_for_outbound on the correspondinginfo doc.

It would be very useful to be able to view a history of outbound tasks from the web app. This could be a new page in the admin section that has a tab for unprocessed and failed tasks, and a separate tab for successful outbound tasks (or just one page with a filter). Within this page, you’d be able to see things like

• The ID of the task:outbound:...
• Name from outbound push config
• _idof (& link to?) the report/contact that triggered the task
• The time the task was created
• The time the task was last updated (w/errors, success, etc...)
• History of errors (if any)
• Response from API call once successful

[SCdF]

Before we put any effort into this, I'd appreciate a brief conversation looking forward re: our ability to send data to other systems.

Outbound push as implemented is very bespoke (and marked as beta in documentation), and so this view page would also be very bespoke. I would be wary of implementing features on top of outbound push, and solidifying its existence in our stack, unless we have truly decided that it or a derivation of it is the way forward.

[abbyad]

If https://github.com/medic/cht-core/pull/6372 is merged, it is possible that outbound push will only create a task if it is not sent immediately. As a result, this issue should be more generic to make the status available of all outbound pushes (complete, pending, and failed).

[MaxDiz]

@michaelkohn I added this to in design for 3.12 for additional review with an eng to determine the best pathway forward