Watchtower Control Room

Somchai Scheduler

Monitor connected apps, review incidents, onboard new projects, and keep your operational contract in one calm place.

Add Project Integration Guide
production

Somchai Scheduler

Healthy

http://100.67.241.67:18080/health

Container Pattern
somchai-scheduler
Source
Manual
Container
chili-radio-somchai-somchai-scheduler-1
Last Alert
2026-08-19 23:20:09 UTC
Open Errors
0
Open Warnings
0
Info Events
0
Monitoring
Active
Edit project Implementation guide
Health

Endpoint Snapshot

LIVE

http://100.67.241.67:18080/health

Healthy
Status Code
200
Response Time
24 ms
Failures
0

Last checked: 2026-09-15 09:32:10 UTC

Recent Alerts

Somchai Scheduler Incident Feed

Somchai Scheduler · Health

Live health recovered

Info
Live endpoint recovered for Somchai Scheduler
Status: Resolved Occurrences: 1 Last seen: 2026-08-19 23:26:56 UTC
View raw incident details 
Project: Somchai Scheduler
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: 200
Response time: 8975ms
Recovered at: 2026-08-19T23:26:47.194073+00:00
Response: {"ok":true,"service":"somchai-api","db":"ok","qdrant":"ok","mode":"isolated-vps-station-manager"}
Somchai Scheduler · Health

Live health check failed

Info
Live endpoint is failing for Somchai Scheduler
Status: Resolved Occurrences: 1 Last seen: 2026-08-19 23:26:56 UTC
View raw incident details 
Project: Somchai Scheduler
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: no response
Response time: 14773ms
Consecutive failures: 2
Checked at: 2026-08-19T23:22:13.472011+00:00
Somchai Scheduler · Log

1 log error(s) detected

Error
- Root cause: AI analysis is temporarily unavailable, so Watchtower is sending a basic fallback summary. - Distinct errors: 1 - First signal: 2026-08-19T23:19:41.913446427Z raise e.OperationalError(str(last_exc)) - Recommended action: review the raw log excerpt below and try the analysis again later if needed. AI error: Cannot connect to host generativelanguage.googleapis.com:443 ssl:<ssl.SSLContext object at 0x71ade8c258d0> [Temporary failure in name res…
Status: Recorded Occurrences: 1 Last seen: 2026-08-19 23:24:26 UTC
View full analysis
- Root cause: AI analysis is temporarily unavailable, so Watchtower is sending a basic fallback summary. - Distinct errors: 1 - First signal: 2026-08-19T23:19:41.913446427Z raise e.OperationalError(str(last_exc)) - Recommended action: review the raw log excerpt below and try the analysis again later if needed. AI error: Cannot connect to host generativelanguage.googleapis.com:443 ssl:<ssl.SSLContext object at 0x71ade8c258d0> [Temporary failure in name resolution] Raw errors: --- Error 1 --- 2026-08-19T23:19:41.913446427Z raise e.OperationalError(str(last_exc)) 2026-08-19T23:19:41.913449562Z psycopg.OperationalError: [Errno -3] Temporary failure in name resolution
View raw incident details 
Fingerprint: d2ebc270195b
Occurrences: 1

2026-08-19T23:19:41.913446427Z     raise e.OperationalError(str(last_exc))
2026-08-19T23:19:41.913449562Z psycopg.OperationalError: [Errno -3] Temporary failure in name resolution
Somchai Scheduler · Health

Live health recovered

Info
Live endpoint recovered for Somchai Scheduler
Status: Resolved Occurrences: 1 Last seen: 2026-08-02 13:37:45 UTC
View raw incident details 
Project: Somchai Scheduler
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: 200
Response time: 28ms
Recovered at: 2026-08-02T13:37:45.081636+00:00
Response: {"ok":true,"service":"somchai-api","db":"ok","qdrant":"ok","mode":"isolated-vps-station-manager"}
Somchai Scheduler · Health

Live health check failed

Info
Live endpoint is failing for Somchai Scheduler
Status: Resolved Occurrences: 1 Last seen: 2026-08-02 13:37:45 UTC
View raw incident details 
Project: Somchai Scheduler
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: no response
Response time: 10999ms
Consecutive failures: 2
Checked at: 2026-08-02T13:28:17.080787+00:00
Somchai Scheduler · Log

1 log error(s) detected

Error
### Error 1: Database Connection Failure * **Root Cause**: The application container is unable to resolve the hostname of the PostgreSQL database server. This is a DNS (Domain Name System) lookup failure. * **Explanation**: The application tried to connect to the database using its name (e.g., `postgres-db.internal`), but the network service responsible for translating that name into an IP address failed. The application doesn't know where to find the dat…
Status: Recorded Occurrences: 1 Last seen: 2026-08-02 13:27:14 UTC
View full analysis
### Error 1: Database Connection Failure * **Root Cause**: The application container is unable to resolve the hostname of the PostgreSQL database server. This is a DNS (Domain Name System) lookup failure. * **Explanation**: The application tried to connect to the database using its name (e.g., `postgres-db.internal`), but the network service responsible for translating that name into an IP address failed. The application doesn't know where to find the database. * **To Investigate**: * Verify the database hostname is correct in the application's connection string or environment variables. * Check the DNS configuration of the Docker container and the host machine. * Ensure the container has network connectivity to the DNS server. * Confirm that the DNS server itself is operational and can resolve the database hostname. * **Severity**: **CRITICAL**. The application cannot connect to its database and is likely non-functional.
View raw incident details 
Fingerprint: d2ebc270195b
Occurrences: 1

2026-08-02T13:26:31.826112161Z     raise e.OperationalError(str(last_exc))
2026-08-02T13:26:31.826121405Z psycopg.OperationalError: [Errno -3] Temporary failure in name resolution
Somchai Scheduler · Health

Live health recovered

Info
Live endpoint recovered for Somchai Scheduler
Status: Resolved Occurrences: 1 Last seen: 2026-08-02 08:36:59 UTC
View raw incident details 
Project: Somchai Scheduler
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: 200
Response time: 29ms
Recovered at: 2026-08-02T08:36:59.083184+00:00
Response: {"ok":true,"service":"somchai-api","db":"ok","qdrant":"ok","mode":"isolated-vps-station-manager"}
Somchai Scheduler · Health

Live health check failed

Info
Live endpoint is failing for Somchai Scheduler
Status: Resolved Occurrences: 1 Last seen: 2026-08-02 08:36:59 UTC
View raw incident details 
Project: Somchai Scheduler
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: no response
Response time: 10998ms
Consecutive failures: 2
Checked at: 2026-08-02T05:47:45.082760+00:00
Somchai Scheduler · Health

Live health recovered

Info
Live endpoint recovered for Somchai Scheduler
Status: Resolved Occurrences: 1 Last seen: 2026-06-23 06:11:59 UTC
View raw incident details 
Project: Somchai Scheduler
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: 200
Response time: 28ms
Recovered at: 2026-06-23T06:11:59.484024+00:00
Response: {"ok":true,"service":"somchai-api","db":"ok","qdrant":"ok","mode":"isolated-vps-station-manager"}
Somchai Scheduler · Health

Live health check failed

Info
Live endpoint is failing for Somchai Scheduler
Status: Resolved Occurrences: 1 Last seen: 2026-06-23 06:11:59 UTC
View raw incident details 
Project: Somchai Scheduler
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: no response
Response time: 10996ms
Consecutive failures: 2
Checked at: 2026-06-23T06:02:52.475321+00:00
Somchai Scheduler · Log

1 log error(s) detected

Error
### Error 1: Database Connection Timeout * **Root Cause:** The application failed to establish a connection to its PostgreSQL database within the allowed time. The `psycopg` library, which the application uses to talk to the database, gave up after waiting for a response that never came. * **Simple Explanation:** The application tried to call the database, but the database didn't pick up the phone in time. * **Things to Investigate:** * **Network Issues:*…
Status: Recorded Occurrences: 1 Last seen: 2026-06-23 06:10:57 UTC
View full analysis
### Error 1: Database Connection Timeout * **Root Cause:** The application failed to establish a connection to its PostgreSQL database within the allowed time. The `psycopg` library, which the application uses to talk to the database, gave up after waiting for a response that never came. * **Simple Explanation:** The application tried to call the database, but the database didn't pick up the phone in time. * **Things to Investigate:** * **Network Issues:** Check if there are any network problems (e.g., firewall rules, DNS issues) preventing the application server from reaching the database server. * **Database Health:** Verify that the PostgreSQL database is running, healthy, and not overloaded. An overloaded database may be too slow to accept new connections. * **Configuration:** Double-check that the database hostname, port, and other connection details in the application's configuration are correct. * **Severity:** **CRITICAL**. The application cannot perform its core functions without a database connection.
View raw incident details 
Fingerprint: cee6e7c5115a
Occurrences: 1

2026-06-23T06:10:11.960947330Z psycopg.errors.ConnectionTimeout: connection timeout expired
Somchai Scheduler · Log

1 log error(s) detected

Error
**Error 1: Database Connection Timeout** * **Root Cause:** The application failed to establish a connection with its PostgreSQL database within the configured time limit. * **Explanation:** The application tried to contact its database to read or write information, but the database did not respond in time. This is like making a phone call and hanging up because no one answered. * **Potential Fixes:** * **Check Database Health:** Verify the PostgreSQL data…
Status: Recorded Occurrences: 1 Last seen: 2026-06-23 06:04:47 UTC
View full analysis
**Error 1: Database Connection Timeout** * **Root Cause:** The application failed to establish a connection with its PostgreSQL database within the configured time limit. * **Explanation:** The application tried to contact its database to read or write information, but the database did not respond in time. This is like making a phone call and hanging up because no one answered. * **Potential Fixes:** * **Check Database Health:** Verify the PostgreSQL database server is running, healthy, and not overloaded. * **Verify Network Connectivity:** Ensure there are no network issues (e.g., firewall rules, DNS problems) preventing the application container from reaching the database server. * **Verify Configuration:** Double-check that the application's database connection details (hostname, port, credentials) are correct. * **Severity:** **CRITICAL**. An inability to connect to the database will likely render the entire application or its core features non-functional.
View raw incident details 
Fingerprint: cee6e7c5115a
Occurrences: 1

2026-06-23T06:03:38.678652885Z psycopg.errors.ConnectionTimeout: connection timeout expired