Table of Contents

Search

  1. Preface
  2. Part 1: Version 10.5.6 - Version 10.5.6.x
  3. Part 2: Version 10.5.5 - 10.5.5.x
  4. Part 3: Version 10.5.4 - 10.5.4.x
  5. Part 4: Version 10.5.3 - 10.5.3.x
  6. Part 5: Version 10.5.2 - 10.5.2.1.x
  7. Part 6: Version 10.5.1 - 10.5.1.1
  8. Part 7: Versions 10.5 - 10.5.0.1
  9. Part 8: Versions 10.4.1 - 10.4.1.3
  10. Part 9: Versions 10.4 - 10.4.0.2
  11. Part 10: Versions 10.2.2 - 10.2.2 HotFix 1
  12. Part 11: Version 10.2.1
  13. Part 12: Version 10.2 - 10.2 HotFix 2

Hadoop Cluster Monitoring

Hadoop Cluster Monitoring

Effective in version 10.2.1, you can configure the amount of information that appears in the application logs that you monitor for a Hadoop cluster.
The amount of information in the application logs depends on the tracing level that you configure for a mapping in the Developer tool. The following table describes the amount of information that appears in the application logs for each tracing level:
Tracing Level
Messages
None
The log displays FATAL messages. FATAL messages include non-recoverable system failures that cause the service to shut down or become unavailable.
Terse
The log displays FATAL and ERROR code messages. ERROR messages include connection failures, failures to save or retrieve metadata, service errors.
Normal
The log displays FATAL, ERROR, and WARNING messages. WARNING errors include recoverable system failures or warnings.
Verbose initialization
The log displays FATAL, ERROR, WARNING, and INFO messages. INFO messages include system and service change messages.
Verbose data
The log displays FATAL, ERROR, WARNING, INFO, and DEBUG messages. DEBUG messages are user request logs.
For more information, see the "Monitoring Mappings in the Hadoop Environment" chapter in the
Informatica Big Data Management 10.2.1 User Guide
.

0 COMMENTS

We’d like to hear from you!