General trace and log analysis patterns allow the application of uniform diagnostics and anomaly detection across diverse software environments. It includes troubleshooting, debugging, describing, and explaining problems and incidents on various operating systems and platforms. It is also helpful in recording network traces, malware, general data, narratives, and text and image analysis (space-like narratology). This course, organized as a pattern language dictionary and cross-referenced with classification, explains and teaches more than 200 traces and log analysis patterns.

A Guide to Learning Software Trace and Log Analysis Patterns

## Intra-correlation
Sometimes we may see a functional activity and [basic facts](https://www.educative.io/courses/guide-learning-software-trace-log-analysis-patterns/basic-hidden-indirect-facts-constants-vocabulary) in a trace and want to find a correlation between the activity and facts in another part of the trace. If this **intra-correlation** fits into our problem description, we can present a plausible, and sometimes even the best, explanation of the problem. Here is an example of this, using the `WindowHistory` tracing tool. 

When a third-party application was losing focus frequently, we suspected that the terminal services client process was responsible. On examination, however, we found that the following WindowHistory trace fragment corresponded to that application:

# Intra-correlation
Sometimes we may see a functional activity and [basic facts](https://www.educative.io/courses/guide-learning-software-trace-log-analysis-patterns/basic-hidden-indirect-facts-constants-vocabulary) in a trace and want to find a correlation between the activity and facts in another part of the trace. If this **intra-correlation** fits into our problem description, we can present a plausible, and sometimes even the best, explanation of the problem. Here is an example of this, using the `WindowHistory` tracing tool. 

When a third-party application was losing focus frequently, we suspected that the terminal services client process was responsible. On examination, however, we found that the following WindowHistory trace fragment corresponded to that application:

This lesson introduces the following analysis patterns: intra-correlation, macrofunction, motif, and motivic trace.

Getting Started

Activity

Block and Data

Error and Large Scale

Message 1

Message 2

Trace as a Whole

Trace Set

Vocabulary, Memory, Code and Text

Conclusion

Index

Intra-Correlation, Macrofunction, Motif, Motivic Trace

Intra-correlation