Suggest an Idea

[birendodia]

Currently we use attrep_status for task specific information like task timestamp information. Since the table is common within all our tasks, there is contention on table when multiple updates are happening for all tasks.

The current strategy / mitigation is to have separate tables for each task or group by similar tasks as well as reducing the update frequency to 5 mins. This causes lot of admin work and consolidation on data and latency in task status.

Requesting to expose this information via QEM GetTaskDetails API. This would reduce lot of admin work and contention at the target ( attrep_status table updated)

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.