Service Status Change MX Message¶
service_status_change message is generated by Worker
service when service change oper status.
Message Headers¶
- Message-Type
- Type of message. Always
service_status_change. - Sharding-Key
- Key for consistent sharding.
- Labels
- Service's effective labels.
Message Format¶
Message contains JSON object, containing objects of following structure
| Name | Type | Description |
|---|---|---|
| label | String | Service label (name) |
| description | String | Service description |
| in_maintenance | Bool | Service In Maintenance Flag |
| agreement_id | String | Service Agreement_id |
| status | Object | Service Oper status |
| id | String | Current Status ID |
| name | String | Current Status Name |
| profile | Object | Service Profile |
| id | String | Service Profile ID |
| name | String | Service Profile Name |
| from_status | Object | Previous Oper Status |
| id | String | Current Status ID |
| name | String | Current Status Name |
| remote_system | Object | Source remote system for service |
| id | String | External system's id |
| name | String | External system's name |
| remote_id | String | External system's id (Opaque attribbute) |
| bi_id | Integer | BI Database id (metrics) |
Example¶
{
"id": "6760e485b2a14cf33aebe80d",
"label": "www.com",
"description": null,
"profile": {
"id": "6760e0cab7a64fd042e04aa5",
"name": "WEB сайт"
},
"status": {
"id": 4,
"name": "DOWN"
},
"in_maintenance": 0,
"agreement_id": null,
"caps": {
"Web Site | Name": "www.com"
},
"from_status": {
"id": 1,
"name": "UP"
},
"ts": [
"2025-05-26T17:46:52"
]
}