IBM Integration Bus, Version 10.0.0.9 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Reporting logging, statistics, and accounting data to a Logmet service in IBM Bluemix and displaying it in a Kibana dashboard

Start of changeIBM® Integration Bus provides a facility to send logging, statistics, and accounting data for your integration servers to a Logmet service in IBM Bluemix™, and then display the reported information in a Kibana dashboard. End of change

About this task

Start of changeThis IBM Integration Bus logging, statistics, and accounting capability enables you to centralize the data for all your IBM Integration Bus installations, and gain an insight into the operation of your systems through a single focal point for viewing any failure alerts. You can choose to report the information for a specified integration server, or for all integration servers on a specified integration node. End of change

Start of changeYou can configure your integration servers to report the following information to the Logmet service in Bluemix:
  • Logging data (BIP messages)
  • Logging data, plus statistics and accounting data
End of change

Start of changeYou can then use a Kibana dashboard in IBM Bluemix to display the reported information for all your integration servers across all your integration nodes. A sample Kibana dashboard is provided, which you can load through the mqsichangebluemixreporting command, or you can choose to import it manually. You can use the dashboard to view logging data and statistics and accounting data for all your active, configured integration servers. The dashboard provides a set of charts that enable you to quickly identify the top five integration servers producing logging events, and the top five logging event types. It also provides charts showing total events, highlighting the logging information, warning, and error type, and the stop, start, and change activity of the integration servers. Additionally, a tabular view of the details of all events in the selected time period is provided. If you activate the reporting of message flow statistics and accounting data to Logmet, by running the mqsichangeflowstats command, the statistics and accounting data for your configured integration servers is also displayed in the dashboard. End of change

The Logmet service can also receive logging events from other products such as IBM MQ, WebSphere® Liberty, and IBM Business Process Manager, enabling you to build single queries that include events from multiple products.

When you activate the IBM Integration Bus logging capability, by specifying the -l parameter in the mqsichangebluemixreporting command, BIP messages that are triggered by integration server events are sent to the Logmet service.

Start of changeLogging data:End of change

The logging data that is sent to the service includes BIP messages with the following content:
@timestamp
ISO8601 date timestamp reported to the logging service
ALCH_TENANT_ID
Bluemix logging service tenant identifier
_type
The type of event, set to iib_message
host
Host name of the server that was the source of the event.

You can override the host name that the integration server reports to the Product Insights service, by setting the MQSI_BLUEMIXREPORTING_HOSTNAME environment variable. This can be useful if you are running the integration server in a container.

loglevel
Severity indicator mapped to an equivalent Bluemix logging level:
  • BIPnnnnE - ERROR
  • BIPnnnnW - WARNING
  • BIPnnnnI - INFO
module
The name of the integration node and server that was the source of the event, in the form "integration node name"."integration server name"
message
Full message text, starting with the message ID
ibm_sequence
Sequence number of the event, which is used to distinguish events with the same @timestamp
ibm_messageId
Message ID - IBM Integration Bus BIP number
ibm_serverName
Name of the integration server
ibm_threadId
Thread ID (text name)
ibm_processId
Process ID

The logging data that is sent to the Logmet service contains information about the events that are issued by the integration server process; events that are initiated by other components are not reported. If you compare the contents of the local event log with the contents of the log in the Kibana dashboard, you will see that a very small number of messages at the beginning and end of the local log are not shown in the dashboard; these are typically messages about the start and end of the message logging process.

For more information about this service, see the IBM Cloud Product Insights documentation.

Start of changeStatistics and accounting data:End of change

Start of changeYou can choose to report message flow statistics and accounting data to the Logmet service in Bluemix, in addition to reporting logging information. To enable the reporting of statistics and accounting data, you must first enable your IBM Integration Bus integration servers to send logging information to Logmet, and then configure the collection and reporting of the statistics and accounting data by using the mqsichangeflowstats command. For more information about statistics and accounting data, see Message flow statistics and accounting data and Starting collection of message flow accounting and statistics data.End of change

Procedure

Start of changeComplete the following steps to enable your IBM Integration Bus integration servers to send logging, statistics, and accounting data to Logmet:End of change

  1. Create an account in IBM Bluemix. In the IBM Bluemix welcome page, click Sign up and follow the instructions to create your account. For more information, see Setting up your account.
  2. Configure your integration servers to send logging, statistics, and accounting data to Logmet. You can choose either of the following methods to configure an integration server and specify your Bluemix service credentials:
    • Automatic configuration: Use the mqsichangebluemixreporting command to specify your Bluemix service credentials directly, so that it can configure the server and load the IBM Integration Bus Kibana dashboard into your Bluemix space automatically. To complete this task, follow the steps in Configuring an integration server to send logging, statistics, and accounting data to a Kibana dashboard in IBM Bluemix.

      When you use this method to configure an integration server to send data to the Logmet service, you must provide your Bluemix service credentials. Your Bluemix password is used only by the mqsichangebluemixreporting command, and it is not stored by IBM Integration Bus. However, if you would prefer not to provide the Bluemix service credentials directly, you can choose to use the alternative method, which is a manual configuration.

    • Manual configuration: Use the curl command with your Bluemix service credentials to obtain logging service tokens, and then specify the logging service tokens to the mqsichangebluemixreporting command so that it can configure the server and prepare the IBM Integration Bus Kibana dashboard for you to load into your Bluemix space manually. To complete this task, follow the steps in Configuring an integration server and loading the IBM Integration Bus Kibana dashboard manually.
  3. Start of changeView the logging, statistics, and accounting data for all your integration servers in the IBM Integration Bus Kibana dashboard, as described in Viewing logging information in the IBM Integration Bus Kibana dashboard in IBM Bluemix.End of change

bz91180_.htm | Last updated 2017-07-17 12:46:57