question
stringlengths 1.03k
1.62k
| answer
stringclasses 2
values |
|---|---|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-364a1e6f",
"description": "High shipping queue processing time",
"timestamp": "2024-01-18T23:00:00Z",
"severity": "critical",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1258,
"threshold": 500,
"queue_depth": 2544
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-eb0fee65",
"description": "Label generation service degraded",
"timestamp": "2024-01-18T23:02:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 2656,
"threshold": 1000,
"carrier": "usps"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-364a1e6f",
"description": "High shipping queue processing time",
"timestamp": "2024-01-18T23:00:00Z",
"severity": "critical",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1258,
"threshold": 500,
"queue_depth": 2544
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-b0699d0d",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-01-18T23:06:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 7.8297508031457035,
"threshold": 5
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 6.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e8fd074c",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-01-18T23:01:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 22.872144855931374,
"threshold": 5,
"error_type": "CarrierAPIException"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-eb0fee65",
"description": "Label generation service degraded",
"timestamp": "2024-01-18T23:02:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 2656,
"threshold": 1000,
"carrier": "usps"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 1.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e8fd074c",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-01-18T23:01:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 22.872144855931374,
"threshold": 5,
"error_type": "CarrierAPIException"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-b0699d0d",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-01-18T23:06:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 7.8297508031457035,
"threshold": 5
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-eb0fee65",
"description": "Label generation service degraded",
"timestamp": "2024-01-18T23:02:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 2656,
"threshold": 1000,
"carrier": "usps"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-b0699d0d",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-01-18T23:06:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 7.8297508031457035,
"threshold": 5
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e06919a5",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-19T03:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 157,
"threshold": 20,
"gateway": "stripe"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-c53f55f2",
"description": "High refund processing latency",
"timestamp": "2024-01-19T03:01:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 12999,
"threshold": 5000,
"refund_type": "full"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 1.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e06919a5",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-19T03:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 157,
"threshold": 20,
"gateway": "stripe"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-21d319e3",
"description": "Increased refund failure rate",
"timestamp": "2024-01-19T03:06:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 16.092576568934412,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 6.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e06919a5",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-19T03:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 157,
"threshold": 20,
"gateway": "stripe"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-ddae6d06",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-19T03:10:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 6.1324752850139355,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 10.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c53f55f2",
"description": "High refund processing latency",
"timestamp": "2024-01-19T03:01:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 12999,
"threshold": 5000,
"refund_type": "full"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-21d319e3",
"description": "Increased refund failure rate",
"timestamp": "2024-01-19T03:06:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 16.092576568934412,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c53f55f2",
"description": "High refund processing latency",
"timestamp": "2024-01-19T03:01:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 12999,
"threshold": 5000,
"refund_type": "full"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-ddae6d06",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-19T03:10:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 6.1324752850139355,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 9.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-21d319e3",
"description": "Increased refund failure rate",
"timestamp": "2024-01-19T03:06:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 16.092576568934412,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-ddae6d06",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-19T03:10:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 6.1324752850139355,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-f802072a",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-01-19T04:00:00Z",
"severity": "critical",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 89.04481587909223,
"threshold": 80
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-eaac6f96",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-01-19T04:02:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 97.41591108951611,
"total_connections": 100,
"available_connections": 3
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-f802072a",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-01-19T04:00:00Z",
"severity": "critical",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 89.04481587909223,
"threshold": 80
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-26c19bb5",
"description": "High query latency on returns-db-01",
"timestamp": "2024-01-19T04:06:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 1691.234968567048,
"threshold": 200,
"query_type": "INSERT"
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 6.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-eaac6f96",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-01-19T04:02:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 97.41591108951611,
"total_connections": 100,
"available_connections": 3
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-26c19bb5",
"description": "High query latency on returns-db-01",
"timestamp": "2024-01-19T04:06:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 1691.234968567048,
"threshold": 200,
"query_type": "INSERT"
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-360cb330",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-01-19T10:00:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 21.815379090013238,
"threshold": 5,
"error_type": "CarrierAPIException"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-198733a2",
"description": "High shipping queue processing time",
"timestamp": "2024-01-19T10:01:00Z",
"severity": "medium",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1098,
"threshold": 500,
"queue_depth": 1619
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 1.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-360cb330",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-01-19T10:00:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 21.815379090013238,
"threshold": 5,
"error_type": "CarrierAPIException"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-f351ccc0",
"description": "Label generation service degraded",
"timestamp": "2024-01-19T10:05:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1712,
"threshold": 1000,
"carrier": "fedex"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-360cb330",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-01-19T10:00:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 21.815379090013238,
"threshold": 5,
"error_type": "CarrierAPIException"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-fb0c907d",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-01-19T10:08:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 12.989960897514132,
"threshold": 5
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 8.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-198733a2",
"description": "High shipping queue processing time",
"timestamp": "2024-01-19T10:01:00Z",
"severity": "medium",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1098,
"threshold": 500,
"queue_depth": 1619
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-f351ccc0",
"description": "Label generation service degraded",
"timestamp": "2024-01-19T10:05:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1712,
"threshold": 1000,
"carrier": "fedex"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-198733a2",
"description": "High shipping queue processing time",
"timestamp": "2024-01-19T10:01:00Z",
"severity": "medium",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1098,
"threshold": 500,
"queue_depth": 1619
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-fb0c907d",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-01-19T10:08:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 12.989960897514132,
"threshold": 5
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-f351ccc0",
"description": "Label generation service degraded",
"timestamp": "2024-01-19T10:05:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1712,
"threshold": 1000,
"carrier": "fedex"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-fb0c907d",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-01-19T10:08:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 12.989960897514132,
"threshold": 5
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-28df7249",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-20T00:00:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 89,
"threshold": 20,
"gateway": "square"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-dc4c1743",
"description": "High refund processing latency",
"timestamp": "2024-01-20T00:02:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 8424,
"threshold": 5000,
"refund_type": "partial"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-28df7249",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-20T00:00:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 89,
"threshold": 20,
"gateway": "square"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-fbefeace",
"description": "Increased refund failure rate",
"timestamp": "2024-01-20T00:04:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 11.127900008292347,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-28df7249",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-20T00:00:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 89,
"threshold": 20,
"gateway": "square"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-3acc2e16",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-20T00:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.489843177797766,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-dc4c1743",
"description": "High refund processing latency",
"timestamp": "2024-01-20T00:02:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 8424,
"threshold": 5000,
"refund_type": "partial"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-fbefeace",
"description": "Increased refund failure rate",
"timestamp": "2024-01-20T00:04:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 11.127900008292347,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-dc4c1743",
"description": "High refund processing latency",
"timestamp": "2024-01-20T00:02:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 8424,
"threshold": 5000,
"refund_type": "partial"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-3acc2e16",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-20T00:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.489843177797766,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-fbefeace",
"description": "Increased refund failure rate",
"timestamp": "2024-01-20T00:04:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 11.127900008292347,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-3acc2e16",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-20T00:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.489843177797766,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-21e871de",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-01-20T08:00:00Z",
"severity": "critical",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 93.2411359139003,
"total_connections": 100,
"available_connections": 2
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-484d6515",
"description": "High query latency on returns-db-01",
"timestamp": "2024-01-20T08:05:00Z",
"severity": "critical",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 1665.8362558018257,
"threshold": 200,
"query_type": "UPDATE"
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-21e871de",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-01-20T08:00:00Z",
"severity": "critical",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 93.2411359139003,
"total_connections": 100,
"available_connections": 2
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-d7bbbb7f",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-01-20T08:07:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 86.82847383379439,
"threshold": 80
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-484d6515",
"description": "High query latency on returns-db-01",
"timestamp": "2024-01-20T08:05:00Z",
"severity": "critical",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 1665.8362558018257,
"threshold": 200,
"query_type": "UPDATE"
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-d7bbbb7f",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-01-20T08:07:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 86.82847383379439,
"threshold": 80
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-3dcaea6e",
"description": "High shipping queue processing time",
"timestamp": "2024-01-20T18:00:00Z",
"severity": "high",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1225,
"threshold": 500,
"queue_depth": 2049
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-12069a2a",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-01-20T18:04:00Z",
"severity": "critical",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 19.299394567769866,
"threshold": 5,
"error_type": "CarrierAPIException"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-3dcaea6e",
"description": "High shipping queue processing time",
"timestamp": "2024-01-20T18:00:00Z",
"severity": "high",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1225,
"threshold": 500,
"queue_depth": 2049
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-6bda7a4f",
"description": "Label generation service degraded",
"timestamp": "2024-01-20T18:09:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1600,
"threshold": 1000,
"carrier": "fedex"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 9.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-3dcaea6e",
"description": "High shipping queue processing time",
"timestamp": "2024-01-20T18:00:00Z",
"severity": "high",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1225,
"threshold": 500,
"queue_depth": 2049
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-97aa19f1",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-01-20T18:14:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 5.760302876709197,
"threshold": 5
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 14.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-12069a2a",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-01-20T18:04:00Z",
"severity": "critical",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 19.299394567769866,
"threshold": 5,
"error_type": "CarrierAPIException"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-6bda7a4f",
"description": "Label generation service degraded",
"timestamp": "2024-01-20T18:09:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1600,
"threshold": 1000,
"carrier": "fedex"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-12069a2a",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-01-20T18:04:00Z",
"severity": "critical",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 19.299394567769866,
"threshold": 5,
"error_type": "CarrierAPIException"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-97aa19f1",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-01-20T18:14:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 5.760302876709197,
"threshold": 5
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 10.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-6bda7a4f",
"description": "Label generation service degraded",
"timestamp": "2024-01-20T18:09:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1600,
"threshold": 1000,
"carrier": "fedex"
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"alert2": {
"alert": {
"id": "alert-97aa19f1",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-01-20T18:14:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 5.760302876709197,
"threshold": 5
}
},
"sop_context": {
"signs": "Label generation delays, Carrier API errors, Queue processing backlog",
"actions": "Verify carrier APIs, Clear queue backlog, Scale label service"
}
},
"time_difference_minutes": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-8977dbc5",
"description": "High query latency on returns-db-01",
"timestamp": "2024-01-20T20:00:00Z",
"severity": "high",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 1603.0853267792327,
"threshold": 200,
"query_type": "UPDATE"
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-0e719116",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-01-20T20:03:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 86.70166889195902,
"threshold": 80
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-8977dbc5",
"description": "High query latency on returns-db-01",
"timestamp": "2024-01-20T20:00:00Z",
"severity": "high",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 1603.0853267792327,
"threshold": 200,
"query_type": "UPDATE"
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-b46d1f82",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-01-20T20:07:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 94.29814587608105,
"total_connections": 100,
"available_connections": 4
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-0e719116",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-01-20T20:03:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 86.70166889195902,
"threshold": 80
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-b46d1f82",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-01-20T20:07:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 94.29814587608105,
"total_connections": 100,
"available_connections": 4
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-30147d2f",
"description": "Increased refund failure rate",
"timestamp": "2024-01-21T23:00:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 10.725867079815144,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-52ecf1b5",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-21T23:03:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 92,
"threshold": 20,
"gateway": "paypal"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-30147d2f",
"description": "Increased refund failure rate",
"timestamp": "2024-01-21T23:00:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 10.725867079815144,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-30af5725",
"description": "High refund processing latency",
"timestamp": "2024-01-21T23:04:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 12832,
"threshold": 5000,
"refund_type": "partial"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-30147d2f",
"description": "Increased refund failure rate",
"timestamp": "2024-01-21T23:00:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 10.725867079815144,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-2925ae7e",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-21T23:06:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.140522870158819,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 6.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-52ecf1b5",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-21T23:03:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 92,
"threshold": 20,
"gateway": "paypal"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-30af5725",
"description": "High refund processing latency",
"timestamp": "2024-01-21T23:04:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 12832,
"threshold": 5000,
"refund_type": "partial"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 1.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-52ecf1b5",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-21T23:03:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 92,
"threshold": 20,
"gateway": "paypal"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-2925ae7e",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-21T23:06:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.140522870158819,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-30af5725",
"description": "High refund processing latency",
"timestamp": "2024-01-21T23:04:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 12832,
"threshold": 5000,
"refund_type": "partial"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-2925ae7e",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-21T23:06:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.140522870158819,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-07153c42",
"description": "High CPU usage detected on returns-web-02",
"timestamp": "2024-01-23T03:00:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"cpu_usage": 93.73222991384455,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-c3792d8d",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-01-23T03:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 4770,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-07153c42",
"description": "High CPU usage detected on returns-web-02",
"timestamp": "2024-01-23T03:00:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"cpu_usage": 93.73222991384455,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-1789b1e0",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-01-23T03:08:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 89.20114522664868,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 8.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-07153c42",
"description": "High CPU usage detected on returns-web-02",
"timestamp": "2024-01-23T03:00:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"cpu_usage": 93.73222991384455,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-c87d5f2d",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-01-23T03:13:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 91.44228002751831,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 13.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-07153c42",
"description": "High CPU usage detected on returns-web-02",
"timestamp": "2024-01-23T03:00:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"cpu_usage": 93.73222991384455,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-e2ca3fc8",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-01-23T03:15:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4158,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 15.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-07153c42",
"description": "High CPU usage detected on returns-web-02",
"timestamp": "2024-01-23T03:00:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"cpu_usage": 93.73222991384455,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-150be8bd",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-01-23T03:19:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 87.01326966425195,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 19.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-07153c42",
"description": "High CPU usage detected on returns-web-02",
"timestamp": "2024-01-23T03:00:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"cpu_usage": 93.73222991384455,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f4da696f",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-01-23T03:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 12.386128264684217,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 21.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-07153c42",
"description": "High CPU usage detected on returns-web-02",
"timestamp": "2024-01-23T03:00:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"cpu_usage": 93.73222991384455,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-5758a9f9",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-01-23T03:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.233177850140136,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 23.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-07153c42",
"description": "High CPU usage detected on returns-web-02",
"timestamp": "2024-01-23T03:00:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"cpu_usage": 93.73222991384455,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-a6e20cc6",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-01-23T03:28:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 13.160474084328374,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 28.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-07153c42",
"description": "High CPU usage detected on returns-web-02",
"timestamp": "2024-01-23T03:00:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"cpu_usage": 93.73222991384455,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f288400d",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-01-23T03:30:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 5.417365634528863,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 30.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c3792d8d",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-01-23T03:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 4770,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-1789b1e0",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-01-23T03:08:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 89.20114522664868,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c3792d8d",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-01-23T03:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 4770,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-c87d5f2d",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-01-23T03:13:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 91.44228002751831,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 9.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c3792d8d",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-01-23T03:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 4770,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-e2ca3fc8",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-01-23T03:15:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4158,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 11.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c3792d8d",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-01-23T03:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 4770,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-150be8bd",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-01-23T03:19:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 87.01326966425195,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 15.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c3792d8d",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-01-23T03:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 4770,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f4da696f",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-01-23T03:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 12.386128264684217,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 17.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c3792d8d",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-01-23T03:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 4770,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-5758a9f9",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-01-23T03:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.233177850140136,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 19.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c3792d8d",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-01-23T03:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 4770,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-a6e20cc6",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-01-23T03:28:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 13.160474084328374,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 24.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c3792d8d",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-01-23T03:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 4770,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f288400d",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-01-23T03:30:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 5.417365634528863,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 26.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-1789b1e0",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-01-23T03:08:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 89.20114522664868,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-c87d5f2d",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-01-23T03:13:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 91.44228002751831,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-1789b1e0",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-01-23T03:08:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 89.20114522664868,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-e2ca3fc8",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-01-23T03:15:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4158,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-1789b1e0",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-01-23T03:08:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 89.20114522664868,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-150be8bd",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-01-23T03:19:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 87.01326966425195,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 11.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-1789b1e0",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-01-23T03:08:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 89.20114522664868,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f4da696f",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-01-23T03:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 12.386128264684217,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 13.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-1789b1e0",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-01-23T03:08:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 89.20114522664868,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-5758a9f9",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-01-23T03:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.233177850140136,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 15.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-1789b1e0",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-01-23T03:08:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 89.20114522664868,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-a6e20cc6",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-01-23T03:28:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 13.160474084328374,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 20.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-1789b1e0",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-01-23T03:08:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 89.20114522664868,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f288400d",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-01-23T03:30:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 5.417365634528863,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 22.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c87d5f2d",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-01-23T03:13:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 91.44228002751831,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-e2ca3fc8",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-01-23T03:15:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4158,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c87d5f2d",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-01-23T03:13:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 91.44228002751831,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-150be8bd",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-01-23T03:19:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 87.01326966425195,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 6.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c87d5f2d",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-01-23T03:13:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 91.44228002751831,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f4da696f",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-01-23T03:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 12.386128264684217,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 8.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c87d5f2d",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-01-23T03:13:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 91.44228002751831,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-5758a9f9",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-01-23T03:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.233177850140136,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 10.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c87d5f2d",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-01-23T03:13:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 91.44228002751831,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-a6e20cc6",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-01-23T03:28:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 13.160474084328374,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 15.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c87d5f2d",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-01-23T03:13:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 91.44228002751831,
"threshold": 80,
"region": "us-east-1"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f288400d",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-01-23T03:30:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 5.417365634528863,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 17.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e2ca3fc8",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-01-23T03:15:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4158,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-150be8bd",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-01-23T03:19:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 87.01326966425195,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e2ca3fc8",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-01-23T03:15:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4158,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f4da696f",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-01-23T03:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 12.386128264684217,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 6.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e2ca3fc8",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-01-23T03:15:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4158,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-5758a9f9",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-01-23T03:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.233177850140136,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 8.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e2ca3fc8",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-01-23T03:15:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4158,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-a6e20cc6",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-01-23T03:28:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 13.160474084328374,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 13.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e2ca3fc8",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-01-23T03:15:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4158,
"threshold": 1000,
"method": "POST"
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f288400d",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-01-23T03:30:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 5.417365634528863,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 15.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-150be8bd",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-01-23T03:19:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 87.01326966425195,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f4da696f",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-01-23T03:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 12.386128264684217,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-150be8bd",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-01-23T03:19:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 87.01326966425195,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-5758a9f9",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-01-23T03:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.233177850140136,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-150be8bd",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-01-23T03:19:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 87.01326966425195,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-a6e20cc6",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-01-23T03:28:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 13.160474084328374,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 9.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-150be8bd",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-01-23T03:19:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 87.01326966425195,
"threshold": 80
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f288400d",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-01-23T03:30:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 5.417365634528863,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 11.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-f4da696f",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-01-23T03:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 12.386128264684217,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-5758a9f9",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-01-23T03:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.233177850140136,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-f4da696f",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-01-23T03:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 12.386128264684217,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-a6e20cc6",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-01-23T03:28:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 13.160474084328374,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-f4da696f",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-01-23T03:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 12.386128264684217,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f288400d",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-01-23T03:30:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 5.417365634528863,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 9.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-5758a9f9",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-01-23T03:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.233177850140136,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-a6e20cc6",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-01-23T03:28:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 13.160474084328374,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-5758a9f9",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-01-23T03:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.233177850140136,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f288400d",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-01-23T03:30:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 5.417365634528863,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-a6e20cc6",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-01-23T03:28:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 13.160474084328374,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"alert2": {
"alert": {
"id": "alert-f288400d",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-01-23T03:30:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 5.417365634528863,
"threshold": 5
}
},
"sop_context": {
"signs": "High CPU on returns web servers, 5xx errors, Slow return API responses",
"actions": "Check resources, Scale web instances, Enable API throttling"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-89e7a4f4",
"description": "High refund processing latency",
"timestamp": "2024-01-23T10:00:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 9274,
"threshold": 5000,
"refund_type": "partial"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-5c2431c7",
"description": "Increased refund failure rate",
"timestamp": "2024-01-23T10:04:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 17.397885890076676,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-89e7a4f4",
"description": "High refund processing latency",
"timestamp": "2024-01-23T10:00:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 9274,
"threshold": 5000,
"refund_type": "partial"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-40381ff9",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-23T10:07:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 195,
"threshold": 20,
"gateway": "paypal"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-89e7a4f4",
"description": "High refund processing latency",
"timestamp": "2024-01-23T10:00:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 9274,
"threshold": 5000,
"refund_type": "partial"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-8232f5a5",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-23T10:10:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.675582627181772,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 10.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-5c2431c7",
"description": "Increased refund failure rate",
"timestamp": "2024-01-23T10:04:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 17.397885890076676,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-40381ff9",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-23T10:07:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 195,
"threshold": 20,
"gateway": "paypal"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-5c2431c7",
"description": "Increased refund failure rate",
"timestamp": "2024-01-23T10:04:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 17.397885890076676,
"threshold": 5,
"error_type": "RefundProcessingException"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-8232f5a5",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-23T10:10:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.675582627181772,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 6.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-40381ff9",
"description": "Payment gateway connection issues",
"timestamp": "2024-01-23T10:07:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 195,
"threshold": 20,
"gateway": "paypal"
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"alert2": {
"alert": {
"id": "alert-8232f5a5",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-01-23T10:10:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.675582627181772,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-7c0e9129",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-01-23T17:00:00Z",
"severity": "high",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 97.43681238143084,
"total_connections": 100,
"available_connections": 6
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-dbbb69f8",
"description": "High query latency on returns-db-01",
"timestamp": "2024-01-23T17:04:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 789.4716816356765,
"threshold": 200,
"query_type": "INSERT"
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-7c0e9129",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-01-23T17:00:00Z",
"severity": "high",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 97.43681238143084,
"total_connections": 100,
"available_connections": 6
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-7d12ff66",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-01-23T17:07:00Z",
"severity": "critical",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 93.38595704025589,
"threshold": 80
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-dbbb69f8",
"description": "High query latency on returns-db-01",
"timestamp": "2024-01-23T17:04:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 789.4716816356765,
"threshold": 200,
"query_type": "INSERT"
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-7d12ff66",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-01-23T17:07:00Z",
"severity": "critical",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 93.38595704025589,
"threshold": 80
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-72f6a48f",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-01-25T10:00:00Z",
"severity": "high",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 88.69478134217447,
"threshold": 80
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-63e3514f",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-01-25T10:02:00Z",
"severity": "critical",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 95.88295604057527,
"total_connections": 100,
"available_connections": 5
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-72f6a48f",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-01-25T10:00:00Z",
"severity": "high",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 88.69478134217447,
"threshold": 80
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"alert2": {
"alert": {
"id": "alert-da02e1c4",
"description": "High query latency on returns-db-01",
"timestamp": "2024-01-25T10:05:00Z",
"severity": "critical",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 1451.0257406230467,
"threshold": 200,
"query_type": "INSERT"
}
},
"sop_context": {
"signs": "Connection pool >90%, High query latency on returns-db, Memory pressure",
"actions": "Kill blocking queries, Clear cache, Release idle connections"
}
},
"time_difference_minutes": 5.0
}
|
true
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.