# System Status - Live-Überwachung
📊 Live System Dashboard
Real-time Überwachung und Status-Monitoring des Georg Fischer WMS
⚙️ SYSTEM-MONITORING
Ziel: 99.9% Verfügbarkeit mit proaktiver Problem-Erkennung
Monitoring-Center: +41 81 770 7777 (24/7 NOC)
## Überblick
Das System Status Dashboard bietet Real-time Einblicke in die Gesundheit und Performance des Georg Fischer WMS. Proaktive Überwachung ermöglicht frühzeitige Problemerkennung und präventive Maßnahmen.
## Live System Status
WMS Core System
Uptime:
99.97%
Response Time:
1.2s
Active Users:
47
Database Server
CPU Usage:
68%
Memory:
12.3GB / 32GB
Connections:
156 / 500
SAP Integration
RFC Latency:
3.8s
Success Rate:
94.2%
Queue Depth:
23
Hardware Systems
HRL Status:
Online
AKL Status:
Online
Conveyor:
Active
## Navigation
Real-time Monitoring
Performance Metrics
Health Checks
Alert Management
Status History
## Real-time Monitoring {#real-time}
### Live Dashboard Metrics
#### **System Performance**
#### **Application Metrics**
```yaml
real_time_metrics:
response_times:
login: "1.2 seconds (Target: < 3s)"
order_creation: "2.8 seconds (Target: < 5s)"
inventory_lookup: "0.9 seconds (Target: < 2s)"
report_generation: "15.3 seconds (Target: < 30s)"
transaction_volume:
orders_per_hour: "247 (Peak: 450)"
inventory_movements: "892/hour"
user_sessions: "47 active"
api_calls: "1,247/minute"
error_rates:
application_errors: "0.02% (Target: < 0.1%)"
integration_failures: "2.1% (Target: < 1%)"
timeout_errors: "0.8% (Target: < 2%)"
user_errors: "1.3% (Acceptable)"
```
#### **Integration Status**
```yaml
integration_health:
sap_connection:
status: "Connected"
rfc_pool: "8/10 connections active"
avg_response_time: "3.8 seconds"
success_rate: "94.2%"
last_failure: "2024-03-15 14:23:17"
database_connections:
primary_db: "Connected (156/500 connections)"
backup_db: "Standby Ready"
replication_lag: "< 1 second"
hardware_interfaces:
hrl_communication: "Online"
akl_communication: "Online"
conveyor_system: "Active"
scanner_network: "47/50 devices online"
```
## Performance Metrics {#performance}
### Performance KPIs
#### **System Performance Trends**
#### **Performance Benchmarks**
```yaml
performance_targets:
response_time_sla:
tier_1_operations: "< 2 seconds (95th percentile)"
tier_2_operations: "< 5 seconds (95th percentile)"
tier_3_operations: "< 30 seconds (95th percentile)"
throughput_targets:
peak_concurrent_users: "100 simultaneous"
transactions_per_second: "50 TPS sustained"
data_processing_rate: "1000 records/minute"
availability_sla:
system_uptime: "> 99.9% monthly"
planned_downtime: "< 4 hours/month"
mttr: "< 2 hours for critical issues"
mtbf: "> 720 hours"
```
#### **Resource Utilization Analysis**
```yaml
resource_analysis:
cpu_patterns:
baseline_usage: "35-45% during business hours"
peak_usage: "70-80% during morning rush (08:00-10:00)"
overnight_usage: "15-25% (batch processing)"
memory_consumption:
application_heap: "12.3GB / 32GB allocated"
database_buffer: "18.7GB / 24GB allocated"
system_cache: "8.2GB active"
memory_leaks: "None detected"
storage_metrics:
database_growth: "2.3GB/month average"
log_file_growth: "450MB/day"
backup_size: "127GB (compressed)"
free_space_remaining: "28% (monitoring threshold: 20%)"
```
## Health Checks {#health-checks}
### Automated Health Monitoring
#### **System Health Checks**
```yaml
health_check_suite:
application_health:
web_service_ping:
endpoint: "/health"
frequency: "30 seconds"
timeout: "5 seconds"
expected_response: "HTTP 200 + JSON status"
database_connectivity:
test_query: "SELECT 1"
frequency: "1 minute"
timeout: "10 seconds"
connection_pool_check: "Active connections validation"
external_dependencies:
sap_rfc_test:
function: "RFC_PING"
frequency: "2 minutes"
timeout: "30 seconds"
email_service:
smtp_test: "Test connection to mail server"
frequency: "5 minutes"
infrastructure_health:
server_resources:
cpu_threshold: "< 90%"
memory_threshold: "< 85%"
disk_threshold: "< 90%"
network_connectivity:
gateway_ping: "< 10ms response time"
dns_resolution: "< 1 second lookup time"
external_api_reach: "Internet connectivity test"
hardware_status:
storage_health: "SMART status monitoring"
temperature_monitoring: "Server temperature sensors"
ups_status: "Uninterruptible power supply status"
```
#### **Business Function Tests**
```yaml
business_function_tests:
core_processes:
user_login:
test: "Automated login with test account"
frequency: "5 minutes"
validation: "Successful authentication + menu access"
order_creation:
test: "Create test order with dummy data"
frequency: "15 minutes"
validation: "Order saved + SAP integration triggered"
cleanup: "Delete test order after validation"
inventory_lookup:
test: "Query random article stock levels"
frequency: "10 minutes"
validation: "Results returned within SLA"
report_generation:
test: "Generate small test report"
frequency: "30 minutes"
validation: "Report completed successfully"
integration_tests:
sap_data_sync:
test: "Sync test material master record"
frequency: "1 hour"
validation: "Data consistency between systems"
printer_functionality:
test: "Send test label to each printer"
frequency: "2 hours"
validation: "Print queue processed successfully"
```
### Health Check Results
#### **Current Status Summary**
System Components
Web Application
PASS
Database Server
PASS
SAP Integration
WARN
Hardware Systems
PASS
Business Functions
User Authentication
PASS
Order Processing
PASS
Inventory Management
PASS
Reporting
PASS
## Alert Management {#alerts}
### Alert Configuration
#### **Alert Severity Levels**
```yaml
alert_levels:
critical:
description: "Systemausfall oder schwerwiegende Funktionsstörung"
response_time: "Sofortige Reaktion erforderlich"
notification: "SMS + Anruf + E-Mail + Slack"
escalation: "Nach 15 Minuten automatische Eskalation"
high:
description: "Signifikante Performance-Probleme oder Teilausfälle"
response_time: "15 Minuten"
notification: "E-Mail + Slack + SMS"
escalation: "Nach 1 Stunde Eskalation an Management"
medium:
description: "Performance-Verschlechterung oder Warnungen"
response_time: "2 Stunden"
notification: "E-Mail + Slack"
escalation: "Tägliche Review"
low:
description: "Informative Alerts und Trend-Warnungen"
response_time: "Best Effort"
notification: "E-Mail"
escalation: "Wöchentliche Review"
```
#### **Alert Rules & Thresholds**
```yaml
alert_rules:
system_alerts:
cpu_usage:
warning: "> 80% for 5 minutes"
critical: "> 95% for 2 minutes"
memory_usage:
warning: "> 85% for 10 minutes"
critical: "> 95% for 5 minutes"
disk_space:
warning: "> 85% used"
critical: "> 95% used"
response_time:
warning: "95th percentile > 5 seconds"
critical: "95th percentile > 10 seconds"
application_alerts:
error_rate:
warning: "> 1% errors in 15 minutes"
critical: "> 5% errors in 5 minutes"
user_sessions:
warning: "> 80 concurrent users"
critical: "> 100 concurrent users"
database_connections:
warning: "> 400 active connections"
critical: "> 480 active connections"
integration_alerts:
sap_connectivity:
warning: "RFC response time > 10 seconds"
critical: "RFC connection failure"
data_sync_delay:
warning: "Sync delay > 30 minutes"
critical: "Sync delay > 2 hours"
```
### Active Alerts
Current Alerts (Last 24 Hours)
0
Critical
1
High
3
Medium
7
Low
Recent Alerts
SAP Integration Performance Warning
RFC response time averaging 8.2 seconds (threshold: 5s)
2024-03-15 15:42:33
HIGH
Disk Space Warning
Log partition at 87% capacity (threshold: 85%)
2024-03-15 14:15:22
MEDIUM
Scheduled Maintenance Reminder
Monthly system maintenance scheduled for tonight 22:00-02:00
2024-03-15 12:00:00
INFO
## Status History {#history}
### Historical Performance
#### **Uptime Statistics**
```yaml
uptime_history:
current_month:
uptime_percentage: "99.97%"
total_downtime: "13 minutes"
planned_maintenance: "2 hours (excluded from SLA)"
unplanned_outages: "1 incident (13 minutes)"
last_3_months:
january_2024: "99.95% (18 minutes downtime)"
february_2024: "99.98% (8 minutes downtime)"
march_2024: "99.97% (13 minutes downtime)"
trend: "Stable, meeting SLA targets"
yearly_summary:
2023_uptime: "99.94%"
2024_ytd: "99.97%"
improvement: "+0.03% year-over-year"
```
#### **Major Incidents History**
2024-03-10
Database Connection Pool Exhaustion
Duration: 13 minutes
Impact: Complete system unavailability
Root Cause: Memory leak in connection pooling library
Resolution: Service restart + library update
Prevention: Enhanced connection monitoring implemented
2024-02-28
SAP Integration Timeout Issues
Duration: 45 minutes
Impact: Delayed order processing
Root Cause: Network latency spike to SAP server
Resolution: Network path optimization
Prevention: Redundant network path configured
2024-02-15
Hardware Maintenance
Duration: 2 hours (planned)
Impact: Scheduled downtime for server upgrades
Work Performed: RAM upgrade and OS patches
Result: 25% performance improvement
#### **Performance Trends**
```yaml
performance_trends:
response_time_trend:
3_month_average: "2.1 seconds"
improvement: "-15% since system optimization"
best_month: "February 2024 (1.8s average)"
error_rate_trend:
current_rate: "0.12%"
3_month_average: "0.18%"
improvement: "-33% reduction in errors"
capacity_utilization:
peak_usage: "68% (morning rush)"
average_usage: "42%"
growth_rate: "+5% month-over-month"
capacity_planning: "Sufficient for next 18 months"
```