Skip to main content
Availability2014.1 or later

KPI levels

Layers of Siebel metrics

Business-Process KPIs

Metrics for complete workflows

Component Resource KPIs

Server and component usage

Error KPIs

Failure rates and counts

Overview

GermainUX includes preconfigured KPIs for monitoring Oracle Siebel CRM user experience, business processes, availability, components, tasks, errors, crashes, integrations, workflows, database activity, logs, and synthetic transactions. These KPIs help teams:
  • Measure the experience of actual Siebel users
  • Identify slow screens, clicks, requests, and workflows
  • Detect component, server, Gateway, and HTTP outages
  • Monitor tasks, processes, memory, CPU, and capacity
  • Analyze Object Manager errors and crashes
  • Measure EAI, Web Service, Workflow, and database transactions
  • Track Service Request volume and resolution time
  • Proactively validate Siebel with synthetic transactions
  • Correlate user-facing symptoms with server-side causes
The available KPIs depend on the deployed GermainUX components, enabled data sources, Siebel version, and monitoring configuration.

KPI levels

Real User Experience KPIs

Session Replay KPIs

Siebel sessions use the standard GermainUX User Monitoring and Session Replay KPIs. These KPIs provide:
  • User-session duration
  • Session status and outcome
  • Recorded user activity
  • Replay availability
  • Application, browser, device, and user context
  • Errors, business processes, and feedback associated with the session
See KPIs for User Monitoring and Replay.

Click and browser KPIs

The Siebel User Click KPI connects the user’s action with all browser and Siebel requests generated by that action.

User Feedback KPIs

User Feedback KPIs capture positive and negative responses, comments, scores, and the corresponding application and session context. See KPIs of Real User Feedback Popup.

Business-Process KPIs

Custom business-process definitions can generate additional process and process-step KPIs.

Siebel Data KPIs

Availability and Status KPIs

Component Resource KPIs

Task and Process KPIs

Hung Session and Backlog KPIs

Error KPIs

Crash KPIs

GermainUX correlates related error, Enterprise, FDR, and core evidence and can categorize crashes as new or known.

Siebel Application Container KPIs

EAI and Integration KPIs

Database KPIs

Correlate SQL-query duration with Siebel user clicks, Object Manager activity, workflows, and business processes to determine whether database activity contributes to user-facing slowness.

Service Transaction KPIs

Web Engine and User Transaction KPIs

Workflow KPIs

Synthetic Monitoring KPIs

Synthetic KPIs can be used to measure:
  • Availability
  • Complete scenario duration
  • Individual step duration
  • Success or failure
  • Execution location
  • SLA compliance

Event and Configuration KPIs

Using the KPIs

After data collection begins, use GermainUX dashboards and analytics to:
  1. Compare user experience across screens, views, applets, users, teams, and environments.
  2. Identify the slowest clicks, requests, SQL queries, services, workflows, and business-process steps.
  3. Correlate user-facing slowness with tasks, processes, components, integrations, and database activity.
  4. Detect unavailable or degraded Siebel servers, Gateways, components, and endpoints.
  5. Identify components approaching task or process capacity.
  6. Distinguish new errors and crash signatures from recurring issues.
  7. Measure users and business processes affected by each issue.
  8. Configure SLAs for availability, duration, capacity, errors, and workflow completion.
  9. Alert teams when critical KPIs violate their thresholds.
  10. Validate resolution by comparing performance before and after a change.

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.