Why proactive monitoring is needed for Informatica Infrastructure ?

Why proactive monitoring is needed for Informatica Infrastructure ?
  • All the critical business process are constantly monitored by SLA based matrices.
  • Most of the critical business decision reports relay on the Informatica loads.
  • Periodic checks helps identify the vulnerabilities in the system very quickly.
  • It compromises to maintain the better quality and health in the infrastructure.
Third Party Recommended Tools For Proactive Monitoring Of Informatica Infrastructure.

1)      Informatica Support Console (ISC 2.2) :

It’s browser based GUI and can only be installed on Linux or Windows machine and you can configure all the Informatica environments (Powercenter,Meta Data Manager, ILM) irrespective of the Operating System those have installed on either it’s Unix Solaris/Linux/Windows. No need of  multiple installation of ISC only one instance installation is required.
It's a combination of -
  • Monitoring.
  • Alerting.
  • Operational Reporting.
  • Performance Monitoring (Server and Application) .
  • PM Utility (pmstack, ptstack,)
  • Meta Querying Tool.
2)      Log Express 1.0 :

Log express is a centralized automated log capturing tool whenever the service crash happens in infrastructure and logs can be automatically uploaded to the vendor's site for analysis.
It’s a combination of -
  • Log Management
All the downstream logs  will be captured (Sess Logs, Workflow Logs) in case of crash or termination in service.
All the upstream infrastructure logs (Repository Service logs, Integration Service Logs,  Node logs, exception logs, Service Framework log)
  • Backup Management  (Domain/Repository)
3 ) Control –M and Appworx.

Informatica Native scheduler doesn’t have the capability to schedule the Jobs in random intervals of time, rather it can schedule the jobs in regular intervals.
Above two frequently used third party helps manage the scheduling activities for the jobs in production environment, above tools comes with both client based and GUI based user interfaces through which you can schedule the Informatica jobs even in random intervals of time.

All the above tools helps automating the below regular operational activities.

We can discriminate both environment monitoring and load monitoring concepts instead of consolidating. These are major activities in Informatica administration per my expertise.
  • Environment Monitoring –
  1. Constantly keeping eye on whether the infrastructure is readily available, I meant to say keep monitoring the readiness in the environment.
  2. System level parameter checks CPU spike, Memory utilization , Number of parallel loads (sessions) running on each node.
Here 2nd option is most intricate one and intensive checks are needed.
  • Load Monitoring –
  1. Monitoring the loads (workflows) whether the loads are scheduled to respective timings.
  2. Recovery or Re-start in loads in case of any failures.
  3. Identifying the tardiness in loading process in case of any sessions are in hung status.
We have done automations for most of the above monitoring activities but still the manual re-checks are more important.

1.Alerts Monitoring.
2.Load Monitoring .
3.Servers Monitoring.


  1. […] Why proactive monitoring is needed for Informatica Infrastructure ? (ptlshivakumar.wordpress.com) […]

  2. Agree that its worth monitoring.. at the same time, the overhead or risk associated with monitoring tools has to be planned and taken care.


  3. Hi Sriya -

    Ultimately making sure that Informatica Infrastructure is healthy and behaving well or not.
    Thanks for you comments and suggestions...

    Many Thanks


  4. I have installed version 2.4 at our location. I'm starting to configure alerts and such. Do you have any recommendation as to some basic rules to set to monitor disk usage, v memory, etc.? I'm trying to start basic and then expand as I have experience with the tool.



Featured Post

Cloud : A Trendsetter Technology