Tivoli EIF
Supported versions | Type | Authentication Type |
|---|---|---|
7, 8 | Agent | Org Bearer Token |
IBM’s Tivoli Event Integration Facility (EIF) is a toolkit that expands the types of events and system information that you can monitor. You can use it to develop your own adapters, which are tailored to your environment.
Use this integration to start sending monitoring events from Tivoli EIF to BigPanda.
Open Integration Manager
The Open Integration Manager is available for use with Tivoli. For more information, see the Open Integration Manager documentation.
Payload size
Alert payloads must be 6MB or smaller. Larger payloads will fail to process with BigPanda. We recommend reviewing your configurations to ensure that only actionable, useful information is being sent to BigPanda.
Upgraded installation for agent version 10.4.0 and above
The BigPanda agent has been upgraded for improved stability and system security. Agent versions 10.4.0 and up are installed using a virtual environment.
Multiple Agent Plugins
Running multiple agent plugins at the same time (i.e. listener and rawalertstransfer) will create a race condition with the local filesystem queue.
In this case, create a subdirectory for each plugin within the queue directory, and adjust the queue path in both the bp_listener.json and bigpanda.conf configuration files.
$ mkdir -p /var/lib/bigpanda/queue/listener /var/lib/bigpanda/dlq/listener
$ sudo bigpanda-config --add listener --app-key <your app key> --listener_queue_directory /var/lib/bigpanda/queue/listener --listener_dlq_directory /var/lib/bigpanda/dlq/listener
Configuring Timestamps
BigPanda requires the timestamp to be in epoch format. The bigpanda-listener service converts the human readable time, that is received from Tivoli EIF as the situation_time, into epoch format. The timestamp received does not include a timezone, so the bigpanda-listener service extracts the timezone in one of the following methods:
Configured in the bp_listener.json configuration file.
Set as an environment variable named TZ.
Resolved via the /etc/localtime symlink on the server.
Resolved via the /etc/timezone file on the server.
All timezone must be an IANA compliant timezone identifier. If the timezone lookup fails, a log entry is made and the current local timestamp is generated. If the timestamp received is in epoch format, timestamp conversion is skipped and the original timestamp is used.
Troubleshoot the Integration
If the bigpanda-listener service does not start, you can view the journal logs to get a more detailed explanation of the error. To view these logs, use the following command in the terminal:
journalctl -u bigpanda-listener
Uninstall the Integration
Deleting an integration requires that you remove the integration in both the integrated system and BigPanda. We recommend that you first uninstall the integration on the integrated system to prevent traffic from being sent and rejected by BigPanda, since the app key will not exist once you delete the integration in BigPanda.
Caution during replacement
When replacing an existing integration with a new tool or system, we recommend configuring the new integration first to ensure no data is lost.
Deactivate Inbound Integration
If you want to stop sending data to BigPanda but don’t want to delete your integration, you can temporarily deactivate it.
To deactivate an inbound integration:
In BigPanda, navigate to the Integrations tab and select the desired integration from the list. This will open integration details on the right side of the window.
At the top of the integration details, click the Active/Inactive toggle next to the application name to change the status of the integration.
In the integrations list, inactive integrations will be marked with a gray bar.
Alert resolution for inactive integrations
Any active alerts belonging to an inactive integration must be manually resolved or they will stay in the system until the auto-resolve window is reached.
Stop Sending Data to BigPanda
Within the integrated system, disable any settings that send data to BigPanda.
Each system requires specific changes to disable the integration with BigPanda. For example, you must delete the topic in CloudWatch, and you must disable the alert channel in New Relic. To determine the changes for your integrated system, reference the relevant documentation or contact BigPanda support.
Manually resolve any open alerts sent from the integration to remove the associated incidents from your incident feed. These incidents will not automatically resolve without an ok status from the original sending integration.
Delete the Integration in BigPanda
Take the following steps to delete the integration from BigPanda:
In BigPanda, navigate to the Integrations tab and select the desired integration from the list.
In the integration details on the right of the page, click the trash icon, then confirm you want to delete the integration. The integration will be removed immediately.
️Automatic alert resolution for deleted integrations
All active alerts from the integration will be resolved after deletion.
Data removal
This procedure does not remove any data from the integrated system.