Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Cached version of resources during List Resources in Orion Platform

Cached version of resources during List Resources in Orion Platform

Table of contents

Updated January 9th, 2019


When doing List Resources, an informational message shows up:

You see a cached version of resources from <Date and Time>


List resources.PNG


  • Orion Platform 2016.1 and later


  • This informational message is by design, In Orion platform 2016.1 and later development introduced a cache to speed up a list resources page to quickly see what is currently added.
  • The first time you run List Resources against the node, it will send requests using your chosen polling method against the node to show all the resources that can be monitored. Then, it will use this to build a cache of resources to be monitored.
  • When a user clicks into List Resources for the first time it populates a new table, NodeListResourcesCache as well as displaying the information to the user

  • The next time you run a List Resources against the node, you will see the informational message showing the last time you did a List Resources from that node.

  • The Force refresh button was then added to allow the user to repopulate the cache with newer data.

    When that's finished, doing a List Resource again will use the content of the table (and it should be much faster). This should work for all types of nodes.

  • If you need to refresh the results of resources to be monitored and build a new cache, just click the Force Refresh. It is important to note as new resources may have been added since such as interfaces and volumes.
  • Discovery will not populate the node cache, only a manual run of list resources against the node will achieve this.


Last modified