Instances Overview

Up to version 1.72.0, instances were called clusters.

Shows a list of all instances and their details, such as Account, Account Status (taken from Salesfx), Type, URL, Release Name, Version, Last and Next Upgrade, Major and Minor Version Upgrade Duration, Provider, Check-in date, Instance overrides, Location, Account ID. This list is fully synchronized with records in Salesfx (based on the serial number field). If some information is missing in Salesfx or PlatformManager and it is known, it is added automatically in the other place.

When an instance stops reporting, it is deleted – after the deletion is approved in a workflow. This workflow is automatically initiated when the last recorded message from the instance is older than 2 weeks.

This section is visible only with the global permission Instance List – read.

You can also download this list in the CSV format.

Available options in this table:

A note on Server Roles: Setting/changing them really only makes sense in the old bare metal environments. In next-gen infrastructure, these server roles still exist, but they work in tandem with the k8s pods (i.e. the infrastructure) and cannot be viewed individually. As such, the below role explanation still applies, but the settings should not be changed really.

Edit Custom Upgrade Times – Allows you to specify upgrade times for major and minor versions.
Instance Admin – Allows you to view/manage instances. This option is visible only with the global permission Instance Admin.
The options are:
- Server Roles (to manage what every node should do; roles can be added/removed)
  - ListProcessor – A node that can (and will) process background jobs such as price list and price grid calculations etc. For distributed calculations this node will hold the master.
  - CalculationSlave – A node that accepts calculation requests as distributed slave.
  - CalculationFlowProcessor – A node that processes CF jobs.
  - CalculationFlowFailoverProcessor – A node that that will assume CalcFlowProcessor if primary fails (totally useless and should not be used in next gen!).
  - PADataLoad – A node that runs PA data load jobs. These nodes require fast disks.
  - EventProcessor – A node that processes (=sends) generates events out.
  - EmailProcessor – A node that sends emails. Any node can create email tasks, but the actual sending to the MTA happens here.
  - Janitor – A node that performs general house keeping.
  - CalculationScheduler – A node that processes the schedule (mainly PA for now, but this scheduling system will be favored over CF in the future).
- Restrict calculations to partition
- Restrict PA data loads to partition
- View information on: Jetty Host, Jetty Port, Last Join Date, Last Seen Date
Show Logs – Shows the log. This is available only for instances with Loki (log aggregation system).
Version History – Shows a table with used IM versions and dates of upgrade. (Versions are stored since May 2024, no historical data is provided.) It is available even to users who do not have any other permissions assigned for this particular instance; it is sufficient to have only the global permission Instances List – read.