question
stringlengths 1.03k
1.62k
| answer
stringclasses 2
values |
|---|---|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-3af7ef96",
"description": "Degraded performance in returns-database due to returns-processing issues",
"timestamp": "2024-02-15T20:19:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [
"returns-processing"
],
"error_rate": 13.807843962944213,
"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-80ccae2e",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-02-15T20:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 9.295235377943174,
"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-3af7ef96",
"description": "Degraded performance in returns-database due to returns-processing issues",
"timestamp": "2024-02-15T20:19:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [
"returns-processing"
],
"error_rate": 13.807843962944213,
"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-2da219e2",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-15T20:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 9.053531482126846,
"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-80ccae2e",
"description": "Degraded performance in refund-service due to returns-processing issues",
"timestamp": "2024-02-15T20:21:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"returns-processing"
],
"error_rate": 9.295235377943174,
"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-2da219e2",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-15T20:23:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 9.053531482126846,
"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-6e299246",
"description": "Label generation service degraded",
"timestamp": "2024-02-16T03:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 2624,
"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-0fa29d03",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-02-16T03:03:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 18.863925957250327,
"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": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-6e299246",
"description": "Label generation service degraded",
"timestamp": "2024-02-16T03:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 2624,
"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-76f2599f",
"description": "High shipping queue processing time",
"timestamp": "2024-02-16T03:06:00Z",
"severity": "medium",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1310,
"threshold": 500,
"queue_depth": 2465
}
},
"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-6e299246",
"description": "Label generation service degraded",
"timestamp": "2024-02-16T03:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 2624,
"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-37adf8a5",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-02-16T03:11:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 6.207788077041312,
"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": 11.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-0fa29d03",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-02-16T03:03:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 18.863925957250327,
"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-76f2599f",
"description": "High shipping queue processing time",
"timestamp": "2024-02-16T03:06:00Z",
"severity": "medium",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1310,
"threshold": 500,
"queue_depth": 2465
}
},
"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-0fa29d03",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-02-16T03:03:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 18.863925957250327,
"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-37adf8a5",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-02-16T03:11:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 6.207788077041312,
"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-76f2599f",
"description": "High shipping queue processing time",
"timestamp": "2024-02-16T03:06:00Z",
"severity": "medium",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1310,
"threshold": 500,
"queue_depth": 2465
}
},
"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-37adf8a5",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-02-16T03:11:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 6.207788077041312,
"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-47d733f2",
"description": "Increased refund failure rate",
"timestamp": "2024-02-16T21:00:00Z",
"severity": "critical",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 10.212151894107848,
"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-6cf0935c",
"description": "High refund processing latency",
"timestamp": "2024-02-16T21:01:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 8057,
"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-47d733f2",
"description": "Increased refund failure rate",
"timestamp": "2024-02-16T21:00:00Z",
"severity": "critical",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 10.212151894107848,
"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-da9ae0d3",
"description": "Payment gateway connection issues",
"timestamp": "2024-02-16T21:05:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 65,
"threshold": 20,
"gateway": "square"
}
},
"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-47d733f2",
"description": "Increased refund failure rate",
"timestamp": "2024-02-16T21:00:00Z",
"severity": "critical",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 10.212151894107848,
"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-6111692a",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-02-16T21:08:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 6.763236094055446,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 8.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-6cf0935c",
"description": "High refund processing latency",
"timestamp": "2024-02-16T21:01:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 8057,
"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-da9ae0d3",
"description": "Payment gateway connection issues",
"timestamp": "2024-02-16T21:05:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 65,
"threshold": 20,
"gateway": "square"
}
},
"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-6cf0935c",
"description": "High refund processing latency",
"timestamp": "2024-02-16T21:01:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 8057,
"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-6111692a",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-02-16T21:08:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 6.763236094055446,
"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-da9ae0d3",
"description": "Payment gateway connection issues",
"timestamp": "2024-02-16T21:05:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 65,
"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-6111692a",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-02-16T21:08:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 6.763236094055446,
"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-59f0a81a",
"description": "Payment gateway connection issues",
"timestamp": "2024-02-17T07:00:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 84,
"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-0eba4141",
"description": "High refund processing latency",
"timestamp": "2024-02-17T07:03:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 9904,
"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": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-59f0a81a",
"description": "Payment gateway connection issues",
"timestamp": "2024-02-17T07:00:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 84,
"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-0669cc03",
"description": "Increased refund failure rate",
"timestamp": "2024-02-17T07:06:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 16.830293098236055,
"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-59f0a81a",
"description": "Payment gateway connection issues",
"timestamp": "2024-02-17T07:00:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 84,
"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-4842ebd6",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-02-17T07:08:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.217626136629232,
"threshold": 5
}
},
"sop_context": {
"signs": "High refund latency, Gateway timeouts, RefundProcessingException",
"actions": "Check payment gateway, Enable circuit breakers, Queue failed refunds"
}
},
"time_difference_minutes": 8.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-0eba4141",
"description": "High refund processing latency",
"timestamp": "2024-02-17T07:03:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 9904,
"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-0669cc03",
"description": "Increased refund failure rate",
"timestamp": "2024-02-17T07:06:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 16.830293098236055,
"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": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-0eba4141",
"description": "High refund processing latency",
"timestamp": "2024-02-17T07:03:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 9904,
"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-4842ebd6",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-02-17T07:08:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.217626136629232,
"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-0669cc03",
"description": "Increased refund failure rate",
"timestamp": "2024-02-17T07:06:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 16.830293098236055,
"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-4842ebd6",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-02-17T07:08:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 12.217626136629232,
"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-2b02d198",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-02-17T14:00:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 16.361894740626802,
"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-c8b9eb23",
"description": "Label generation service degraded",
"timestamp": "2024-02-17T14:02:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1601,
"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-2b02d198",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-02-17T14:00:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 16.361894740626802,
"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-3b992701",
"description": "High shipping queue processing time",
"timestamp": "2024-02-17T14:05:00Z",
"severity": "critical",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1278,
"threshold": 500,
"queue_depth": 2395
}
},
"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-2b02d198",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-02-17T14:00:00Z",
"severity": "medium",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 16.361894740626802,
"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-b6dbb15d",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-02-17T14:09:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 10.039926139788902,
"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": 9.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-c8b9eb23",
"description": "Label generation service degraded",
"timestamp": "2024-02-17T14:02:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1601,
"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-3b992701",
"description": "High shipping queue processing time",
"timestamp": "2024-02-17T14:05:00Z",
"severity": "critical",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1278,
"threshold": 500,
"queue_depth": 2395
}
},
"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-c8b9eb23",
"description": "Label generation service degraded",
"timestamp": "2024-02-17T14:02:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1601,
"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-b6dbb15d",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-02-17T14:09:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 10.039926139788902,
"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-3b992701",
"description": "High shipping queue processing time",
"timestamp": "2024-02-17T14:05:00Z",
"severity": "critical",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1278,
"threshold": 500,
"queue_depth": 2395
}
},
"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-b6dbb15d",
"description": "Degraded performance in shipping-queue due to shipping-service issues",
"timestamp": "2024-02-17T14:09:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-queue",
"related_entities": [
"shipping-service"
],
"error_rate": 10.039926139788902,
"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-44f09907",
"description": "Increased refund failure rate",
"timestamp": "2024-02-17T15:00:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 10.000803598946405,
"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-99467416",
"description": "High refund processing latency",
"timestamp": "2024-02-17T15:02:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 8689,
"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-44f09907",
"description": "Increased refund failure rate",
"timestamp": "2024-02-17T15:00:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 10.000803598946405,
"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-40d3492e",
"description": "Payment gateway connection issues",
"timestamp": "2024-02-17T15:03:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 163,
"threshold": 20,
"gateway": "square"
}
},
"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-44f09907",
"description": "Increased refund failure rate",
"timestamp": "2024-02-17T15:00:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"error_rate": 10.000803598946405,
"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-cb728861",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-02-17T15:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 5.64513949504722,
"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-99467416",
"description": "High refund processing latency",
"timestamp": "2024-02-17T15:02:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 8689,
"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-40d3492e",
"description": "Payment gateway connection issues",
"timestamp": "2024-02-17T15:03:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 163,
"threshold": 20,
"gateway": "square"
}
},
"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-99467416",
"description": "High refund processing latency",
"timestamp": "2024-02-17T15:02:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"processing_time": 8689,
"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-cb728861",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-02-17T15:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 5.64513949504722,
"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-40d3492e",
"description": "Payment gateway connection issues",
"timestamp": "2024-02-17T15:03:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "refund-service",
"related_entities": [
"payment-database"
],
"connection_failures": 163,
"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-cb728861",
"description": "Degraded performance in payment-database due to refund-service issues",
"timestamp": "2024-02-17T15:04:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "payment-database",
"related_entities": [
"refund-service"
],
"error_rate": 5.64513949504722,
"threshold": 5
}
},
"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-61fbbcac",
"description": "Label generation service degraded",
"timestamp": "2024-02-17T22:00:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 2225,
"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-a24fadaf",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-02-17T22:05:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 25.023530772491753,
"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": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-61fbbcac",
"description": "Label generation service degraded",
"timestamp": "2024-02-17T22:00:00Z",
"severity": "critical",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 2225,
"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-bca96b94",
"description": "High shipping queue processing time",
"timestamp": "2024-02-17T22:09:00Z",
"severity": "high",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1173,
"threshold": 500,
"queue_depth": 1938
}
},
"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-a24fadaf",
"description": "Shipping carrier API errors increasing",
"timestamp": "2024-02-17T22:05:00Z",
"severity": "high",
"source": "application-logs",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"error_rate": 25.023530772491753,
"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-bca96b94",
"description": "High shipping queue processing time",
"timestamp": "2024-02-17T22:09:00Z",
"severity": "high",
"source": "queue-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"shipping-queue"
],
"processing_time": 1173,
"threshold": 500,
"queue_depth": 1938
}
},
"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-4e38d638",
"description": "Memory pressure on returns-web-01",
"timestamp": "2024-02-18T11:00:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"memory_usage": 85.93838918994717,
"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-be6a6a41",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T11:03:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 86.10152074537696,
"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": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-4e38d638",
"description": "Memory pressure on returns-web-01",
"timestamp": "2024-02-18T11:00:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"memory_usage": 85.93838918994717,
"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-e5a2f269",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-02-18T11:04:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 2378,
"threshold": 1000,
"method": "GET"
}
},
"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-4e38d638",
"description": "Memory pressure on returns-web-01",
"timestamp": "2024-02-18T11:00:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"memory_usage": 85.93838918994717,
"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-21596c57",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T11:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 3296,
"threshold": 1000,
"method": "GET"
}
},
"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-4e38d638",
"description": "Memory pressure on returns-web-01",
"timestamp": "2024-02-18T11:00:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"memory_usage": 85.93838918994717,
"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-0e8cbb88",
"description": "High CPU usage detected on returns-proc-02",
"timestamp": "2024-02-18T11:11:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"cpu_usage": 87.52526654994782,
"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": 11.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-4e38d638",
"description": "Memory pressure on returns-web-01",
"timestamp": "2024-02-18T11:00:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"memory_usage": 85.93838918994717,
"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-8527756f",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-02-18T11:15:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 93.6302683661817,
"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-4e38d638",
"description": "Memory pressure on returns-web-01",
"timestamp": "2024-02-18T11:00:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"memory_usage": 85.93838918994717,
"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-6b717683",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T11:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 10.433387066918282,
"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": 16.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-4e38d638",
"description": "Memory pressure on returns-web-01",
"timestamp": "2024-02-18T11:00:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"memory_usage": 85.93838918994717,
"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-3a67d253",
"description": "Degraded performance in returns-database due to returns-processing issues",
"timestamp": "2024-02-18T11:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [
"returns-processing"
],
"error_rate": 9.451335898657817,
"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-4e38d638",
"description": "Memory pressure on returns-web-01",
"timestamp": "2024-02-18T11:00:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"memory_usage": 85.93838918994717,
"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-c0f62601",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T11:22:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 14.474476917524097,
"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-be6a6a41",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T11:03:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 86.10152074537696,
"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-e5a2f269",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-02-18T11:04:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 2378,
"threshold": 1000,
"method": "GET"
}
},
"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": 1.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-be6a6a41",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T11:03:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 86.10152074537696,
"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-21596c57",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T11:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 3296,
"threshold": 1000,
"method": "GET"
}
},
"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-be6a6a41",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T11:03:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 86.10152074537696,
"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-0e8cbb88",
"description": "High CPU usage detected on returns-proc-02",
"timestamp": "2024-02-18T11:11:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"cpu_usage": 87.52526654994782,
"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": 8.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-be6a6a41",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T11:03:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 86.10152074537696,
"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-8527756f",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-02-18T11:15:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 93.6302683661817,
"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": 12.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-be6a6a41",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T11:03:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 86.10152074537696,
"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-6b717683",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T11:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 10.433387066918282,
"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-be6a6a41",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T11:03:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 86.10152074537696,
"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-3a67d253",
"description": "Degraded performance in returns-database due to returns-processing issues",
"timestamp": "2024-02-18T11:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [
"returns-processing"
],
"error_rate": 9.451335898657817,
"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-be6a6a41",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T11:03:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 86.10152074537696,
"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-c0f62601",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T11:22:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 14.474476917524097,
"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-e5a2f269",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-02-18T11:04:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 2378,
"threshold": 1000,
"method": "GET"
}
},
"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-21596c57",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T11:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 3296,
"threshold": 1000,
"method": "GET"
}
},
"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": 3.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e5a2f269",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-02-18T11:04:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 2378,
"threshold": 1000,
"method": "GET"
}
},
"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-0e8cbb88",
"description": "High CPU usage detected on returns-proc-02",
"timestamp": "2024-02-18T11:11:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"cpu_usage": 87.52526654994782,
"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": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e5a2f269",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-02-18T11:04:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 2378,
"threshold": 1000,
"method": "GET"
}
},
"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-8527756f",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-02-18T11:15:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 93.6302683661817,
"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-e5a2f269",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-02-18T11:04:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 2378,
"threshold": 1000,
"method": "GET"
}
},
"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-6b717683",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T11:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 10.433387066918282,
"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": 12.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e5a2f269",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-02-18T11:04:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 2378,
"threshold": 1000,
"method": "GET"
}
},
"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-3a67d253",
"description": "Degraded performance in returns-database due to returns-processing issues",
"timestamp": "2024-02-18T11:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [
"returns-processing"
],
"error_rate": 9.451335898657817,
"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": 16.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-e5a2f269",
"description": "Increased API response time for /api/returns endpoint",
"timestamp": "2024-02-18T11:04:00Z",
"severity": "high",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/returns",
"response_time": 2378,
"threshold": 1000,
"method": "GET"
}
},
"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-c0f62601",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T11:22:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 14.474476917524097,
"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": 18.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-21596c57",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T11:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 3296,
"threshold": 1000,
"method": "GET"
}
},
"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-0e8cbb88",
"description": "High CPU usage detected on returns-proc-02",
"timestamp": "2024-02-18T11:11:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"cpu_usage": 87.52526654994782,
"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": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-21596c57",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T11:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 3296,
"threshold": 1000,
"method": "GET"
}
},
"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-8527756f",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-02-18T11:15:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 93.6302683661817,
"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-21596c57",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T11:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 3296,
"threshold": 1000,
"method": "GET"
}
},
"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-6b717683",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T11:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 10.433387066918282,
"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-21596c57",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T11:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 3296,
"threshold": 1000,
"method": "GET"
}
},
"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-3a67d253",
"description": "Degraded performance in returns-database due to returns-processing issues",
"timestamp": "2024-02-18T11:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [
"returns-processing"
],
"error_rate": 9.451335898657817,
"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-21596c57",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T11:07:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 3296,
"threshold": 1000,
"method": "GET"
}
},
"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-c0f62601",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T11:22:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 14.474476917524097,
"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-0e8cbb88",
"description": "High CPU usage detected on returns-proc-02",
"timestamp": "2024-02-18T11:11:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"cpu_usage": 87.52526654994782,
"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-8527756f",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-02-18T11:15:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 93.6302683661817,
"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-0e8cbb88",
"description": "High CPU usage detected on returns-proc-02",
"timestamp": "2024-02-18T11:11:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"cpu_usage": 87.52526654994782,
"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-6b717683",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T11:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 10.433387066918282,
"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-0e8cbb88",
"description": "High CPU usage detected on returns-proc-02",
"timestamp": "2024-02-18T11:11:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"cpu_usage": 87.52526654994782,
"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-3a67d253",
"description": "Degraded performance in returns-database due to returns-processing issues",
"timestamp": "2024-02-18T11:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [
"returns-processing"
],
"error_rate": 9.451335898657817,
"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-0e8cbb88",
"description": "High CPU usage detected on returns-proc-02",
"timestamp": "2024-02-18T11:11:00Z",
"severity": "critical",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"cpu_usage": 87.52526654994782,
"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-c0f62601",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T11:22:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 14.474476917524097,
"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-8527756f",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-02-18T11:15:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 93.6302683661817,
"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-6b717683",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T11:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 10.433387066918282,
"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": 1.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-8527756f",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-02-18T11:15:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 93.6302683661817,
"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-3a67d253",
"description": "Degraded performance in returns-database due to returns-processing issues",
"timestamp": "2024-02-18T11:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [
"returns-processing"
],
"error_rate": 9.451335898657817,
"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-8527756f",
"description": "Memory pressure on returns-proc-02",
"timestamp": "2024-02-18T11:15:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-02",
"memory_usage": 93.6302683661817,
"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-c0f62601",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T11:22:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 14.474476917524097,
"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-6b717683",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T11:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 10.433387066918282,
"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-3a67d253",
"description": "Degraded performance in returns-database due to returns-processing issues",
"timestamp": "2024-02-18T11:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [
"returns-processing"
],
"error_rate": 9.451335898657817,
"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-6b717683",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T11:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 10.433387066918282,
"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-c0f62601",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T11:22:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 14.474476917524097,
"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-3a67d253",
"description": "Degraded performance in returns-database due to returns-processing issues",
"timestamp": "2024-02-18T11:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [
"returns-processing"
],
"error_rate": 9.451335898657817,
"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-c0f62601",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T11:22:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 14.474476917524097,
"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-6ef31591",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-02-18T15:00:00Z",
"severity": "high",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 93.44331340471673,
"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-3e5a2d79",
"description": "High query latency on returns-db-01",
"timestamp": "2024-02-18T15:04:00Z",
"severity": "high",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 1026.0150173775412,
"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-6ef31591",
"description": "Database connection pool near capacity on returns-db-01",
"timestamp": "2024-02-18T15:00:00Z",
"severity": "high",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"pool_usage": 93.44331340471673,
"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-dead3855",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-02-18T15:08:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 93.11304742005879,
"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": 8.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-3e5a2d79",
"description": "High query latency on returns-db-01",
"timestamp": "2024-02-18T15:04:00Z",
"severity": "high",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"query_latency": 1026.0150173775412,
"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-dead3855",
"description": "Increased memory usage on returns-db-01",
"timestamp": "2024-02-18T15:08:00Z",
"severity": "medium",
"source": "database-monitoring",
"metadata": {
"service": "returns-database",
"related_entities": [],
"server": "returns-db-01",
"memory_usage": 93.11304742005879,
"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": 4.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-2e708cf2",
"description": "Increased API response time for /api/labels endpoint",
"timestamp": "2024-02-18T17:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/labels",
"response_time": 3908,
"threshold": 1000,
"method": "GET"
}
},
"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-16e27269",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T17:05:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 83.84856751958705,
"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-2e708cf2",
"description": "Increased API response time for /api/labels endpoint",
"timestamp": "2024-02-18T17:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/labels",
"response_time": 3908,
"threshold": 1000,
"method": "GET"
}
},
"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-fe536512",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-02-18T17:07:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 85.17745261319895,
"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": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-2e708cf2",
"description": "Increased API response time for /api/labels endpoint",
"timestamp": "2024-02-18T17:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/labels",
"response_time": 3908,
"threshold": 1000,
"method": "GET"
}
},
"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-a3a7c6f8",
"description": "Memory pressure on returns-proc-01",
"timestamp": "2024-02-18T17:12:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"memory_usage": 90.5692407797698,
"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": 12.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-2e708cf2",
"description": "Increased API response time for /api/labels endpoint",
"timestamp": "2024-02-18T17:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/labels",
"response_time": 3908,
"threshold": 1000,
"method": "GET"
}
},
"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-941e701c",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-02-18T17:13:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 84.43221916058859,
"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-2e708cf2",
"description": "Increased API response time for /api/labels endpoint",
"timestamp": "2024-02-18T17:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/labels",
"response_time": 3908,
"threshold": 1000,
"method": "GET"
}
},
"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-654329df",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T17:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4932,
"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": 16.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-2e708cf2",
"description": "Increased API response time for /api/labels endpoint",
"timestamp": "2024-02-18T17:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/labels",
"response_time": 3908,
"threshold": 1000,
"method": "GET"
}
},
"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-273617fc",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-02-18T17:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.760070050816928,
"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-2e708cf2",
"description": "Increased API response time for /api/labels endpoint",
"timestamp": "2024-02-18T17:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/labels",
"response_time": 3908,
"threshold": 1000,
"method": "GET"
}
},
"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-d3c53a06",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T17:24:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.669421771823846,
"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-2e708cf2",
"description": "Increased API response time for /api/labels endpoint",
"timestamp": "2024-02-18T17:00:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"endpoint": "/api/labels",
"response_time": 3908,
"threshold": 1000,
"method": "GET"
}
},
"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-235b190d",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T17:25:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 8.16482904016829,
"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": 25.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-16e27269",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T17:05:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 83.84856751958705,
"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-fe536512",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-02-18T17:07:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 85.17745261319895,
"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": 2.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-16e27269",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T17:05:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 83.84856751958705,
"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-a3a7c6f8",
"description": "Memory pressure on returns-proc-01",
"timestamp": "2024-02-18T17:12:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"memory_usage": 90.5692407797698,
"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": 7.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-16e27269",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T17:05:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 83.84856751958705,
"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-941e701c",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-02-18T17:13:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 84.43221916058859,
"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": 8.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-16e27269",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T17:05:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 83.84856751958705,
"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-654329df",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T17:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4932,
"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-16e27269",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T17:05:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 83.84856751958705,
"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-273617fc",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-02-18T17:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.760070050816928,
"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-16e27269",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T17:05:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 83.84856751958705,
"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-d3c53a06",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T17:24:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.669421771823846,
"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-16e27269",
"description": "High CPU usage detected on returns-web-01",
"timestamp": "2024-02-18T17:05:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-01",
"cpu_usage": 83.84856751958705,
"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-235b190d",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T17:25:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 8.16482904016829,
"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-fe536512",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-02-18T17:07:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 85.17745261319895,
"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-a3a7c6f8",
"description": "Memory pressure on returns-proc-01",
"timestamp": "2024-02-18T17:12:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"memory_usage": 90.5692407797698,
"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": 5.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-fe536512",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-02-18T17:07:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 85.17745261319895,
"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-941e701c",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-02-18T17:13:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 84.43221916058859,
"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": 6.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-fe536512",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-02-18T17:07:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 85.17745261319895,
"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-654329df",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T17:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4932,
"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": 9.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-fe536512",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-02-18T17:07:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 85.17745261319895,
"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-273617fc",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-02-18T17:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.760070050816928,
"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-fe536512",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-02-18T17:07:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 85.17745261319895,
"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-d3c53a06",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T17:24:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.669421771823846,
"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-fe536512",
"description": "Memory pressure on returns-web-02",
"timestamp": "2024-02-18T17:07:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-frontend",
"related_entities": [
"returns-processing",
"customer-validation"
],
"server": "returns-web-02",
"memory_usage": 85.17745261319895,
"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-235b190d",
"description": "Degraded performance in shipping-service due to returns-processing issues",
"timestamp": "2024-02-18T17:25:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "shipping-service",
"related_entities": [
"returns-processing"
],
"error_rate": 8.16482904016829,
"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": 18.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-a3a7c6f8",
"description": "Memory pressure on returns-proc-01",
"timestamp": "2024-02-18T17:12:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"memory_usage": 90.5692407797698,
"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-941e701c",
"description": "High CPU usage detected on returns-proc-01",
"timestamp": "2024-02-18T17:13:00Z",
"severity": "medium",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"cpu_usage": 84.43221916058859,
"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": 1.0
}
|
true
|
Are these alerts related to each other ?
{
"alert1": {
"alert": {
"id": "alert-a3a7c6f8",
"description": "Memory pressure on returns-proc-01",
"timestamp": "2024-02-18T17:12:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"memory_usage": 90.5692407797698,
"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-654329df",
"description": "Increased API response time for /api/default endpoint",
"timestamp": "2024-02-18T17:16:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"endpoint": "/api/default",
"response_time": 4932,
"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-a3a7c6f8",
"description": "Memory pressure on returns-proc-01",
"timestamp": "2024-02-18T17:12:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"memory_usage": 90.5692407797698,
"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-273617fc",
"description": "Degraded performance in returns-processing due to returns-frontend issues",
"timestamp": "2024-02-18T17:20:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.760070050816928,
"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-a3a7c6f8",
"description": "Memory pressure on returns-proc-01",
"timestamp": "2024-02-18T17:12:00Z",
"severity": "high",
"source": "cloudwatch",
"metadata": {
"service": "returns-processing",
"related_entities": [
"returns-database",
"refund-service",
"shipping-service"
],
"server": "returns-proc-01",
"memory_usage": 90.5692407797698,
"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-d3c53a06",
"description": "Degraded performance in customer-validation due to returns-frontend issues",
"timestamp": "2024-02-18T17:24:00Z",
"severity": "medium",
"source": "application-monitoring",
"metadata": {
"service": "customer-validation",
"related_entities": [
"returns-frontend"
],
"error_rate": 11.669421771823846,
"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": 12.0
}
|
true
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.