More monitoring intervals

Feedback Orchestrator
, ,
1

For now it is only possible to monitor a queue, with an interval of either 1 hour or 1 day. I would like to be able to have more options, in particular be able to go back for a longer period than 1 day.

For example we currently have a scheduled job running in the afternoon at 16:30 each workday (Monday through Friday). It runs for approximately one hour and since we tend to leave before 17:30, we are not able to use the monitoring for the run started on Fridays.

4 Likes
2

Hi,
Thank you for your suggestion. I added it to our internal ideas tracker for our team to consider.

4 Likes
4

Yes, I do not see point to implement such nice dashboards into Orchestrator if the monitoring interval is only one day at max.

1 Like
5

Hi @Pablito,

Do you know what’s the latest on that one?

Have a good one,
Filip

6

This one has been reviewed. It means that the ticket will be tracked as eventual feature. But we don’t have any estimation yet.

1 Like
7

In the meantime, what’s the best way to get this sort of information for a period longer than 1 day from an on-prem installation?

I’m talking number of jobs, their outcomes, average job duration, total time spent per process etc.?

1 Like
8

Would like to see more intervals in monitoring or anywhere else where we can get such granular metrics in terms of average execution time, running, pending, faulted etc.

2 Likes
9

Hi @Pablito.
Any news on the ticket and do you have an estimate yet?

10

Hi,
We have it on the long list of Orchestrator improvements. Unfortunately, I don’t have an ETA.

2 Likes
11

Hello Pawel, hope you are doing well? Any updates on this matter, since it already has passed a lot of time since this was requested, which was also mentioned since 2019 within a other post: Set default interval level for queue monitoring

Thank you

12

Hi @Pablito, has this Orchestrator improvement gone any further?

13

@Ovidiu_Constantin could you provide more details?

15

We do not have plans to change the default monitoring periods for the moment. Advanced users could use the Insights product, that can be tweaked to fit specific use cases.

1 Like
17

Hello, we have the same requirement.
A monitoring interval of max. 1 month is much too less.
Minimum max. 1 year would be suitable to make this feature useful and valueable.

18

You probably should use Insights.