Overview - Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
30255
f1e994e9 Added structured alert fields to email analytics job completion log ref https://linear.app/ghost/issue/HKG-1990/add-baseline-execution-logging-to-existing-background-jobs - The `ghost/email-analytics-failing` Elastic rule counted log lines matching `[EmailAnalytics] Job complete`. HKG-1990 reworded that string to the shared `[Background Job]` format, so the count went to zero and the rule fired continuously. Mailgun ingestion was never affected. - Rewording a human-readable message should not be able to break an alert. This emits the completion as structured fields so the rule can key on `system.event` and `system.job_type` instead of a message regex. - Uses the `system: {event, job_type, duration_ms}` shape the jobs service already logs completions with (per review), extended with `task` for the sub-fetch and `event_count` for the processed events. `system.*` is the namespace existing Elastic rules already query, and remote-flags and gifts emit `system.event` in production today, so indexing is verifiable up front. - No behaviour change: same call site, same conditions, same message text. `_logJobCompletion` still returns early at zero events, so these documents continue to mean "events were actually processed". - Only this one call site is converted; the other background jobs keep their message-only logging for now.
by Princi Ver...
Failed
30255
a3e9fdd0 Added structured alert fields to email analytics job completion log ref https://linear.app/ghost/issue/HKG-1990/add-baseline-execution-logging-to-existing-background-jobs - The `ghost/email-analytics-failing` Elastic rule counted log lines matching `[EmailAnalytics] Job complete`. HKG-1990 reworded that string to the shared `[Background Job]` format, so the count went to zero and the rule fired continuously. Mailgun ingestion was never affected. - Rewording a human-readable message should not be able to break an alert. This emits the completion as structured fields so the rule can key on `system.event` and `system.job_type` instead of a message regex. - Uses the `system: {event, job_type, duration_ms}` shape the jobs service already logs completions with (per review), extended with `task` for the sub-fetch and `event_count` for the processed events. `system.*` is the namespace existing Elastic rules already query, and remote-flags and gifts emit `system.event` in production today, so indexing is verifiable up front. - No behaviour change: same call site, same conditions, same message text. `_logJobCompletion` still returns early at zero events, so these documents continue to mean "events were actually processed". - Only this one call site is converted; the other background jobs keep their message-only logging for now.
by Princi Ver...
Succeeded
30255
4a030c9c Added structured alert fields to email analytics job completion log ref https://linear.app/ghost/issue/HKG-1990/add-baseline-execution-logging-to-existing-background-jobs - The `ghost/email-analytics-failing` Elastic rule counted log lines matching `[EmailAnalytics] Job complete`. HKG-1990 reworded that string to the shared `[Background Job]` format, so the count went to zero and the rule fired continuously. Mailgun ingestion was never affected. - Rewording a human-readable message should not be able to break an alert. This emits the completion as structured fields, so the rule can key on `type: "job.completed"` and `job_name` instead of a message regex. - `type: "job.completed"` is the convention the scheduler and customer certificate rules already alert on. Ghost core has not used it until now. - No behaviour change: same call site, same conditions, same message text. `_logJobCompletion` still returns early at zero events, so these documents continue to mean "events were actually processed". - Only this one call site is converted. The other background jobs keep their message-only logging until the field names are confirmed against the logs-ghost ingest pipeline.
by Princi Ver...
Succeeded
30255
4a030c9c Added structured alert fields to email analytics job completion log ref https://linear.app/ghost/issue/HKG-1990/add-baseline-execution-logging-to-existing-background-jobs - The `ghost/email-analytics-failing` Elastic rule counted log lines matching `[EmailAnalytics] Job complete`. HKG-1990 reworded that string to the shared `[Background Job]` format, so the count went to zero and the rule fired continuously. Mailgun ingestion was never affected. - Rewording a human-readable message should not be able to break an alert. This emits the completion as structured fields, so the rule can key on `type: "job.completed"` and `job_name` instead of a message regex. - `type: "job.completed"` is the convention the scheduler and customer certificate rules already alert on. Ghost core has not used it until now. - No behaviour change: same call site, same conditions, same message text. `_logJobCompletion` still returns early at zero events, so these documents continue to mean "events were actually processed". - Only this one call site is converted. The other background jobs keep their message-only logging until the field names are confirmed against the logs-ghost ingest pipeline.
by Princi Ver...