Log Detail #52

26 April 2026, 15:56:05 WIB

Monitor Information

Monitor ID
ThisWillBeTheMonitorID32CharLong
Monitor Name
Test Monitor Label
Monitor Status
Offline
Request Method
POST

Request Payload

{
    "received_at": "2026-04-26 15:56:05",
    "event_time": "2026-04-26 15:56:04",
    "client_ip": "172.70.80.162",
    "monitor_id": "ThisWillBeTheMonitorID32CharLong",
    "monitor_name": "Test Monitor Label",
    "monitor_target": "http://this-is-a-test.com/",
    "monitor_type": "website",
    "monitor_category": "Test Category",
    "monitor_status": "offline",
    "monitor_errors": {
        "New York": "http code 403",
        "San Francisco": "http code 403",
        "Dallas": "timeout",
        "Amsterdam": "http code 403",
        "London": "http code 403",
        "Frankfurt": "http code 403",
        "Singapore": "timeout",
        "Sydney": "http code 403",
        "Sao Paulo": "http code 403",
        "Tokyo": "keyword not found",
        "Mumbai": "http code 403",
        "Warsaw": "keyword not found"
    },
    "raw_json": {
        "monitor_id": "ThisWillBeTheMonitorID32CharLong",
        "monitor_name": "Test Monitor Label",
        "monitor_target": "http://this-is-a-test.com/",
        "monitor_type": "website",
        "monitor_category": "Test Category",
        "monitor_status": "offline",
        "timestamp": 1777193764,
        "monitor_errors": {
            "New York": "http code 403",
            "San Francisco": "http code 403",
            "Dallas": "timeout",
            "Amsterdam": "http code 403",
            "London": "http code 403",
            "Frankfurt": "http code 403",
            "Singapore": "timeout",
            "Sydney": "http code 403",
            "Sao Paulo": "http code 403",
            "Tokyo": "keyword not found",
            "Mumbai": "http code 403",
            "Warsaw": "keyword not found"
        }
    }
}

Response Body

{
    "status": "success",
    "success": true,
    "message": "Pesan Terkirim",
    "data": {
        "success": true,
        "message": "Messages sent successfully",
        "data": [
            {
                "remoteJid": "120363410098349594@g.us",
                "fromMe": true,
                "id": "3EB0A0350F4B4BC5F18F8C",
                "extendedTextMessage": {
                    "text": "🚨 *ALERT: SERVICE DOWN*\n────────────────────────────────────────\n\nšŸ“Š *INFORMASI LAYANAN*\n*Monitor:* Test Monitor Label\n*Target:* http://this-is-a-test.com/\n*Status:* OFFLINE\n*Tipe Monitor:* website\n*Kategori:* Test Category\n\nšŸ•’ *WAKTU*\n*Kejadian:* 2026-04-26 15:56:04 WIB\n*Diterima:* 2026-04-26 15:56:05 WIB\n\n────────────────────────────────────────\n\nāš ļø *PEMBERITAHUAN*\nMohon maaf atas ketidaknyamanan ini. Layanan kami saat ini sedang mengalami gangguan dan tidak dapat diakses.\n\nTim teknis kami telah menerima notifikasi ini dan sedang melakukan penanganan dengan prioritas tinggi untuk memulihkan layanan secepatnya.\n\nāŒ *DETAIL ERROR*\nTerdeteksi *12 lokasi monitoring* mengalami kegagalan:\n\n• *New York*\n  └─ http code 403\n• *San Francisco*\n  └─ http code 403\n• *Dallas*\n  └─ timeout\n• *Amsterdam*\n  └─ http code 403\n• *London*\n  └─ http code 403\n• *Frankfurt*\n  └─ http code 403\n• *Singapore*\n  └─ timeout\n• *Sydney*\n  └─ http code 403\n• *Sao Paulo*\n  └─ http code 403\n• *Tokyo*\n  └─ keyword not found\n• *Mumbai*\n  └─ http code 403\n• *Warsaw*\n  └─ keyword not found\n\nšŸ”§ *TINDAKAN KAMI*\n• Tim sedang menginvestigasi penyebab gangguan\n• Prioritas: Pemulihan segera layanan\n• Update akan diberikan jika diperlukan\n\nTerima kasih atas pengertian Anda. šŸ™\n\n────────────────────────────────────────\nšŸ” *Monitor ID:* `ThisWillBeTheMonitorID32CharLong`\n\n> send via _wa.farmedia.co.id_"
                }
            }
        ]
    }
}

Status

Webhook Status
Success
HTTP Status Code
200
Retry Count
0x

Timestamps

Created At
26 April 2026
15:56:05 WIB
Updated At
26 April 2026
15:56:09 WIB

Connection

Client IP
172.70.80.162
Webhook URL
https://wa.farmedia.co.id/api/send-message