Skip to main content
ServiceAnalytics
Availability2021.3 or later

Availability and Uptime KPIs

Detect outages and failed components

Performance KPIs

Speed, throughput and capacity

Fact Models

Data models per KPI

Combining KPIs, Measures and Pivots

Trace impact to sessions
GermainUX provides preconfigured KPIs, pivots and measures for monitoring the availability, performance and health of hardware, software and cloud services. These analytics support desktop, server, mobile, containerized and distributed environments—whether deployed in the cloud or on premises. They help teams detect outages, degradation, capacity constraints, errors and abnormal behavior before they create a larger impact on users or business operations. Preconfigured analytics can be used as provided or customized for your technologies, architecture and service-level objectives.

What Technology Analytics Help You Understand

GermainUX technology KPIs can answer questions such as:
  • Is a server, service, database, application or container available?
  • Which components are failing or restarting?
  • Where are requests being rejected, queued or delayed?
  • Which resources are approaching capacity?
  • Which applications or dependencies generate the most errors?
  • Is performance degradation isolated to a host, environment, version or location?
  • Which technical condition caused a poor user experience or interrupted workflow?
  • Is an issue new, recurring or becoming more severe over time?

Availability and Uptime KPIs

Availability KPIs identify outages, failed components, crashes and conditions that prevent a technology from operating as expected.

General Availability

Application Failures and Crashes

.NET and Java Availability Indicators

Salesforce and Siebel Availability

Messaging and Connection Availability

Performance KPIs

Performance KPIs measure speed, throughput, utilization, capacity, contention and operational health.

Host and Operating-System Performance

These KPIs help determine whether infrastructure constraints are contributing to slow applications, failed requests or interrupted workflows.

ASP.NET and IIS Performance

Representative ASP.NET KPIs include:
  • Application cache-hit ratio
  • Executing, current and queued requests
  • Request execution time and wait time
  • Current connections
  • Disconnected, failed and rejected requests
  • Application and worker-process restarts
  • Running worker processes
Together, these KPIs reveal whether poor application performance is caused by request volume, queue saturation, insufficient resources, restarts or communication failures.

Database Performance

GermainUX includes database KPIs across several analytical areas: These measurements help teams identify whether a database problem is caused by a costly query, blocked session, lock, capacity constraint, inefficient access path or storage bottleneck.

Containers and Images

Apache, ActiveMQ and ZooKeeper

Elasticsearch

Representative Elasticsearch KPIs include:
  • Cluster health
  • Active shards
  • Cluster node count
  • Read and write operations
  • Tasks
  • Rollup jobs

Cloud and Messaging Services

Oracle E-Business Suite and BI Publisher

Representative KPIs include:
  • Active, pending and running concurrent requests
  • Concurrent processes, programs and queues
  • Requests completed with warnings
  • Terminated processes
  • Invalid database objects
  • BI Publisher diagnostic and server events

Browser and Digital Experience Signals

Technology analysis can also incorporate browser-side evidence: These signals help connect server and infrastructure conditions with what users actually experienced.

GermainUX Platform Health

GermainUX can monitor its own components using KPIs such as:
  • Agent status
  • Component status
  • Engine and Engine Manager status
  • Engine and Engine Manager CPU utilization
  • Engine and Engine Manager memory utilization
  • Aggregation duration
  • Fact-processing rate
  • GermainUX service events and action logs
  • Datamart data and index tablespace utilization

Fact Models

Each KPI is backed by a fact model appropriate for the type of data collected.

Pivots

A pivot segments a KPI result by a selected technology dimension. Available pivots vary by KPI and data source. Common technology pivots include:
  • Pivot
  • Application, application component and service
  • Technology type and component type
  • Environment, system, host and target
  • Cluster, node, container and process
  • Database, schema, table, query or session
  • Error, event, status and severity
  • Browser, device and operating system
  • Data center, region, country and cloud zone
  • User, session and business transaction
  • Version, release and deployment
Pivots help determine whether an issue is widespread or concentrated in a particular component, host, environment or user population.

Measures

A measure is the calculation applied to a KPI. Depending on the underlying fact model, GermainUX can provide:
  • Measure
  • Count and distinct count
  • Minimum and maximum
  • Average and total
  • Current or latest value
  • Rate and throughput
  • Availability or uptime percentage
  • Error and failure percentage
  • Resource utilization percentage
  • 50th, 90th, 95th, 99th and 99.9th percentiles
  • Standard deviation
Percentiles are particularly important for response-time and latency analysis because an average can hide severe degradation affecting a smaller population.

Combining KPIs, Measures and Pivots

From an aggregate KPI result, teams can drill into affected technologies, related events, traces and user sessions to identify root cause and business impact.

Correlate Technology with User and Business Impact

GermainUX can correlate technology KPIs with:
  • Real-user sessions and Session Replay
  • Application transactions and distributed traces
  • Errors and exceptions
  • Business processes and workflow steps
  • Conversion and drop-off events
  • Alerts and automated actions
This helps teams move from “the application is slow” to understanding which users and workflows were affected, which component caused the degradation and what corrective action should be prioritized.

Customize the Analytics

GermainUX can support custom:
  • KPIs and fact models
  • Measures and formulas
  • Pivots and business dimensions
  • Availability and performance thresholds
  • Static and statistical SLAs
  • Correlation and tracing logic
  • Dashboards, reports and alerts
  • Automated diagnostic or remediation actions
The exact KPI, pivot and measure set depends on the monitored technology, enabled components and implementation requirements.

Get Help

Contact GermainUX Support

The Germain Team can help you set this up.

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.