Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 8 Next »

#Frontdoor-Queue-Length


Identifying if the Frontdoor service has stopped

There are two ways to identify if the Frontdoor service has stopped running.

1 Admin Section

If you are an Admin on the NRDAv2 application you will be able to navigate to the Admin section at the top of the page. 

 

From the Admin section select the System Monitoring option form the menu

on the left hand side of the screen. 








System Monitoring

The system monitoring page shows a list of systems being used by the application and their current health.

If there are multiple Frontdoor services connected to the application then there will multiple rows showing each Frontdoor and their health.

If any of the Frontdoor services are showing Down then you can follow the next section on restarting the Frontdoor.

Example of the System Monitoring Screen

  

 

  

 

  

 

  

 

2 Frontdoor Queue Length

An alternative way of identifying if the Frontdoor has stopped is by navigating to any Dataset and going to the Ingest Rules page.

At the bottom of the page below any Ingest Rules there is a section called "Latest queue length for front door messages".
Below are a few examples for what to look out for when the Frontdoor is Down. 



This shows an example of a Frontdoor with no messages 

waiting to be consumed. This means that the Frontdoor is

functioning correctly and nothing needs to be done.







This is an example of a Frontdoor with messages waiting to be consumed.

If the numbers shown in the queues do not change for a period of time then 

the Frontdoor will need to be restarted.







Restarting Frontdoor Service



  • No labels