Admin Dashboard Metrics
With the new admin dashboard application and metric gathering, I have a question on 2 specific measurements -
Is there any information what these represent? How are notifications "in queue"? Are these queues that I need to review in the database and clear?
The metric fields in the application have this information stored in the field descriptions.
The first is the number of notifications that are waiting to be sent. These are cases where the record was hard saved in a state that met the digest notification criteria, but it hasn't yet reached the notification's send interval. This number for many organizations will never be zero (unless all your digests fire at once), but will give you an idea of your "normal" queue size so that you can see if the queue is abnormally large or small potentially indicating a problem such as records not queuing when they should or queuing when they shouldn't.
The second is the count of items that are waiting to be picked up, indexed, and then written to the index file store. This number again in many organizations may not always be zero, and certainly would not be after doing a large data import / feed, but again should have a "normal" for the instance to allow you to see when something is going wrong and things are not being indexed.
Thanks for that detail. I have a follow-up specific to the notification queue. Since installing the application and gathering the metric, the volume started at 54,879 and is now 55,056. Is there any option to view what is in queue and take any action? What I don't want is to have 55,000 emails hit our exchange and flood the end users mailbox.
The queue is not exposed through any UI, and would only be available through database query. I'd have to double check on what the exact scenarios are, but I know there are ways for things to make their way in to the queue that won't ever be sent under current configuration. A good example would be a monthly digest email that is a few hours from going out, and is then marked inactive. All of it's items will remain in the queue and never send since the template isn't active.