You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DM API has a default limit of showing only 100 events. In some cases jobs can create more than than this in which case you don't see the ones after 100 which is confusing to the user.
The API does allow to provide a parameter for how many to include, and an offset to start from.
Probably we should:
increase the default a bit (e.g. 500)
change noisy jobs to be less noisy (the one of concern here is the shard job)
enhance the UI so that it requests a specific number of events and if it gets exactly that many it goes back for more
The text was updated successfully, but these errors were encountered:
I reconfigured the shard job so that it is now less noisy. So this is less of a priority now, but still needs to be handled at some stage. If the default limit in the API is also raised to 500 then I don't think we'll see this very often.
Just noticed that I exposed the DM-API default event limit to the Pod ENV. So a simple restart of the DM should suffice - but I will change the 'out of box' value shortly.
The DM API has a default limit of showing only 100 events. In some cases jobs can create more than than this in which case you don't see the ones after 100 which is confusing to the user.
The API does allow to provide a parameter for how many to include, and an offset to start from.
Probably we should:
The text was updated successfully, but these errors were encountered: