How can I view the size of the events queue

greg schrank
Tera Contributor

Occasionally, I'll run into situations where events are not being processed, and the cause is likely due to a buildup of events. However, I cannot figure out how to verify this.

 

In older version, I could check System Diagnostics > Diagnostics Page and see total number of events pending (as described here) but in later versions, the diagnostics page no longer exists.

 

Is there a similar feature in newer versions?

1 ACCEPTED SOLUTION

AnveshKumar M
Tera Sage
Tera Sage

Hi @greg schrank 

Have you checked the Event Log? In System Policy -> Events -> Event Log, you can  see all the events that are triggered and filter using the state to see which are processed, running and error etc.

 

And you can also check Event monitoring dashboard at System Diagnostics -> Stats -> Events and Jobs Dashboard.

 

To check slow events, navigate to System Diagnostics -> Stats -> Slow Events

 

Screenshot_2023-10-07-07-48-59-512-edit_com.android.chrome.jpg

 

Please mark my answer helpful and accept as solution if it helped you 👍

Thanks,
Anvesh

View solution in original post

3 REPLIES 3

AnveshKumar M
Tera Sage
Tera Sage

Hi @greg schrank 

Have you checked the Event Log? In System Policy -> Events -> Event Log, you can  see all the events that are triggered and filter using the state to see which are processed, running and error etc.

 

And you can also check Event monitoring dashboard at System Diagnostics -> Stats -> Events and Jobs Dashboard.

 

To check slow events, navigate to System Diagnostics -> Stats -> Slow Events

 

Screenshot_2023-10-07-07-48-59-512-edit_com.android.chrome.jpg

 

Please mark my answer helpful and accept as solution if it helped you 👍

Thanks,
Anvesh

Thanks Anvesh.

 

Is there something I need to enable to access Events and Jobs Dashboard? I don't have that option in my developer instance:

 

gregschrank_0-1696798653370.png

 

Hi @greg schrank 

That dashboard comes with Vancouver I could have mentioned that.

Thanks,
Anvesh