Configuring an integration server to send logging, statistics, and accounting data to a
Kibana dashboard in IBM Bluemix
You can configure integration servers to send logging, statistics, and accounting data to the
Logmet service in IBM® Bluemix™, and then display the
data in the IBM Integration Bus Kibana dashboard.
About this task

You can configure your
integration servers to report the following information to the Logmet
service in Bluemix:
- Logging, statistics, and accounting data
- Logging data only

You can use the mqsichangebluemixreporting command
to configure either a specified integration server or all integration
servers on a specified integration node.
To enable
the reporting of logging information to Logmet, you must use the mqsichangebluemixreporting command
to enable your IBM Integration Bus integration
servers to send the logging information to the Logmet host. If you also want to send statistics and accounting
data, in addition to the logging information, you must then configure
the collection and reporting of statistics and accounting data by
using the mqsichangeflowstats command.
Procedure
Complete the following steps to configure
an integration server to send logging information to Logmet,
ready to be displayed in a Kibana dashboard in IBM Bluemix:
- Run the mqsichangebluemixreporting command
from the host machine that is running your integration node (typically
on-premise) to configure and activate the Bluemix reporting feature. For
example, the following command specifies that all integration servers
(as specified by the -g parameter) on integration
node myIntegrationNode1 will report to the Logmet
service in the us-south region, for the specified
user organization and space:

mqsichangebluemixreporting myIntegrationNode1 -g -l active -r https://api.ng.bluemix.net
-o a.user@comp.com -a dev -u a.user@comp.com -p password1 -d
You can set the logging status to
active only
if valid values are specified (or have been specified previously)
for the following parameters:

- -r region
- Sets the Bluemix region
for logging, statistics, and accounting services.
You can use the -r parameter to specify a Bluemix
API endpoint, such as https://api.ng.bluemix.net for
the us-south region, or https://api.eu-gb.bluemix.net for
the eu-gb region. Alternatively, you can use the
region names us-south or eu-gb.
If you specify a Bluemix API endpoint, the Logmet host and port are
obtained dynamically from a Bluemix service, rather than being set
with a static value. If you specify a Bluemix API endpoint, the Logmet
host and port are obtained dynamically from a Bluemix service, rather
than being set with a static value.
- -o organization
- Sets the Bluemix organization
for logging, statistics, and accounting services.
- -a space
- Sets the Bluemix space
for logging, statistics, and accounting services.
- -u userName
- Sets the Bluemix user
name for logging, statistics, and accounting services.
- -p password
- Sets the Bluemix password
for logging, statistics, and accounting services.
- -d
- Publishes the current IBM Integration Bus Kibana
dashboard for Bluemix logging, statistics, and accounting services.
For more information about required and optional
parameters, see the mqsichangebluemixreporting command.
When you have enabled
your integration servers to send logging information to Logmet, you
can enable them to also send message flow statistics and accounting
data:
Run the mqsichangeflowstats command,
specifying bluemix as the output format in the -o parameter,
and setting either the -a or -s parameter
to active. For example, the following
command turns on the collection of snapshot statistics data for all
message flows in all integration servers for myIntegrationNode,
and emits the data in bluemix format to the Logmet service:
mqsichangeflowstats myIntegrationNode -s -g -j -c active -o bluemix
For more information, see mqsichangeflowstats command.
Restart the integration node (or all the integration
servers that you have configured) for the changes to take effect. When the reporting status is active, data for all configured
integration servers on the specified integration node will be sent
to Logmet. Alternatively, if you specified a named integration server
(by using the -e parameter), data will be reported
for that integration server only.
The default interval for sending
events to Logmet is 60 seconds, so there can be a delay of up to 60
seconds before you see events in the Kibana dashboard.

You can now view the data from your configured
and restarted integration servers, by logging into the Logmet service
and opening the IBM Integration Bus Kibana
dashboard. For more information, see Viewing logging information in the IBM Integration Bus Kibana dashboard in IBM Bluemix.
What to do next
You can stop sending logging, statistics, and accounting data at any
time by setting the -l parameter to inactive and
then restarting the integration server.
You can view the current
configuration that has been set for reporting logging, statistics, and accounting data, by
using the mqsireportbluemixreporting command.