Pingdom

Build me a focused uptime, errors, logs and status pages workflow for the personal core of Pingdom. Requirements:

- Use Go, PostgreSQL, ClickHouse, a Next.js 15 dashboard, and Docker Compose. Model accounts, source transactions, ledger entries, reconciliations, and reports; store source IDs and timestamps for each.
- Paid product context: Run independent uptime and transaction checks with a simple status view. Build only this DIY scope: Run independent uptime and transaction checks, receive bounded error or log events, alert through one channel, and publish an honest status page.
- Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies.
- Run checks from one independently hosted worker and store raw results plus incident state transitions.
- Send deduplicated alerts to email or one webhook destination with recovery notifications. Create services, maintenance windows, incidents, subscribers, and a public status page. Add bounded event ingestion for application errors with sampling and sensitive-field scrubbing.
- Use a local web page with input, progress, review, and export views. Required input or access: server outside the monitored failure domain; optional ClickHouse.
- Recovery: Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: global probes, transaction infrastructure, alerts, reporting, and SolarWinds operations; global probe network. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Pingdom

## Project scope
Run independent uptime and transaction checks, receive bounded error or log events, alert through one channel, and publish an honest status page.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Pingdom, run independent uptime and transaction checks with a simple status view. The hard boundary is global probes, transaction infrastructure, alerts, reporting, and solarwinds operations, plus independent infrastructure and reliable alerting.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- server outside the monitored failure domain
- PostgreSQL
- optional ClickHouse
- email or webhook destination
- public HTTPS

## Stack and architecture
- Use Go, PostgreSQL, ClickHouse, a Next.js 15 dashboard, and Docker Compose.
- Model accounts, source transactions, ledger entries, reconciliations, and reports; store source IDs and timestamps for each.
- Interface for this uptime, errors, logs and status pages workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: global probes, transaction infrastructure, alerts, reporting, and SolarWinds operations.

## Agent implementation rules
- Project rule, data: Model accounts, source transactions, ledger entries, reconciliations, and reports; store source IDs and timestamps for each.
- Project rule, behavior: Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies.
- Project rule, recovery: Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this uptime, errors, logs and status pages operation with sample or user-owned data: Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies.
- Show a concrete result or export: Provide health checks, retention settings, exports, backups, and a test-alert function.
- State the practical limit: global probes, transaction infrastructure, alerts, reporting, and SolarWinds operations.

## Engineering roadmap
1. Phase 1, architecture and data: Use Go, PostgreSQL, ClickHouse, a Next.js 15 dashboard, and Docker Compose. Model accounts, source transactions, ledger entries, reconciliations, and reports; store source IDs and timestamps for each.
2. Phase 2, implement: Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies.
3. Phase 3, implement: Run checks from one independently hosted worker and store raw results plus incident state transitions.
4. Phase 4, review and output: Send deduplicated alerts to email or one webhook destination with recovery notifications. Provide health checks, retention settings, exports, backups, and a test-alert function.
5. Phase 5, recovery and acceptance: Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies. Verify this invariant with a saved fixture: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs. State the practical limit: global probes, transaction infrastructure, alerts, reporting, and SolarWinds operations.

## Paid-product capabilities outside this build
- global probes, transaction infrastructure, alerts, reporting, and SolarWinds operations
- global probe network
- phone and SMS delivery
- massive retention
- advanced incident response and support

## Implementation prompt
Build me a focused uptime, errors, logs and status pages workflow for the personal core of Pingdom. Requirements:

- Use Go, PostgreSQL, ClickHouse, a Next.js 15 dashboard, and Docker Compose. Model accounts, source transactions, ledger entries, reconciliations, and reports; store source IDs and timestamps for each.
- Paid product context: Run independent uptime and transaction checks with a simple status view. Build only this DIY scope: Run independent uptime and transaction checks, receive bounded error or log events, alert through one channel, and publish an honest status page.
- Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies.
- Run checks from one independently hosted worker and store raw results plus incident state transitions.
- Send deduplicated alerts to email or one webhook destination with recovery notifications. Create services, maintenance windows, incidents, subscribers, and a public status page. Add bounded event ingestion for application errors with sampling and sensitive-field scrubbing.
- Use a local web page with input, progress, review, and export views. Required input or access: server outside the monitored failure domain; optional ClickHouse.
- Recovery: Implement HTTP, TCP, DNS, TLS-expiry, and heartbeat checks with explicit timeout and retry policies.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: global probes, transaction infrastructure, alerts, reporting, and SolarWinds operations; global probe network. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.