> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Technology Health Tab

> The Technology Health Dashboard gives a real-time view of the health, availability, and performance of the technologies supporting your applications.

Components
[`Workspace`](https://docs.germainux.com/main/workspace)

Availability
2026.2 or later

> **[Key Insights](#key-insights)**
>
> Headline technology health signals

> **[Services & APIs](#services-&-apis)**
>
> Health of services and APIs

> **[Environments](#environments)**
>
> Compare environments side by side

> **[Investigate Technology Health](#investigate-technology-health)**
>
> Narrow from KPI to cause

## Technology Health Dashboard: Real-Time Monitoring of Application and Infrastructure Performance

## Overview

The **Technology Health Dashboard** provides a real-time view of the health, availability, and performance of the technologies supporting your applications and users.

It brings together application, component, service, database, host, and environment health so teams can quickly identify **where technology issues are occurring and what may be affected**.

## Key Insights

Use the Technology Health Dashboard to monitor:

| Insight | Description |
| - | - |
| Availability | **Availability** — Are applications, services, databases, hosts, and other monitored technologies available? |
| Performance | **Performance** — Which technologies are slow or performing outside expected levels? |
| Errors & Failures | **Errors & Failures** — Where are errors, failures, or abnormal conditions occurring? |
| SLA Health | **SLA Health** — Which technology KPIs are approaching or violating expected service levels? |
| Application Health | **Application Health** — Are monitored applications and their components operating as expected? |
| Service Health | **Service Health** — Are APIs, services, and dependencies available and performing normally? |
| Database Health | **Database Health** — Are databases experiencing performance, availability, capacity, or connection issues? |
| Infrastructure Health | **Infrastructure Health** — Are CPU, memory, disk, network, processes, or other host resources contributing to an issue? |
| Environment Health | **Environment Health** — Are conditions isolated to Production, Staging, QA, Development, or another environment? |
| Dependencies | **Dependencies** — Are downstream or upstream components contributing to application problems? |
| Trends | **Trends** — Is technology health improving, degrading, or showing recurring patterns? |

## Applications & Components

Monitor the health of applications and their underlying components to identify whether an issue affects an entire application or a specific functional or technical component.

Analyze:

* Availability
* Performance
* Errors
* Activity
* SLA status
* Component health
* Dependencies
* Trends

When an application issue is detected:

Application
Component
KPI
Related Signals
Instances
Analysis
Likely Root Cause

## Services & APIs

Monitor services, APIs, integrations, and other application dependencies.

Analyze:

* Availability
* Response time
* Request volume
* Errors and failures
* SLA status
* Dependencies
* Application impact
* Trends

Use GermainUX tracing and Analysis capabilities to follow issues across related transactions and dependencies:

User/Application Issue
Service
Request
Related Transaction
Trace
Likely Root Cause

## Databases

Monitor database health and identify conditions that may affect application performance or availability.

Depending on the configured monitoring, analyze:

* Availability
* Response time
* Activity
* Errors
* Connections
* Capacity

> **Show all 9**
>
> * Resource utilization
> * SLA status
> * Trends

When a database KPI becomes abnormal:

Database Condition
KPI
Related KPIs
Application Impact
Analysis
Likely Root Cause

## Hosts & Infrastructure

Monitor the servers and infrastructure supporting applications and services.

Depending on the configured monitoring, analyze:

* Availability
* CPU
* Memory
* Disk
* Network
* Processes

> **Show all 9**
>
> * Resource utilization
> * SLA status
> * Trends

This helps determine whether an application or service symptom may be associated with its underlying infrastructure.

Application/Service Issue
Host
Resource KPI
Related KPIs
Analysis
Likely Root Cause

## Environments

Compare technology health across configured environments such as:

* Production
* Staging
* QA
* Development

Environment comparison can help answer:

| Question | Purpose |
| - | - |
| Is the issue limited to Production? | Is the issue limited to Production? |
| Does the same behavior occur in Staging? | Does the same behavior occur in Staging? |
| Did a recent deployment introduce a difference? | Did a recent deployment introduce a difference? |
| Are infrastructure or configuration differences associated with the issue? | Are infrastructure or configuration differences associated with the issue? |

## Technology Frictions

Technology Health can surface technical conditions that may negatively affect applications, users, business processes, conversion, adoption, productivity, or experience.

Examples can include:

* Application errors
* Service failures
* Slow requests
* Failed transactions
* Database issues
* Infrastructure resource constraints

> **Show all 9**
>
> * Integration failures
> * Availability issues
> * Other abnormal technology conditions

When deeper investigation is required, use the **Analysis Dashboard Relationships graph** and filter on **Technology Frictions** to focus the investigation on relevant technical signals.

## Investigate Technology Health

Start with the affected technology or KPI and progressively narrow the investigation.

Technology Health Issue
Application / Service / Database / Host
KPI
Related Signals
Technology Frictions
Affected Population
Instances
Analysis
Likely Root Cause

The Analysis Dashboard can then connect technical evidence with affected users, sessions, transactions, and other available business or experience data.

## From Technology Issue to Business Impact

A technology problem should not be evaluated only by its technical severity.

GermainUX can help determine whether the issue is also affecting:

* Conversion
* Adoption
* Productivity
* User Experience

For example:

**Slow Service** \
&#x20;→ Application slowdown \
&#x20;→ Affected user sessions \
&#x20;→ Increased Experience Friction \
&#x20;→ Checkout abandonment \
&#x20;→ Conversion impact

This connects **technology health to actual user and business impact**.

## Additional Resources

> **[Frictions Dashboard](https://docs.germainux.com/main/frictions-dashboard.md)**
>
> Read more

> **[Analysis Dashboard](https://docs.germainux.com/main/4-analysis-dashboard.md)**
>
> Read more

> **[SLA Violations Dashboard](https://docs.germainux.com/main/slas.md)**
>
> Read more

> **[Transaction Insights](https://docs.germainux.com/main/transaction-insights.md)**
>
> Read more

> **[Correlation & Tracing](https://docs.germainux.com/main/correlation-and-tracing.md)**
>
> Read more

> **[Monitoring](https://docs.germainux.com/main/monitoring-management.md)**
>
> Read more

> **[AI](https://docs.germainux.com/main/ai-driven-insights.md)**
>
> Insights & Recommendations

> **[Analytics](https://docs.germainux.com/main/analytics.md)**
>
> More Analytics Features

> **[Automation](https://docs.germainux.com/main/automation.md)**
>
> More Automation Features

> **[Dashboards](https://docs.germainux.com/main/dashboard-and-report.md)**
>
> Dashboards and reports overview

> **[Reports](https://docs.germainux.com/main/reporting-automatic.md)**
>
> Automatic and scheduled reports

> **[Management](https://docs.germainux.com/main/management.md)**
>
> More Management Features

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.