Synchronization Troubleshooting - Bugreport and feature request

[Gassim (AL-Gassim Sharaf Addin)]

Hi @gregory

This is an interesting idea. You’re welcome to submit an idea, see Vote for DHIS2 features & submit your ideas in our new software roadmap process! .

Regrading the main post, I checked with @milagros whose looking at this issue:

@gregory

The application does not manage to display the errors when there are 2 many events in error. This is due to one one of the request from the app, which tries to fetch all events with sync errors (. The response is “header too large” when there are too many events.
the request looks like this
/api/41/tracker/events?event=Event1_UID%3BEvent1_UID%3Event3_UID%3BEvent4_UID%3BEvent5_UID%3BEvent6_UID%3BEvent7_UID… Etc

This might be a bug issue.

@gregory

In order to give access to the “synchronization troubleshoot” application, I had to grant the authority “F_JOB_LOG_READ” to the users.
They have access to the logs, through the app, however, they see all the logs, from all the programs, from all the OUs.
In order to decentralize the sync troubleshoot, it would be really nice to enable each user to only see the logs from the OUs or programs that are assigned to them.

If I understood @milagros correctly, users with the authority to use the app who can view these logs will only be able to see the details of the errors need to have access to the related metadata.