How to handle the error when project storage (or RDM collection) is out of quota

[hurngchunlee]

There has been two times that streamer job failed due to the project storage is out of quota.

The baseline is that the data is anyway streamed to the catch-all RDM collection, but not to the project storage.

Currently I have to check the failed job and send a notification email manually (and for some reason, I didn't get feedback in one of the two cases).

Should it be improved?

[robertoostenveld]

I think that researchers do not need information about quota overruns that are specific to the streamer, only a general one. It would be fine to send a daily mail about quota being (almost) full. That is also relevant for analysis.

I think that you (or the TG sysadmin) should know which errors happen to anticipate researchers asking for support at the helpdesk, and possibly also for catching problems with the catch-all. You may want to consider forwarding streamer error emails to datasupport, so that the support team knows about it (and can deal with it, but they can also choose not to act upon user errors).