Die vorliegende Übersetzung wurde maschinell erstellt. Im Falle eines Konflikts oder eines Widerspruchs zwischen dieser übersetzten Fassung und der englischen Fassung (einschließlich infolge von Verzögerungen bei der Übersetzung) ist die englische Fassung maßgeblich.
# Beispiele für die Komponentenkonfiguration
Die folgenden Beispiele zeigen Komponentenkonfigurationen im JSON-Format für relevante Services.
**Topics**
+ [Amazon-DynamoDB-Tabelle.](component-configuration-examples-dynamo.md)
+ [Amazon EC2 Auto Scaling (ASG)](component-configuration-examples-asg.md)
+ [Amazon-EKS-Cluster](component-configuration-examples-eks-cluster.md)
+ [Amazon Elastic Compute Cloud (EC2)-Instance](component-configuration-examples-ec2.md)
+ [Amazon Elastic Container Service (Amazon ECS)](component-configuration-examples-ecs.md)
+ [Amazon-ECS-Dienstleistungen](component-configuration-examples-ecs-service.md)
+ [Amazon-ECS-Aufgaben](component-configuration-examples-ecs-task.md)
+ [Amazon Elastic File System (Amazon EFS)](component-configuration-examples-efs.md)
+ [Amazon FSx](component-configuration-examples-fsx.md)
+ [Amazon Relational Database Service (RDS) Aurora MySQL](component-configuration-examples-rds-aurora.md)
+ [Amazon-Relational-Database-Service(RDS)-Instance](component-configuration-examples-rds.md)
+ [Amazon-Route-53-Zustandsprüfung](component-configuration-examples-health-check.md)
+ [Gehostete Zone von Amazon Route 53](component-configuration-examples-hosted-zone.md)
+ [Amazon Route 53 Resolver Endpunkt](component-configuration-examples-resolver-endpoint.md)
+ [Amazon Route 53 Resolver Konfiguration der Abfrageprotokollierung](component-configuration-examples-resolver-query-logging.md)
+ [Amazon-S3-Bucket](component-configuration-examples-s3.md)
+ [Amazon Simple Queue Service (SQS)](component-configuration-examples-sqs.md)
+ [Amazon-SNS-Thema](component-configuration-examples-sns.md)
+ [Amazon Virtual Private Cloud (Amazon VPC)](component-configuration-examples-vpc.md)
+ [Gateways von Amazon VPC Network Address Translation (NAT)](component-configuration-examples-nat-gateway.md)
+ [API-Gateway-REST-API-Phasen](component-configuration-examples-api-gateway.md)
+ [Application Elastic Load Balancing](component-configuration-examples-application-elb.md)
+ [AWS Lambda Funktion](component-configuration-examples-lambda.md)
+ [AWS Network Firewall Regelgruppe](component-configuration-examples-firewall-rule-group.md)
+ [AWS Network Firewall Zuordnung von Regelgruppen](component-configuration-examples-firewall-rule-group-assoc.md)
+ [AWS Step Functions](component-configuration-examples-step-functions.md)
+ [Vom Kunden gruppierte Amazon-EC2-Instances](component-configuration-examples-grouped-ec2.md)
+ [Elastic Load Balancing](component-configuration-examples-elb.md)
+ [Java](component-configuration-examples-java.md)
+ [Kubernetes auf Amazon EC2](component-configuration-examples-kubernetes-ec2.md)
+ [RDS MariaDB und RDS MySQL](component-configuration-examples-mysql.md)
+ [RDS Oracle](component-configuration-examples-oracle.md)
+ [RDS PostgreSQL](component-configuration-examples-rds-postgre-sql.md)
+ [SAP ASE auf Amazon EC2](component-configuration-examples-sap-ase.md)
+ [SAP ASE bei Amazon EC2 mit hoher Verfügbarkeit](component-configuration-examples-sap-ase-ha.md)
+ [SAP HANA bei Amazon EC2](component-configuration-examples-hana.md)
+ [SAP HANA bei Amazon EC2 mit hoher Verfügbarkeit](component-configuration-examples-hana-ha.md)
+ [SAP NetWeaver auf Amazon EC2](component-configuration-examples-netweaver.md)
+ [NetWeaver SAP-Hochverfügbarkeit auf Amazon EC2](component-configuration-examples-netweaver-ha.md)
+ [SQL Always On-Verfügbarkeitsgruppe](component-configuration-examples-sql.md)
+ [SQL-Failoverclusterinstance](component-configuration-examples-sql-failover-cluster.md)
# Amazon-DynamoDB-Tabelle.
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für eine Amazon-DynamoDB-Tabelle.
```
{
"alarmMetrics": [
{
"alarmMetricName": "SystemErrors",
"monitor": false
},
{
"alarmMetricName": "UserErrors",
"monitor": false
},
{
"alarmMetricName": "ConsumedReadCapacityUnits",
"monitor": false
},
{
"alarmMetricName": "ConsumedWriteCapacityUnits",
"monitor": false
},
{
"alarmMetricName": "ReadThrottleEvents",
"monitor": false
},
{
"alarmMetricName": "WriteThrottleEvents",
"monitor": false
},
{
"alarmMetricName": "ConditionalCheckFailedRequests",
"monitor": false
},
{
"alarmMetricName": "TransactionConflict",
"monitor": false
}
],
"logs": []
}
```
# Amazon EC2 Auto Scaling (ASG)
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für Amazon EC2 Auto Scaling (ASG).
```
{
"alarmMetrics" : [
{
"alarmMetricName" : "CPUCreditBalance"
}, {
"alarmMetricName" : "EBSIOBalance%"
}
],
"subComponents" : [
{
"subComponentType" : "AWS::EC2::Instance",
"alarmMetrics" : [
{
"alarmMetricName" : "CPUUtilization"
}, {
"alarmMetricName" : "StatusCheckFailed"
}
],
"logs" : [
{
"logGroupName" : "my_log_group",
"logPath" : "C:\\LogFolder\\*",
"logType" : "APPLICATION"
}
],
"processes" : [
{
"processName" : "my_process",
"alarmMetrics" : [
{
"alarmMetricName" : "procstat cpu_usage",
"monitor" : true
}, {
"alarmMetricName" : "procstat memory_rss",
"monitor" : true
}
]
}
],
"windowsEvents" : [
{
"logGroupName" : "my_log_group_2",
"eventName" : "Application",
"eventLevels" : [ "ERROR", "WARNING", "CRITICAL" ]
}
]
}, {
"subComponentType" : "AWS::EC2::Volume",
"alarmMetrics" : [
{
"alarmMetricName" : "VolumeQueueLength"
}, {
"alarmMetricName" : "BurstBalance"
}
]
}
],
"alarms" : [
{
"alarmName" : "my_asg_alarm",
"severity" : "LOW"
}
]
}
```
# Amazon-EKS-Cluster
Das folgende Beispiel zeigt Komponentenkonfigurationen im JSON-Format für den Amazon-EKS-Cluster.
```
{
"alarmMetrics":[
{
"alarmMetricName": "cluster_failed_node_count",
"monitor":true
},
{
"alarmMetricName": "node_cpu_reserved_capacity",
"monitor":true
},
{
"alarmMetricName": "node_cpu_utilization",
"monitor":true
},
{
"alarmMetricName": "node_filesystem_utilization",
"monitor":true
},
{
"alarmMetricName": "node_memory_reserved_capacity",
"monitor":true
},
{
"alarmMetricName": "node_memory_utilization",
"monitor":true
},
{
"alarmMetricName": "node_network_total_bytes",
"monitor":true
},
{
"alarmMetricName": "pod_cpu_reserved_capacity",
"monitor":true
},
{
"alarmMetricName": "pod_cpu_utilization",
"monitor":true
},
{
"alarmMetricName": "pod_cpu_utilization_over_pod_limit",
"monitor":true
},
{
"alarmMetricName": "pod_memory_reserved_capacity",
"monitor":true
},
{
"alarmMetricName": "pod_memory_utilization",
"monitor":true
},
{
"alarmMetricName": "pod_memory_utilization_over_pod_limit",
"monitor":true
},
{
"alarmMetricName": "pod_network_rx_bytes",
"monitor":true
},
{
"alarmMetricName": "pod_network_tx_bytes",
"monitor":true
}
],
"logs":[
{
"logGroupName": "/aws/containerinsights/kubernetes/application",
"logType":"APPLICATION",
"monitor":true,
"encoding":"utf-8"
}
],
"subComponents":[
{
"subComponentType":"AWS::EC2::Instance",
"alarmMetrics":[
{
"alarmMetricName":"CPUUtilization",
"monitor":true
},
{
"alarmMetricName":"StatusCheckFailed",
"monitor":true
},
{
"alarmMetricName":"disk_used_percent",
"monitor":true
},
{
"alarmMetricName":"mem_used_percent",
"monitor":true
}
],
"logs":[
{
"logGroupName":"APPLICATION-KubernetesClusterOnEC2-IAD",
"logPath":"",
"logType":"APPLICATION",
"monitor":true,
"encoding":"utf-8"
}
],
"processes" : [
{
"processName" : "my_process",
"alarmMetrics" : [
{
"alarmMetricName" : "procstat cpu_usage",
"monitor" : true
}, {
"alarmMetricName" : "procstat memory_rss",
"monitor" : true
}
]
}
],
"windowsEvents":[
{
"logGroupName":"my_log_group_2",
"eventName":"Application",
"eventLevels":[
"ERROR",
"WARNING",
"CRITICAL"
],
"monitor":true
}
]
},
{
"subComponentType":"AWS::AutoScaling::AutoScalingGroup",
"alarmMetrics":[
{
"alarmMetricName":"CPUCreditBalance",
"monitor":true
},
{
"alarmMetricName":"EBSIOBalance%",
"monitor":true
}
]
},
{
"subComponentType":"AWS::EC2::Volume",
"alarmMetrics":[
{
"alarmMetricName":"VolumeReadBytes",
"monitor":true
},
{
"alarmMetricName":"VolumeWriteBytes",
"monitor":true
},
{
"alarmMetricName":"VolumeReadOps",
"monitor":true
},
{
"alarmMetricName":"VolumeWriteOps",
"monitor":true
},
{
"alarmMetricName":"VolumeQueueLength",
"monitor":true
},
{
"alarmMetricName":"BurstBalance",
"monitor":true
}
]
}
]
}
```
**Anmerkung**
Der Abschnitt `subComponents` von `AWS::EC2::Instance`, `AWS::EC2::Volume` und `AWS::AutoScaling::AutoScalingGroup` gilt nur für Amazon-EKS-Cluster, die auf dem EC2-Starttyp ausgeführt werden.
Der Abschnitt `windowsEvents` von `AWS::EC2::Instance` in `subComponents` gilt nur für Windows, das auf Amazon-EC2-Instances ausgeführt wird.
# Amazon Elastic Compute Cloud (EC2)-Instance
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für eine Amazon-EC2-Instance.
**Wichtig**
Wenn eine Amazon-EC2-Instance in den Status `stopped` wechselt, wird sie aus der Überwachung entfernt. Wenn es in einen `running` Status zurückkehrt, wird es der Liste der **nicht überwachten Komponenten** auf der Seite mit den **Anwendungsdetails der Application Insights-Konsole** hinzugefügt. CloudWatch Wenn die automatische Überwachung neuer Ressourcen für die Anwendung aktiviert ist, wird die Instance zur Liste der **Überwachten Komponenten** hinzugefügt. Die Protokolle und Metriken werden jedoch auf den Standardwert für die Workload festgelegt. Die vorherige Protokoll- und Metrikkonfiguration wird nicht gespeichert.
```
{
"alarmMetrics" : [
{
"alarmMetricName" : "CPUUtilization",
"monitor" : true
}, {
"alarmMetricName" : "StatusCheckFailed"
}
],
"logs" : [
{
"logGroupName" : "my_log_group",
"logPath" : "C:\\LogFolder\\*",
"logType" : "APPLICATION",
"monitor" : true
},
{
"logGroupName" : "my_log_group_2",
"logPath" : "C:\\LogFolder2\\*",
"logType" : "IIS",
"encoding" : "utf-8"
}
],
"processes" : [
{
"processName" : "my_process",
"alarmMetrics" : [
{
"alarmMetricName" : "procstat cpu_usage",
"monitor" : true
}, {
"alarmMetricName" : "procstat memory_rss",
"monitor" : true
}
]
}
],
"windowsEvents" : [
{
"logGroupName" : "my_log_group_3",
"eventName" : "Application",
"eventLevels" : [ "ERROR", "WARNING", "CRITICAL" ],
"monitor" : true
}, {
"logGroupName" : "my_log_group_4",
"eventName" : "System",
"eventLevels" : [ "ERROR", "WARNING", "CRITICAL" ],
"monitor" : true
}],
"alarms" : [
{
"alarmName" : "my_instance_alarm_1",
"severity" : "HIGH"
},
{
"alarmName" : "my_instance_alarm_2",
"severity" : "LOW"
}
],
"subComponents" : [
{
"subComponentType" : "AWS::EC2::Volume",
"alarmMetrics" : [
{
"alarmMetricName" : "VolumeQueueLength",
"monitor" : "true"
},
{
"alarmMetricName" : "VolumeThroughputPercentage",
"monitor" : "true"
},
{
"alarmMetricName" : "BurstBalance",
"monitor" : "true"
}]
}]
}
```
# Amazon Elastic Container Service (Amazon ECS)
Das folgende Beispiel zeigt Komponentenkonfigurationen im JSON-Format für den Amazon Elastic Container Service (Amazon ECS).
```
{
"alarmMetrics":[
{
"alarmMetricName":"CpuUtilized",
"monitor":true
},
{
"alarmMetricName":"MemoryUtilized",
"monitor":true
},
{
"alarmMetricName":"NetworkRxBytes",
"monitor":true
},
{
"alarmMetricName":"NetworkTxBytes",
"monitor":true
},
{
"alarmMetricName":"RunningTaskCount",
"monitor":true
},
{
"alarmMetricName":"PendingTaskCount",
"monitor":true
},
{
"alarmMetricName":"StorageReadBytes",
"monitor":true
},
{
"alarmMetricName":"StorageWriteBytes",
"monitor":true
}
],
"logs":[
{
"logGroupName":"/ecs/my-task-definition",
"logType":"APPLICATION",
"monitor":true
}
],
"subComponents":[
{
"subComponentType":"AWS::ElasticLoadBalancing::LoadBalancer",
"alarmMetrics":[
{
"alarmMetricName":"HTTPCode_Backend_4XX",
"monitor":true
},
{
"alarmMetricName":"HTTPCode_Backend_5XX",
"monitor":true
},
{
"alarmMetricName":"Latency",
"monitor":true
},
{
"alarmMetricName":"SurgeQueueLength",
"monitor":true
},
{
"alarmMetricName":"UnHealthyHostCount",
"monitor":true
}
]
},
{
"subComponentType":"AWS::ElasticLoadBalancingV2::LoadBalancer",
"alarmMetrics":[
{
"alarmMetricName":"HTTPCode_Target_4XX_Count",
"monitor":true
},
{
"alarmMetricName":"HTTPCode_Target_5XX_Count",
"monitor":true
},
{
"alarmMetricName":"TargetResponseTime",
"monitor":true
},
{
"alarmMetricName":"UnHealthyHostCount",
"monitor":true
}
]
},
{
"subComponentType":"AWS::EC2::Instance",
"alarmMetrics":[
{
"alarmMetricName":"CPUUtilization",
"monitor":true
},
{
"alarmMetricName":"StatusCheckFailed",
"monitor":true
},
{
"alarmMetricName":"disk_used_percent",
"monitor":true
},
{
"alarmMetricName":"mem_used_percent",
"monitor":true
}
],
"logs":[
{
"logGroupName":"my_log_group",
"logPath":"/mylog/path",
"logType":"APPLICATION",
"monitor":true
}
],
"processes" : [
{
"processName" : "my_process",
"alarmMetrics" : [
{
"alarmMetricName" : "procstat cpu_usage",
"monitor" : true
}, {
"alarmMetricName" : "procstat memory_rss",
"monitor" : true
}
]
}
],
"windowsEvents":[
{
"logGroupName":"my_log_group_2",
"eventName":"Application",
"eventLevels":[
"ERROR",
"WARNING",
"CRITICAL"
],
"monitor":true
}
]
},
{
"subComponentType":"AWS::EC2::Volume",
"alarmMetrics":[
{
"alarmMetricName":"VolumeQueueLength",
"monitor":"true"
},
{
"alarmMetricName":"VolumeThroughputPercentage",
"monitor":"true"
},
{
"alarmMetricName":"BurstBalance",
"monitor":"true"
}
]
}
]
}
```
**Anmerkung**
Der Abschnitt `subComponents` von `AWS::EC2::Instance` und `AWS::EC2::Volume` gilt nur für Amazon-ECS-Cluster mit ECS-Service oder ECS-Aufgabe, die auf dem EC2-Starttyp ausgeführt werden.
Der Abschnitt `windowsEvents` von `AWS::EC2::Instance` in `subComponents` gilt nur für Windows, das auf Amazon-EC2-Instances ausgeführt wird.
# Amazon-ECS-Dienstleistungen
Das folgende Beispiel zeigt Komponentenkonfigurationen im JSON-Format für einen Amazon-ECS-Service.
```
{
"alarmMetrics":[
{
"alarmMetricName":"CPUUtilization",
"monitor":true
},
{
"alarmMetricName":"MemoryUtilization",
"monitor":true
},
{
"alarmMetricName":"CpuUtilized",
"monitor":true
},
{
"alarmMetricName":"MemoryUtilized",
"monitor":true
},
{
"alarmMetricName":"NetworkRxBytes",
"monitor":true
},
{
"alarmMetricName":"NetworkTxBytes",
"monitor":true
},
{
"alarmMetricName":"RunningTaskCount",
"monitor":true
},
{
"alarmMetricName":"PendingTaskCount",
"monitor":true
},
{
"alarmMetricName":"StorageReadBytes",
"monitor":true
},
{
"alarmMetricName":"StorageWriteBytes",
"monitor":true
}
],
"logs":[
{
"logGroupName":"/ecs/my-task-definition",
"logType":"APPLICATION",
"monitor":true
}
],
"subComponents":[
{
"subComponentType":"AWS::ElasticLoadBalancing::LoadBalancer",
"alarmMetrics":[
{
"alarmMetricName":"HTTPCode_Backend_4XX",
"monitor":true
},
{
"alarmMetricName":"HTTPCode_Backend_5XX",
"monitor":true
},
{
"alarmMetricName":"Latency",
"monitor":true
},
{
"alarmMetricName":"SurgeQueueLength",
"monitor":true
},
{
"alarmMetricName":"UnHealthyHostCount",
"monitor":true
}
]
},
{
"subComponentType":"AWS::ElasticLoadBalancingV2::LoadBalancer",
"alarmMetrics":[
{
"alarmMetricName":"HTTPCode_Target_4XX_Count",
"monitor":true
},
{
"alarmMetricName":"HTTPCode_Target_5XX_Count",
"monitor":true
},
{
"alarmMetricName":"TargetResponseTime",
"monitor":true
},
{
"alarmMetricName":"UnHealthyHostCount",
"monitor":true
}
]
},
{
"subComponentType":"AWS::EC2::Instance",
"alarmMetrics":[
{
"alarmMetricName":"CPUUtilization",
"monitor":true
},
{
"alarmMetricName":"StatusCheckFailed",
"monitor":true
},
{
"alarmMetricName":"disk_used_percent",
"monitor":true
},
{
"alarmMetricName":"mem_used_percent",
"monitor":true
}
],
"logs":[
{
"logGroupName":"my_log_group",
"logPath":"/mylog/path",
"logType":"APPLICATION",
"monitor":true
}
],
"processes" : [
{
"processName" : "my_process",
"alarmMetrics" : [
{
"alarmMetricName" : "procstat cpu_usage",
"monitor" : true
}, {
"alarmMetricName" : "procstat memory_rss",
"monitor" : true
}
]
}
],
"windowsEvents":[
{
"logGroupName":"my_log_group_2",
"eventName":"Application",
"eventLevels":[
"ERROR",
"WARNING",
"CRITICAL"
],
"monitor":true
}
]
},
{
"subComponentType":"AWS::EC2::Volume",
"alarmMetrics":[
{
"alarmMetricName":"VolumeQueueLength",
"monitor":"true"
},
{
"alarmMetricName":"VolumeThroughputPercentage",
"monitor":"true"
},
{
"alarmMetricName":"BurstBalance",
"monitor":"true"
}
]
}
]
}
```
**Anmerkung**
Der Abschnitt `subComponents` von `AWS::EC2::Instance` und `AWS::EC2::Volume` gilt nur für Amazon ECS, das auf dem EC2-Starttyp ausgeführt wird.
Der Abschnitt `windowsEvents` von `AWS::EC2::Instance` in `subComponents` gilt nur für Windows, das auf Amazon-EC2-Instances ausgeführt wird.
# Amazon-ECS-Aufgaben
Das folgende Beispiel zeigt Komponentenkonfigurationen im JSON-Format für eine Amazon-ECS-Aufgabe.
```
{
"logs":[
{
"logGroupName":"/ecs/my-task-definition",
"logType":"APPLICATION",
"monitor":true
}
],
"processes" : [
{
"processName" : "my_process",
"alarmMetrics" : [
{
"alarmMetricName" : "procstat cpu_usage",
"monitor" : true
}, {
"alarmMetricName" : "procstat memory_rss",
"monitor" : true
}
]
}
]
}
```
# Amazon Elastic File System (Amazon EFS)
Das folgende Beispiel zeigt Komponentenkonfigurationen im JSON-Format für die Amazon EFS.
```
{
"alarmMetrics": [
{
"alarmMetricName": "BurstCreditBalance",
"monitor": true
},
{
"alarmMetricName": "PercentIOLimit",
"monitor": true
},
{
"alarmMetricName": "PermittedThroughput",
"monitor": true
},
{
"alarmMetricName": "MeteredIOBytes",
"monitor": true
},
{
"alarmMetricName": "TotalIOBytes",
"monitor": true
},
{
"alarmMetricName": "DataWriteIOBytes",
"monitor": true
},
{
"alarmMetricName": "DataReadIOBytes",
"monitor": true
},
{
"alarmMetricName": "MetadataIOBytes",
"monitor": true
},
{
"alarmMetricName": "ClientConnections",
"monitor": true
},
{
"alarmMetricName": "TimeSinceLastSync",
"monitor": true
},
{
"alarmMetricName": "Throughput",
"monitor": true
},
{
"alarmMetricName": "PercentageOfPermittedThroughputUtilization",
"monitor": true
},
{
"alarmMetricName": "ThroughputIOPS",
"monitor": true
},
{
"alarmMetricName": "PercentThroughputDataReadIOBytes",
"monitor": true
},
{
"alarmMetricName": "PercentThroughputDataWriteIOBytes",
"monitor": true
},
{
"alarmMetricName": "PercentageOfIOPSDataReadIOBytes",
"monitor": true
},
{
"alarmMetricName": "PercentageOfIOPSDataWriteIOBytes",
"monitor": true
},
{
"alarmMetricName": "AverageDataReadIOBytesSize",
"monitor": true
},
{
"alarmMetricName": "AverageDataWriteIOBytesSize",
"monitor": true
}
],
"logs": [
{
"logGroupName": "/aws/efs/utils",
"logType": "EFS_MOUNT_STATUS",
"monitor": true,
}
]
}
```
# Amazon FSx
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für Amazon FSx.
```
{
"alarmMetrics": [
{
"alarmMetricName": "DataReadBytes",
"monitor": true
},
{
"alarmMetricName": "DataWriteBytes",
"monitor": true
},
{
"alarmMetricName": "DataReadOperations",
"monitor": true
},
{
"alarmMetricName": "DataWriteOperations",
"monitor": true
},
{
"alarmMetricName": "MetadataOperations",
"monitor": true
},
{
"alarmMetricName": "FreeStorageCapacity",
"monitor": true
}
]
}
```
# Amazon Relational Database Service (RDS) Aurora MySQL
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für Amazon RDS Aurora MySQL.
```
{
"alarmMetrics": [
{
"alarmMetricName": "CPUUtilization",
"monitor": true
},
{
"alarmMetricName": "CommitLatency",
"monitor": true
}
],
"logs": [
{
"logType": "MYSQL",
"monitor": true,
},
{
"logType": "MYSQL_SLOW_QUERY",
"monitor": false
}
]
}
```
# Amazon-Relational-Database-Service(RDS)-Instance
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für eine Amazon-RDS-Instance.
```
{
"alarmMetrics" : [
{
"alarmMetricName" : "BurstBalance",
"monitor" : true
}, {
"alarmMetricName" : "WriteThroughput",
"monitor" : false
}
],
"alarms" : [
{
"alarmName" : "my_rds_instance_alarm",
"severity" : "MEDIUM"
}
]
}
```
# Amazon-Route-53-Zustandsprüfung
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für die Zustandsprüfung von Amazon Route 53.
```
{
"alarmMetrics": [
{
"alarmMetricName": "ChildHealthCheckHealthyCount",
"monitor": true
},
{
"alarmMetricName": "ConnectionTime",
"monitor": true
},
{
"alarmMetricName": "HealthCheckPercentageHealthy",
"monitor": true
},
{
"alarmMetricName": "HealthCheckStatus",
"monitor": true
},
{
"alarmMetricName": "SSLHandshakeTime",
"monitor": true
},
{
"alarmMetricName": "TimeToFirstByte",
"monitor": true
}
]
}
```
# Gehostete Zone von Amazon Route 53
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für eine von Amazon Route 53 gehostete Zone.
```
{
"alarmMetrics": [
{
"alarmMetricName": "DNSQueries",
"monitor": true
},
{
"alarmMetricName": "DNSSECInternalFailure",
"monitor": true
},
{
"alarmMetricName": "DNSSECKeySigningKeysNeedingAction",
"monitor": true
},
{
"alarmMetricName": "DNSSECKeySigningKeyMaxNeedingActionAge",
"monitor": true
},
{
"alarmMetricName": "DNSSECKeySigningKeyAge",
"monitor": true
}
],
"logs": [
{
"logGroupName":"/hosted-zone/logs",
"logType": "ROUTE53_DNS_PUBLIC_QUERY_LOGS",
"monitor": true
}
]
}
```
# Amazon Route 53 Resolver Endpunkt
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für Amazon Route 53 Resolver Endgeräte.
```
{
"alarmMetrics": [
{
"alarmMetricName": "EndpointHealthyENICount",
"monitor": true
},
{
"alarmMetricName": "EndpointUnHealthyENICount",
"monitor": true
},
{
"alarmMetricName": "InboundQueryVolume",
"monitor": true
},
{
"alarmMetricName": "OutboundQueryVolume",
"monitor": true
},
{
"alarmMetricName": "OutboundQueryAggregateVolume",
"monitor": true
}
]
}
```
# Amazon Route 53 Resolver Konfiguration der Abfrageprotokollierung
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für die Amazon Route 53 Resolver Konfiguration zur Abfrageprotokollierung.
```
{
"logs": [
{
"logGroupName": "/resolver-query-log-config/logs",
"logType": "ROUTE53_RESOLVER_QUERY_LOGS",
"monitor": true
}
]
}
```
# Amazon-S3-Bucket
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für ein Amazon S3 Bucket.
```
{
"alarmMetrics" : [
{
"alarmMetricName" : "ReplicationLatency",
"monitor" : true
}, {
"alarmMetricName" : "5xxErrors",
"monitor" : true
}, {
"alarmMetricName" : "BytesDownloaded"
"monitor" : true
}
]
}
```
# Amazon Simple Queue Service (SQS)
Die folgenden Beispiele zeigen Komponentenkonfigurationen im JSON-Format für den Amazon Simple Queue Service.
```
{
"alarmMetrics" : [
{
"alarmMetricName" : "ApproximateAgeOfOldestMessage"
}, {
"alarmMetricName" : "NumberOfEmptyReceives"
}
],
"alarms" : [
{
"alarmName" : "my_sqs_alarm",
"severity" : "MEDIUM"
}
]
}
```
# Amazon-SNS-Thema
Das folgende Beispiel zeigt Komponentenkonfigurationen im JSON-Format für das Amazon-SNS-Thema.
```
{
"alarmMetrics": [
{
"alarmMetricName": "NumberOfNotificationsFailed",
"monitor": true
},
{
"alarmMetricName": "NumberOfNotificationsFilteredOut-InvalidAttributes",
"monitor": true
},
{
"alarmMetricName": "NumberOfNotificationsFilteredOut-NoMessageAttributes",
"monitor": true
},
{
"alarmMetricName": "NumberOfNotificationsFailedToRedriveToDlq",
"monitor": true
}
]
}
```
# Amazon Virtual Private Cloud (Amazon VPC)
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für Amazon VPC.
```
{
"alarmMetrics": [
{
"alarmMetricName": "NetworkAddressUsage",
"monitor": true
},
{
"alarmMetricName": "NetworkAddressUsagePeered",
"monitor": true
},
{
"alarmMetricName": "VPCFirewallQueryVolume",
"monitor": true
}
]
}
```
# Gateways von Amazon VPC Network Address Translation (NAT)
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für NAT-Gateways.
```
{
"alarmMetrics": [
{
"alarmMetricName": "ErrorPortAllocation",
"monitor": true
},
{
"alarmMetricName": "IdleTimeoutCount",
"monitor": true
}
]
}
```
# API-Gateway-REST-API-Phasen
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für API-Gateway-REST-API-Phasen.
```
{
"alarmMetrics" : [
{
"alarmMetricName" : "4XXError",
"monitor" : true
},
{
"alarmMetricName" : "5XXError",
"monitor" : true
}
],
"logs" : [
{
"logType" : "API_GATEWAY_EXECUTION",
"monitor" : true
},
{
"logType" : "API_GATEWAY_ACCESS",
"monitor" : true
}
]
}
```
# Application Elastic Load Balancing
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für Application Elastic Load Balancing.
```
{
"alarmMetrics": [
{
"alarmMetricName": "ActiveConnectionCount",
}, {
"alarmMetricName": "TargetResponseTime"
}
],
"subComponents": [
{
"subComponentType": "AWS::EC2::Instance",
"alarmMetrics": [
{
"alarmMetricName": "CPUUtilization",
}, {
"alarmMetricName": "StatusCheckFailed"
}
],
"logs": [
{
"logGroupName": "my_log_group",
"logPath": "C:\\LogFolder\\*",
"logType": "APPLICATION",
}
],
"windowsEvents": [
{
"logGroupName": "my_log_group_2",
"eventName": "Application",
"eventLevels": [ "ERROR", "WARNING", "CRITICAL" ]
}
]
}, {
"subComponentType": "AWS::EC2::Volume",
"alarmMetrics": [
{
"alarmMetricName": "VolumeQueueLength",
}, {
"alarmMetricName": "BurstBalance"
}
]
}
],
"alarms": [
{
"alarmName": "my_alb_alarm",
"severity": "LOW"
}
]
}
```
# AWS Lambda Funktion
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für eine AWS Lambda -Funktion.
```
{
"alarmMetrics": [
{
"alarmMetricName": "Errors",
"monitor": true
},
{
"alarmMetricName": "Throttles",
"monitor": true
},
{
"alarmMetricName": "IteratorAge",
"monitor": true
},
{
"alarmMetricName": "Duration",
"monitor": true
}
],
"logs": [
{
"logType": "DEFAULT",
"monitor": true
}
]
}
```
# AWS Network Firewall Regelgruppe
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für eine AWS Network Firewall -Regelgruppe.
```
{
"alarmMetrics": [
{
"alarmMetricName": "FirewallRuleGroupQueryVolume",
"monitor": true
}
]
}
```
# AWS Network Firewall Zuordnung von Regelgruppen
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für eine AWS Network Firewall -Regelgruppenzuordnung.
```
{
"alarmMetrics": [
{
"alarmMetricName": "FirewallRuleGroupQueryVolume",
"monitor": true
}
]
}
```
# AWS Step Functions
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für AWS Step Functions.
```
{
"alarmMetrics": [
{
"alarmMetricName": "ExecutionsFailed",
"monitor": true
},
{
"alarmMetricName": "LambdaFunctionsFailed",
"monitor": true
},
{
"alarmMetricName": "ProvisionedRefillRate",
"monitor": true
}
],
"logs": [
{
"logGroupName": "/aws/states/HelloWorld-Logs",
"logType": "STEP_FUNCTION",
"monitor": true,
}
]
}
```
# Vom Kunden gruppierte Amazon-EC2-Instances
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für eine vom Kunden gruppierte Amazon-EC2-Instance.
```
{
"subComponents": [
{
"subComponentType": "AWS::EC2::Instance",
"alarmMetrics": [
{
"alarmMetricName": "CPUUtilization",
},
{
"alarmMetricName": "StatusCheckFailed"
}
],
"logs": [
{
"logGroupName": "my_log_group",
"logPath": "C:\\LogFolder\\*",
"logType": "APPLICATION",
}
],
"processes": [
{
"processName": "my_process",
"alarmMetrics": [
{
"alarmMetricName": "procstat cpu_usage",
"monitor": true
}, {
"alarmMetricName": "procstat memory_rss",
"monitor": true
}
]
}
],
"windowsEvents": [
{
"logGroupName": "my_log_group_2",
"eventName": "Application",
"eventLevels": [ "ERROR", "WARNING", "CRITICAL" ]
}
]
}, {
"subComponentType": "AWS::EC2::Volume",
"alarmMetrics": [
{
"alarmMetricName": "VolumeQueueLength",
}, {
"alarmMetricName": "BurstBalance"
}
]
}
],
"alarms": [
{
"alarmName": "my_alarm",
"severity": "MEDIUM"
}
]
}
```
# Elastic Load Balancing
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für Elastic Load Balancing.
```
{
"alarmMetrics": [
{
"alarmMetricName": "EstimatedALBActiveConnectionCount"
}, {
"alarmMetricName": "HTTPCode_Backend_5XX"
}
],
"subComponents": [
{
"subComponentType": "AWS::EC2::Instance",
"alarmMetrics": [
{
"alarmMetricName": "CPUUtilization"
}, {
"alarmMetricName": "StatusCheckFailed"
}
],
"logs": [
{
"logGroupName": "my_log_group",
"logPath": "C:\\LogFolder\\*",
"logType": "APPLICATION"
}
],
"processes": [
{
"processName": "my_process",
"alarmMetrics": [
{
"alarmMetricName": "procstat cpu_usage",
"monitor": true
}, {
"alarmMetricName": "procstat memory_rss",
"monitor": true
}
]
}
],
"windowsEvents": [
{
"logGroupName": "my_log_group_2",
"eventName": "Application",
"eventLevels": [ "ERROR", "WARNING", "CRITICAL" ],
"monitor": true
}
]
}, {
"subComponentType": "AWS::EC2::Volume",
"alarmMetrics": [
{
"alarmMetricName": "VolumeQueueLength"
}, {
"alarmMetricName": "BurstBalance"
}
]
}
],
"alarms": [
{
"alarmName": "my_elb_alarm",
"severity": "HIGH"
}
]
}
```
# Java
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für Java.
```
{
"alarmMetrics": [ {
"alarmMetricName": "java_lang_threading_threadcount",
"monitor": true
},
{
"alarmMetricName": "java_lang_memory_heapmemoryusage_used",
"monitor": true
},
{
"alarmMetricName": "java_lang_memory_heapmemoryusage_committed",
"monitor": true
}],
"logs": [ ],
"JMXPrometheusExporter": {
"hostPort": "8686",
"prometheusPort": "9404"
}
}
```
**Anmerkung**
Application Insights unterstützt die Konfiguration der Authentifizierung für Prometheus JMX Exporter nicht. Informationen zum Einrichten der Authentifizierung finden Sie in der[ Beispielkonfiguration des Prometheus-JMX-Exporters](https://github.com/prometheus/jmx_exporter#configuration).
# Kubernetes auf Amazon EC2
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für Kubernetes auf Amazon EC2.
```
{
"alarmMetrics":[
{
"alarmMetricName":"cluster_failed_node_count",
"monitor":true
},
{
"alarmMetricName":"node_cpu_reserved_capacity",
"monitor":true
},
{
"alarmMetricName":"node_cpu_utilization",
"monitor":true
},
{
"alarmMetricName":"node_filesystem_utilization",
"monitor":true
},
{
"alarmMetricName":"node_memory_reserved_capacity",
"monitor":true
},
{
"alarmMetricName":"node_memory_utilization",
"monitor":true
},
{
"alarmMetricName":"node_network_total_bytes",
"monitor":true
},
{
"alarmMetricName":"pod_cpu_reserved_capacity",
"monitor":true
},
{
"alarmMetricName":"pod_cpu_utilization",
"monitor":true
},
{
"alarmMetricName":"pod_cpu_utilization_over_pod_limit",
"monitor":true
},
{
"alarmMetricName":"pod_memory_reserved_capacity",
"monitor":true
},
{
"alarmMetricName":"pod_memory_utilization",
"monitor":true
},
{
"alarmMetricName":"pod_memory_utilization_over_pod_limit",
"monitor":true
},
{
"alarmMetricName":"pod_network_rx_bytes",
"monitor":true
},
{
"alarmMetricName":"pod_network_tx_bytes",
"monitor":true
}
],
"logs":[
{
"logGroupName":"/aws/containerinsights/kubernetes/application",
"logType":"APPLICATION",
"monitor":true,
"encoding":"utf-8"
}
],
"subComponents":[
{
"subComponentType":"AWS::EC2::Instance",
"alarmMetrics":[
{
"alarmMetricName":"CPUUtilization",
"monitor":true
},
{
"alarmMetricName":"StatusCheckFailed",
"monitor":true
},
{
"alarmMetricName":"disk_used_percent",
"monitor":true
},
{
"alarmMetricName":"mem_used_percent",
"monitor":true
}
],
"logs":[
{
"logGroupName":"APPLICATION-KubernetesClusterOnEC2-IAD",
"logPath":"",
"logType":"APPLICATION",
"monitor":true,
"encoding":"utf-8"
}
],
"processes" : [
{
"processName" : "my_process",
"alarmMetrics" : [
{
"alarmMetricName" : "procstat cpu_usage",
"monitor" : true
}, {
"alarmMetricName" : "procstat memory_rss",
"monitor" : true
}
]
}
]
},
{
"subComponentType":"AWS::EC2::Volume",
"alarmMetrics":[
{
"alarmMetricName":"VolumeReadBytes",
"monitor":true
},
{
"alarmMetricName":"VolumeWriteBytes",
"monitor":true
},
{
"alarmMetricName":"VolumeReadOps",
"monitor":true
},
{
"alarmMetricName":"VolumeWriteOps",
"monitor":true
},
{
"alarmMetricName":"VolumeQueueLength",
"monitor":true
},
{
"alarmMetricName":"BurstBalance",
"monitor":true
}
]
}
]
}
```
# RDS MariaDB und RDS MySQL
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für RDS MariaDB und RDS MySQL.
```
{
"alarmMetrics": [
{
"alarmMetricName": "CPUUtilization",
"monitor": true
}
],
"logs": [
{
"logType": "MYSQL",
"monitor": true,
},
{
"logType": "MYSQL_SLOW_QUERY",
"monitor": false
}
]
}
```
# RDS Oracle
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für RDS Oracle.
```
{
"alarmMetrics": [
{
"alarmMetricName": "CPUUtilization",
"monitor": true
}
],
"logs": [
{
"logType": "ORACLE_ALERT",
"monitor": true,
},
{
"logType": "ORACLE_LISTENER",
"monitor": false
}
]
}
```
# RDS PostgreSQL
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für RDS PostgreSQL.
```
{
"alarmMetrics": [
{
"alarmMetricName": "CPUUtilization",
"monitor": true
}
],
"logs": [
{
"logType": "POSTGRESQL",
"monitor": true
}
]
}
```
# SAP ASE auf Amazon EC2
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für SAP ASE auf Amazon EC2.
```
{
"subComponents": [
{
"subComponentType": "AWS::EC2::Instance",
"alarmMetrics": [
{
"alarmMetricName": "asedb_database_availability",
"monitor": true
},
{
"alarmMetricName": "asedb_trunc_log_on_chkpt_enabled",
"monitor": true
},
{
"alarmMetricName": "asedb_last_db_backup_age_in_days",
"monitor": true
},
{
"alarmMetricName": "asedb_last_transaction_log_backup_age_in_hours",
"monitor": true
},
{
"alarmMetricName": "asedb_suspected_database",
"monitor": true
},
{
"alarmMetricName": "asedb_db_space_usage_percent",
"monitor": true
},
{
"alarmMetricName": "asedb_db_log_space_usage_percent",
"monitor": true
},
{
"alarmMetricName": "asedb_locked_login",
"monitor": true
},
{
"alarmMetricName": "asedb_data_cache_hit_ratio",
"monitor": true
}
],
"logs": [
{
"logGroupName": "SAP_ASE_SERVER_LOGS-my-resource-group",
"logPath": "/sybase/SY2/ASE-*/install/SY2.log",
"logType": "SAP_ASE_SERVER_LOGS",
"monitor": true,
"encoding": "utf-8"
},
{
"logGroupName": "SAP_ASE_BACKUP_SERVER_LOGS-my-resource-group",
"logPath": "/sybase/SY2/ASE-*/install/SY2_BS.log",
"logType": "SAP_ASE_BACKUP_SERVER_LOGS",
"monitor": true,
"encoding": "utf-8"
}
],
"sapAsePrometheusExporter": {
"sapAseSid": "ASE",
"sapAsePort": "4901",
"sapAseSecretName": "ASE_DB_CREDS",
"prometheusPort": "9399",
"agreeToEnableASEMonitoring": true
}
```
# SAP ASE bei Amazon EC2 mit hoher Verfügbarkeit
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für SAP ASE auf Amazon EC2 mit hoher Verfügbarkeit.
```
{
"subComponents": [
{
"subComponentType": "AWS::EC2::Instance",
"alarmMetrics": [
{
"alarmMetricName": "asedb_database_availability",
"monitor": true
},
{
"alarmMetricName": "asedb_trunc_log_on_chkpt_enabled",
"monitor": true
},
{
"alarmMetricName": "asedb_last_db_backup_age_in_days",
"monitor": true
},
{
"alarmMetricName": "asedb_last_transaction_log_backup_age_in_hours",
"monitor": true
},
{
"alarmMetricName": "asedb_suspected_database",
"monitor": true
},
{
"alarmMetricName": "asedb_db_space_usage_percent",
"monitor": true
},
{
"alarmMetricName": "asedb_ha_replication_state",
"monitor": true
},
{
"alarmMetricName": "asedb_ha_replication_mode",
"monitor": true
},
{
"alarmMetricName": "asedb_ha_replication_latency_in_minutes",
"monitor": true
}
],
"logs": [
{
"logGroupName": "SAP_ASE_SERVER_LOGS-my-resource-group",
"logPath": "/sybase/SY2/ASE-*/install/SY2.log",
"logType": "SAP_ASE_SERVER_LOGS",
"monitor": true,
"encoding": "utf-8"
},
{
"logGroupName": "SAP_ASE_BACKUP_SERVER_LOGS-my-resource-group",
"logPath": "/sybase/SY2/ASE-*/install/SY2_BS.log",
"logType": "SAP_ASE_BACKUP_SERVER_LOGS",
"monitor": true,
"encoding": "utf-8"
},
{
"logGroupName": "SAP_ASE_REP_SERVER_LOGS-my-resource-group",
"logPath": "/sybase/SY2/DM/repservername/repservername.log",
"logType": "SAP_ASE_REP_SERVER_LOGS",
"monitor": true,
"encoding": "utf-8"
},
{
"logGroupName": "SAP_ASE_RMA_AGENT_LOGS-my-resource-group",
"logPath": "/sybase/SY2/DM/RMA-*/instances/AgentContainer/logs/",
"logType": "SAP_ASE_RMA_AGENT_LOGS",
"monitor": true,
"encoding": "utf-8"
},
{
"logGroupName": "SAP_ASE_FAULT_MANAGER_LOGS-my-resource-group",
"logPath": "/opt/sap/FaultManager/dev_sybdbfm",
"logType": "SAP_ASE_FAULT_MANAGER_LOGS",
"monitor": true,
"encoding": "utf-8"
}
],
"sapAsePrometheusExporter": {
"sapAseSid": "ASE",
"sapAsePort": "4901",
"sapAseSecretName": "ASE_DB_CREDS",
"prometheusPort": "9399",
"agreeToEnableASEMonitoring": true
}
```
# SAP HANA bei Amazon EC2
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für SAP HANA auf Amazon EC2.
```
{
"subComponents": [
{
"subComponentType": "AWS::EC2::Instance",
"alarmMetrics": [
{
"alarmMetricName": "hanadb_server_startup_time_variations_seconds",
"monitor": true
},
{
"alarmMetricName": "hanadb_level_5_alerts_count",
"monitor": true
},
{
"alarmMetricName": "hanadb_level_4_alerts_count",
"monitor": true
},
{
"alarmMetricName": "hanadb_out_of_memory_events_count",
"monitor": true
},
{
"alarmMetricName": "hanadb_max_trigger_read_ratio_percent",
"monitor": true
},
{
"alarmMetricName": "hanadb_table_allocation_limit_used_percent",
"monitor": true
},
{
"alarmMetricName": "hanadb_cpu_usage_percent",
"monitor": true
},
{
"alarmMetricName": "hanadb_plan_cache_hit_ratio_percent",
"monitor": true
},
{
"alarmMetricName": "hanadb_last_data_backup_age_days",
"monitor": true
}
],
"logs": [
{
"logGroupName": "SAP_HANA_TRACE-my-resourge-group",
"logPath": "/usr/sap/HDB/HDB00/*/trace/*.trc",
"logType": "SAP_HANA_TRACE",
"monitor": true,
"encoding": "utf-8"
},
{
"logGroupName": "SAP_HANA_LOGS-my-resource-group",
"logPath": "/usr/sap/HDB/HDB00/*/trace/*.log",
"logType": "SAP_HANA_LOGS",
"monitor": true,
"encoding": "utf-8"
}
]
}
],
"hanaPrometheusExporter": {
"hanaSid": "HDB",
"hanaPort": "30013",
"hanaSecretName": "HANA_DB_CREDS",
"prometheusPort": "9668"
}
}
```
# SAP HANA bei Amazon EC2 mit hoher Verfügbarkeit
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für SAP HANA auf Amazon EC2 mit hoher Verfügbarkeit.
```
{
"subComponents": [
{
"subComponentType": "AWS::EC2::Instance",
"alarmMetrics": [
{
"alarmMetricName": "hanadb_server_startup_time_variations_seconds",
"monitor": true
},
{
"alarmMetricName": "hanadb_level_5_alerts_count",
"monitor": true
},
{
"alarmMetricName": "hanadb_level_4_alerts_count",
"monitor": true
},
{
"alarmMetricName": "hanadb_out_of_memory_events_count",
"monitor": true
},
{
"alarmMetricName": "ha_cluster_pacemaker_stonith_enabled",
"monitor": true
}
],
"logs": [
{
"logGroupName": "SAP_HANA_TRACE-my-resourge-group",
"logPath": "/usr/sap/HDB/HDB00/*/trace/*.trc",
"logType": "SAP_HANA_TRACE",
"monitor": true,
"encoding": "utf-8"
},
{
"logGroupName": "SAP_HANA_HIGH_AVAILABILITY-my-resource-group",
"logPath": "/var/log/pacemaker/pacemaker.log",
"logType": "SAP_HANA_HIGH_AVAILABILITY",
"monitor": true,
"encoding": "utf-8"
}
]
}
],
"hanaPrometheusExporter": {
"hanaSid": "HDB",
"hanaPort": "30013",
"hanaSecretName": "HANA_DB_CREDS",
"prometheusPort": "9668"
},
"haClusterPrometheusExporter": {
"prometheusPort": "9664"
}
}
```
# SAP NetWeaver auf Amazon EC2
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für SAP NetWeaver auf Amazon EC2.
```
{
"subComponents": [
{
"subComponentType": "AWS::EC2::Instance",
"alarmMetrics": [
{
"alarmMetricName": "CPUUtilization",
"monitor": true
},
{
"alarmMetricName": "StatusCheckFailed",
"monitor": true
},
{
"alarmMetricName": "disk_used_percent",
"monitor": true
},
{
"alarmMetricName": "mem_used_percent",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_ResponseTime",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_ResponseTimeDialog",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_ResponseTimeDialogRFC",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_DBRequestTime",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_LongRunners",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_AbortedJobs",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_BasisSystem",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_Database",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_Security",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_System",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_QueueTime",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_Availability",
"monitor": true
},
{
"alarmMetricName": "sap_start_service_processes",
"monitor": true
},
{
"alarmMetricName": "sap_dispatcher_queue_now",
"monitor": true
},
{
"alarmMetricName": "sap_dispatcher_queue_max",
"monitor": true
},
{
"alarmMetricName": "sap_enqueue_server_locks_max",
"monitor": true
},
{
"alarmMetricName": "sap_enqueue_server_locks_now",
"monitor": true
},
{
"alarmMetricName": "sap_enqueue_server_locks_state",
"monitor": true
},
{
"alarmMetricName": "sap_enqueue_server_replication_state",
"monitor": true
}
],
"logs": [
{
"logGroupName": "SAP_NETWEAVER_DEV_TRACE_LOGS-NetWeaver-ML4",
"logPath": "/usr/sap/ML4/*/work/dev_w*",
"logType": "SAP_NETWEAVER_DEV_TRACE_LOGS",
"monitor": true,
"encoding": "utf-8"
}
]
}
],
"netWeaverPrometheusExporter": {
"sapSid": "ML4",
"instanceNumbers": [
"00",
"11"
],
"prometheusPort": "9680"
}
}
```
# NetWeaver SAP-Hochverfügbarkeit auf Amazon EC2
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für SAP NetWeaver High Availability auf Amazon EC2.
```
{
"subComponents": [
{
"subComponentType": "AWS::EC2::Instance",
"alarmMetrics": [
{
"alarmMetricName": "ha_cluster_corosync_ring_errors",
"monitor": true
},
{
"alarmMetricName": "ha_cluster_pacemaker_fail_count",
"monitor": true
},
{
"alarmMetricName": "sap_HA_check_failover_config_state",
"monitor": true
},
{
"alarmMetricName": "sap_HA_get_failover_config_HAActive",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_AbortedJobs",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_Availability",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_BasisSystem",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_DBRequestTime",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_Database",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_FrontendResponseTime",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_LongRunners",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_QueueTime",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_ResponseTime",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_ResponseTimeDialog",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_ResponseTimeDialogRFC",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_Security",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_Shortdumps",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_SqlError",
"monitor": true
},
{
"alarmMetricName": "sap_alerts_System",
"monitor": true
},
{
"alarmMetricName": "sap_enqueue_server_replication_state",
"monitor": true
},
{
"alarmMetricName": "sap_start_service_processes",
"monitor": true
}
],
"logs": [
{
"logGroupName": "SAP_NETWEAVER_DEV_TRACE_LOGS-NetWeaver-PR1",
"logPath": "/usr/sap//D*/work/dev_w*",
"logType": "SAP_NETWEAVER_DEV_TRACE_LOGS",
"monitor": true,
"encoding": "utf-8"
}
]
}
],
"haClusterPrometheusExporter": {
"prometheusPort": "9664"
},
"netWeaverPrometheusExporter": {
"sapSid": "PR1",
"instanceNumbers": [
"11",
"12"
],
"prometheusPort": "9680"
}
}
```
# SQL Always On-Verfügbarkeitsgruppe
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für eine SQL Always On-Verfügbarkeitsgruppe.
```
{
"subComponents" : [ {
"subComponentType" : "AWS::EC2::Instance",
"alarmMetrics" : [ {
"alarmMetricName" : "CPUUtilization",
"monitor" : true
}, {
"alarmMetricName" : "StatusCheckFailed",
"monitor" : true
}, {
"alarmMetricName" : "Processor % Processor Time",
"monitor" : true
}, {
"alarmMetricName" : "Memory % Committed Bytes In Use",
"monitor" : true
}, {
"alarmMetricName" : "Memory Available Mbytes",
"monitor" : true
}, {
"alarmMetricName" : "Paging File % Usage",
"monitor" : true
}, {
"alarmMetricName" : "System Processor Queue Length",
"monitor" : true
}, {
"alarmMetricName" : "Network Interface Bytes Total/sec",
"monitor" : true
}, {
"alarmMetricName" : "PhysicalDisk % Disk Time",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Buffer Manager Buffer cache hit ratio",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Buffer Manager Page life expectancy",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:General Statistics Processes blocked",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:General Statistics User Connections",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Locks Number of Deadlocks/sec",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:SQL Statistics Batch Requests/sec",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Database Replica File Bytes Received/sec",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Database Replica Log Bytes Received/sec",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Database Replica Log remaining for undo",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Database Replica Log Send Queue",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Database Replica Mirrored Write Transaction/sec",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Database Replica Recovery Queue",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Database Replica Redo Bytes Remaining",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Database Replica Redone Bytes/sec",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Database Replica Total Log requiring undo",
"monitor" : true
}, {
"alarmMetricName" : "SQLServer:Database Replica Transaction Delay",
"monitor" : true
} ],
"windowsEvents" : [ {
"logGroupName" : "WINDOWS_EVENTS-Application-",
"eventName" : "Application",
"eventLevels" : [ "WARNING", "ERROR", "CRITICAL", "INFORMATION" ],
"monitor" : true
}, {
"logGroupName" : "WINDOWS_EVENTS-System-",
"eventName" : "System",
"eventLevels" : [ "WARNING", "ERROR", "CRITICAL" ],
"monitor" : true
}, {
"logGroupName" : "WINDOWS_EVENTS-Security-",
"eventName" : "Security",
"eventLevels" : [ "WARNING", "ERROR", "CRITICAL" ],
"monitor" : true
} ],
"logs" : [ {
"logGroupName" : "SQL_SERVER_ALWAYSON_AVAILABILITY_GROUP-",
"logPath" : "C:\\Program Files\\Microsoft SQL Server\\MSSQL**.MSSQLSERVER\\MSSQL\\Log\\ERRORLOG",
"logType" : "SQL_SERVER",
"monitor" : true,
"encoding" : "utf-8"
} ]
}, {
"subComponentType" : "AWS::EC2::Volume",
"alarmMetrics" : [ {
"alarmMetricName" : "VolumeReadBytes",
"monitor" : true
}, {
"alarmMetricName" : "VolumeWriteBytes",
"monitor" : true
}, {
"alarmMetricName" : "VolumeReadOps",
"monitor" : true
}, {
"alarmMetricName" : "VolumeWriteOps",
"monitor" : true
}, {
"alarmMetricName" : "VolumeQueueLength",
"monitor" : true
}, {
"alarmMetricName" : "VolumeThroughputPercentage",
"monitor" : true
}, {
"alarmMetricName" : "BurstBalance",
"monitor" : true
} ]
} ]
}
```
# SQL-Failoverclusterinstance
Das folgende Beispiel zeigt eine Komponentenkonfiguration im JSON-Format für eine SQL-Failover-Cluster-Instance.
```
{
"subComponents" : [ {
"subComponentType" : "AWS::EC2::Instance",
"alarmMetrics" : [ {
"alarmMetricName" : "CPUUtilization",
"monitor" : true
}, {
"alarmMetricName" : "StatusCheckFailed",
"monitor" : true
}, {
"alarmMetricName" : "Processor % Processor Time",
"monitor" : true
}, {
"alarmMetricName" : "Memory % Committed Bytes In Use",
"monitor" : true
}, {
"alarmMetricName" : "Memory Available Mbytes",
"monitor" : true
}, {
"alarmMetricName" : "Paging File % Usage",
"monitor" : true
}, {
"alarmMetricName" : "System Processor Queue Length",
"monitor" : true
}, {
"alarmMetricName" : "Network Interface Bytes Total/sec",
"monitor" : true
}, {
"alarmMetricName" : "PhysicalDisk % Disk Time",
"monitor" : true
}, {
"alarmMetricName" : "Bytes Received/sec",
"monitor" : true
}, {
"alarmMetricName" : "Normal Messages Queue Length/sec",
"monitor" : true
}, {
"alarmMetricName" : "Urgent Message Queue Length/se",
"monitor" : true
}, {
"alarmMetricName" : "Reconnect Count",
"monitor" : true
}, {
"alarmMetricName" : "Unacknowledged Message Queue Length/sec",
"monitor" : true
}, {
"alarmMetricName" : "Messages Outstanding",
"monitor" : true
}, {
"alarmMetricName" : "Messages Sent/sec",
"monitor" : true
}, {
"alarmMetricName" : "Database Update Messages/sec",
"monitor" : true
}, {
"alarmMetricName" : "Update Messages/sec",
"monitor" : true
}, {
"alarmMetricName" : "Flushes/sec",
"monitor" : true
}, {
"alarmMetricName" : "Crypto Checkpoints Saved/sec",
"monitor" : true
}, {
"alarmMetricName" : "Crypto Checkpoints Restored/sec",
"monitor" : true
}, {
"alarmMetricName" : "Registry Checkpoints Restored/sec",
"monitor" : true
}, {
"alarmMetricName" : "Registry Checkpoints Saved/sec",
"monitor" : true
}, {
"alarmMetricName" : "Cluster API Calls/sec",
"monitor" : true
}, {
"alarmMetricName" : "Resource API Calls/sec",
"monitor" : true
}, {
"alarmMetricName" : "Cluster Handles/sec",
"monitor" : true
}, {
"alarmMetricName" : "Resource Handles/sec",
"monitor" : true
} ],
"windowsEvents" : [ {
"logGroupName" : "WINDOWS_EVENTS-Application-",
"eventName" : "Application",
"eventLevels" : [ "WARNING", "ERROR", "CRITICAL"],
"monitor" : true
}, {
"logGroupName" : "WINDOWS_EVENTS-System-",
"eventName" : "System",
"eventLevels" : [ "WARNING", "ERROR", "CRITICAL", "INFORMATION" ],
"monitor" : true
}, {
"logGroupName" : "WINDOWS_EVENTS-Security-",
"eventName" : "Security",
"eventLevels" : [ "WARNING", "ERROR", "CRITICAL" ],
"monitor" : true
} ],
"logs" : [ {
"logGroupName" : "SQL_SERVER_FAILOVER_CLUSTER_INSTANCE-",
"logPath" : "\\\\amznfsxjmzbykwn.mydomain.aws\\SQLDB\\MSSQL**.MSSQLSERVER\\MSSQL\\Log\\ERRORLOG",
"logType" : "SQL_SERVER",
"monitor" : true,
"encoding" : "utf-8"
} ]
}, {
"subComponentType" : "AWS::EC2::Volume",
"alarmMetrics" : [ {
"alarmMetricName" : "VolumeReadBytes",
"monitor" : true
}, {
"alarmMetricName" : "VolumeWriteBytes",
"monitor" : true
}, {
"alarmMetricName" : "VolumeReadOps",
"monitor" : true
}, {
"alarmMetricName" : "VolumeWriteOps",
"monitor" : true
}, {
"alarmMetricName" : "VolumeQueueLength",
"monitor" : true
}, {
"alarmMetricName" : "VolumeThroughputPercentage",
"monitor" : true
}, {
"alarmMetricName" : "BurstBalance",
"monitor" : true
} ]
} ]
}
```