Welcome to Monitoring Service

By using the Monitoring service, you can centralize events, metrics, and logs generated during data processing, save them to the remote server and access them through the user interface when you need. Storing your logs, events, and metrics in one place increases the reliability of your log/event/metric data and drastically reduces time spent on troubleshooting. You do not have to verify errors or warnings on each server individually (that can be even impossible when a server is unresponsive). With the Monitoring service, not only you keep your records secure, but you can also access your log, event, and metric data in a convenient way, filter their contents for finding the required information quickly. It helps track your system’s performance more efficiently, improve maintenance and support.

The Monitoring service supports two ways of records upload:

• Using Monitoring agent
• Using SDK

The Monitoring service defines logs, events, and metrics as a set of properties. The default properties are the time stamp, severity, and message (name for events).

Log, event, and metric entries are JSON objects that contain the required properties such as a timestamp, error, severity, environment, and any additional metadata. For example, you may want to specify in the log an XEServer route name, a component name, a project owner, and so on. The following is the format of a log record:

{

"objectType":"log", // required, types [log, event]

"timestamp":"2018-07-31T11:07:02.312", // required, formats [ISO8601, UNIX_MS]

"message":"Error message", // required, text

"severity":"DEBUG", // optional, text

"parameters":{ // optional, any names can be used for sub-fields

"logger":"xes.system", // optional, example

…

}

}

Using the user interface the Monitoring service provides, you can select which log/event properties to display that allows you to search and filter within the selected fields only. You can also set user permissions to restrict access to the required logs. You can also create rules to restrict access to the required log entries. In this case, users are able to search and filter within the allowed fields only.