This section consists of: 

Overview

Shows the overall status of the IM instance:

• Top part – system info, IM status and version, build info, instance info with Git URL, server and Git logs, ELK statistics.
  Note:

  • In the Build Info section, there is information on the image type (standard or custom) and you can convert here provisioned IMs to custom image manually. You can also trigger custom image rebuild (might be needed when adding external resources to the repository). Both operations are meant for experienced users only.

  • In the Instance Info section, the links here are active only for users entitled to access Pricefx Git. 

• Middle chart – history of the up and down time

• Bottom charts – usage of JVM memory, heap memory and disk space

Open

Public and Private Routes

It is possible to define public and private routes: a public route's ID starts with the prefix "public". If there is no public route defined, all routes are considered public.

Private routes are displayed grey in the table and cannot be stopped, started, removed and payload cannot be sent to them via UI.

Messages

Shows incoming (to Pricefx) and outgoing (from PlatformManager) messages, events (from PlatformManager) and failed jobs.  

After you click each message category, you will get a list of corresponding messages in the table below. 

Open

The table below the timeline shows additional details for each message.

The messages are stored in Elasticsearch, a search and analytics engine. (It is not possible to get a direct access to Elasticsearch; the view is always through PlatformManager and it is limited only to one customer for whom you need the access permissions.)

To filter in the table, use the time range filter at the top right or click one of the message categories below the timeline.

Records

Shows records for all actions which took place in PlatformManager. 

It is especially useful to check the Failed column. In addition, there is a job scanning the failed records and if there are any, it sends an email notification. This notification contains a list of messages and a link back to the IM instance where users can examine the case. The user must be entitled to view this IM instance for the link to work. 

You can also download the failed records as CSV file. To do so, expand the row with failed records and you will get another nested table with just the failed records. Above this table there is the Export Errors button. Only 10 000 records can be viewed and exported.

This section is handy for troubleshooting and so it is visible only to the integration engineers. 

Log History

Shows the log history, as it is logged into Elasticsearch (search and analytics engine). This section is useful for troubleshooting and so it is visible only to the integration engineers. The data in Elasticsearch is kept for up 3 months.

You can save your most used Elasticsearch queries using the Queries menu next to the search box. It allows you to save queries, share them with other users in PlatformManager, edit or delete them. If you share a query with a user, the query will automatically appear among saved queries for this user.

You can export the selected columns into a CSV file (using the buttons Columns and Export). 

Loggers

In this section you can set the logging levels for each component. 

For the description of the levels (Off, Error, Warn, Info, Debug, Trace) see the documentation of this library. 

Templates

Shows a list of Integration Templates and Accelerators deployed to the IM instance. 

Merge Requests

Shows a list of merge requests, so that you see what changes and by whom were done on the environment. Merge requests are initiated within the Transport to process via the cloud provider IM instances.  

The merge request can be deployed/discarded either from the Notification menu (top right icon) or from the row menu in the Integrations table.

Failed Events

This section shows all failed events of a given IM instance. You can rerun a single event (using the row menu) or all events (using the options below the table). 

To be able to rerun events, you need the Integration - Edit permission.

Documentation

Shows summary information on the IM implementation, including IM version, instance name, list of routes, scheduled jobs, mappers, converters and beans.