insights by infactory in-factory GmbH Splunk connected to PowerCenter - best of 2 leaders

We have recently started using Splunk in a customer project in addition to an ETL track with Informatica PowerCenter – here I would like to talk in particular about the possibilities that this combination gives you.

The Tools

But first a short introduction tool to both tools. Informatica PowerCenter is a classic ETL tool (extract, transform, load) and has been on the market for many years. It has a repository-based approach and stores the information about the developed software artifacts, relationships and executions in a relational database. For more details about PowerCenter, see our previous blog posts.

Splunk Enterprise is the product of the Splunk company of the same name. The product can process and visualize pretty much any data (log files) provided by machines. Almost any source can be connected. In addition, classic relational databases can also be included. And this is where the Informatica PowerCenter Repository comes into play. It is installed and operated on a relational database (Oracle, IBM DB2, Microsoft SQL Server or Sybase ASE).

Possible areas of application

Data stored in relational databases can be queried using SQL (Structured Query Language). Interesting database queries can be created and executed against the Informatica repository. For example, it can be used to query different environments for adjustments to software states and generate reports. For example, if a deployment is taking place on a test environment, Splunk can periodically check the timestamp and generate a deployment report – this can also be emailed or displayed in a dashboard – Splunk provides this functionality directly.

The log files of individual PowerCenter workflows or sessions from different environments can also be integrated into Splunk using agents in order to be able to evaluate them. This makes it possible to search for specific error patterns using all log files collected over a specific period of time. Direct access to the environment is not necessarily required if a workflow abort needs to be analyzed.

However, it is important to know that everything that ends up in Splunk can be analyzed. If your Informatica log files contain personal data, for example, they must be anonymized and/or access to the search restricted.

In summary, the combination of Splunk and Informatica works very well together and offers Splunk developers many possibilities to make their daily work easier and to get important information to the right addressees.

Translated with (free version)

Author: Daniel Kampf


Write us. We are looking forward to your message!