Skip to main content
ServiceAnalytics
Availability8.6.0 or later

Siebel Crash Example

Linking records after crashes

Create a Correlation Scenario

Define shared correlation keys

Create a KPI for the Correlated Data

Track consolidated events

Configuration Considerations

Checks before enabling scenario
Configure Exact-Match Correlation Exact-Match Correlation combines related data points from multiple sources when they share a common identifier—such as a process ID, thread ID, session ID, correlation ID, username, or server name. GermainUX uses the matching properties to create a single correlated data point containing information from the original events. This is useful when multiple sources describe different parts of the same incident, transaction, or business event.

​
Example: Oracle Siebel CRM Crash

When an Oracle Siebel CRM component crashes, GermainUX may collect related data from several sources:
  • Windows Event Log
  • Crash dump
  • Flight Data Recorder (FDR) file
Exact-Match Correlation can group these records using a shared key—such as the server name and process ID—and generate a single crash event containing the relevant information from all three sources.

​
Create a Correlation Scenario

​
1. Open Correlation Configuration

Go to: Germain Workspace > Analytics > Correlation Under Correlation Scenarios, select the Add icon.

​
2. Define the Scenario

Configure the general properties of the correlation scenario: For the Siebel crash example, the retention could be set to one hour if all related crash records are expected to arrive within that period.

​
3. Select the Source KPIs

Select the KPIs containing the raw data to correlate. For the Siebel crash scenario, these may include KPIs containing:
  • Event Log crash records
  • Crash dump information
  • FDR records
Any incoming data point matching one of the selected KPIs is evaluated by the correlation service as part of this scenario.

​
4. Define the Correlation Type and Matching Key

Configure how GermainUX determines that incoming records belong to the same event. For example, a Siebel crash correlation key could combine:
Exact-Match Correlation: 4. Define the Correlation Type and Matching Key
The appropriate key depends on the monitored use case. Other examples include:
  • sessionId
  • correlationId
  • threadId
  • username
  • A combination of application, host, and transaction ID
The Key Expression must generate the same value from every source record that should be combined.
Exact-Match Correlation: 4. Define the Correlation Type and Matching Key, image 2

​
5. Configure Fields to Exclude

Define which fields should not be copied from the raw records into the correlated output. Any field not excluded can be transferred to the correlated data point. For example, if system.name is not excluded, the correlated event can retain the system name from its source records. Exclude fields when they are:
  • Irrelevant to the correlated result
  • Duplicated across sources
  • Likely to conflict
  • Too large or unnecessary to retain
  • Sensitive and not required for analysis

​
6. Save the Scenario

Save the correlation scenario. GermainUX will begin evaluating incoming data against the selected KPIs, filters, and Key Expressions.

​
Create a KPI for the Correlated Data

To display and analyze the correlated output:
1

Go to Germain Workspace > Analytics > KPIs

2

Create a KPI

3

Set its Fact Class to the output type configured in the correlation scenario

4

Set its Name to match the name generated by the scenario

5

Save the KPI

6

Add the KPI to the appropriate dashboard

The resulting KPI can be used to monitor, segment, alert on, and investigate the consolidated events.

​
Configuration Considerations

Before enabling the scenario, confirm that:
  • Every related source contains the fields required by the Key Expression.
  • The generated key is specific enough to avoid combining unrelated events.
  • Retention is long enough to accommodate delays between data sources.
  • Filters exclude irrelevant source records.
  • The output KPI matches the scenario’s Fact Class and generated name.

​
Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.