[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C3TKMGBAHT6WWC7D883M1":3,"skill-same:01M73C3TKMGBAHT6WWC7D883M1":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M73C3TKMGBAHT6WWC7D883M1","setup-uptime-checks",null,"Configure external uptime monitoring using Blackbox Exporter and Prometheus. Implement SSL certificate monitoring, HTTP endpoint health checks, and status pages for customer-facing visibility. Use when monitoring customer-facing endpoints such as APIs and websites, tracking SSL certificate expiration, validating service availability from multiple regions, creating public status pages, or meeting SLA requirements for uptime reporting.","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fsetup-uptime-checks\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: setup-uptime-checks\nlocale: caveman-lite\nsource_locale: en\nsource_commit: 82c77053\ntranslator: \"Julius Brussee homage — caveman\"\ntranslation_date: \"2026-05-03\"\ndescription: >\n  Configure external uptime monitoring using Blackbox Exporter and Prometheus.\n  Implement SSL certificate monitoring, HTTP endpoint health checks, and\n  status pages for customer-facing visibility. Use when monitoring\n  customer-facing endpoints such as APIs and websites, tracking SSL\n  certificate expiration, validating service availability from multiple\n  regions, creating public status pages, or meeting SLA requirements for\n  uptime reporting.\nlicense: MIT\nallowed-tools: Read Write Edit Bash Grep Glob\nmetadata:\n  author: Philipp Thoss\n  version: \"1.0\"\n  domain: observability\n  complexity: basic\n  language: multi\n  tags: uptime, blackbox-exporter, ssl-monitoring, status-page, health-checks\n---\n\n# Set Up Uptime Checks\n\nMonitor service availability from external vantage points and prevent SSL certificate expirations.\n\n## When to Use\n\n- Monitoring customer-facing endpoints (APIs, websites)\n- Tracking SSL certificate expiration\n- Validating service availability from multiple regions\n- Creating public status pages\n- Meeting SLA requirements for uptime reporting\n\n## Inputs\n\n- **Required**: List of HTTP\u002FHTTPS endpoints to monitor\n- **Required**: Prometheus instance for metric collection\n- **Optional**: Multiple geographic probe locations\n- **Optional**: Status page tool (Statuspage.io, Cachet, custom)\n- **Optional**: Alert notification channels (PagerDuty, Slack)\n\n## Procedure\n\n> See [Extended Examples](references\u002FEXAMPLES.md) for complete configuration files and templates.\n\n\n### Step 1: Deploy Blackbox Exporter\n\nInstall Blackbox Exporter via Docker or Kubernetes:\n\n```bash\n# Docker deployment\ndocker run -d \\\n  --name blackbox-exporter \\\n  -p 9115:9115 \\\n  -v $(pwd)\u002Fblackbox.yml:\u002Fetc\u002Fblackbox_exporter\u002Fconfig.yml \\\n  prom\u002Fblackbox-exporter:latest \\\n  --config.file=\u002Fetc\u002Fblackbox_exporter\u002Fconfig.yml\n```\n\nKubernetes deployment:\n\n```yaml\n# blackbox-exporter-deployment.yaml\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: blackbox-exporter\n  namespace: monitoring\nspec:\n  replicas: 1\n  selector:\n    matchLabels:\n      app: blackbox-exporter\n  template:\n    metadata:\n      labels:\n        app: blackbox-exporter\n    spec:\n      containers:\n      - name: blackbox-exporter\n        image: prom\u002Fblackbox-exporter:latest\n        ports:\n        - containerPort: 9115\n        volumeMounts:\n        - name: config\n          mountPath: \u002Fetc\u002Fblackbox_exporter\n      volumes:\n      - name: config\n        configMap:\n          name: blackbox-exporter-config\n---\napiVersion: v1\nkind: Service\nmetadata:\n  name: blackbox-exporter\n  namespace: monitoring\nspec:\n  selector:\n    app: blackbox-exporter\n  ports:\n  - port: 9115\n    targetPort: 9115\n```\n\n**Got:** Blackbox Exporter running and accessible on port 9115.\n\n**If fail:** Check firewall rules, ensure config volume is mounted correctly.\n\n### Step 2: Configure Blackbox Modules\n\nCreate `blackbox.yml` with various probe types:\n\n```yaml\n# blackbox.yml\nmodules:\n  # Basic HTTP 200 check\n  http_2xx:\n    prober: http\n    timeout: 5s\n    http:\n      valid_status_codes: [200]\n      method: GET\n      follow_redirects: true\n      preferred_ip_protocol: \"ip4\"\n\n  # HTTP with authentication\n  http_2xx_auth:\n    prober: http\n    timeout: 5s\n    http:\n      valid_status_codes: [200]\n      method: GET\n      headers:\n        Authorization: \"Bearer ${AUTH_TOKEN}\"\n\n  # API health check (expects JSON response)\n  http_json_health:\n    prober: http\n    timeout: 5s\n    http:\n      valid_status_codes: [200]\n      method: GET\n      fail_if_body_not_matches_regexp:\n        - '\"status\":\"healthy\"'\n\n  # SSL certificate check\n  http_2xx_ssl:\n    prober: http\n    timeout: 5s\n    http:\n      valid_status_codes: [200]\n      method: GET\n      tls_config:\n        insecure_skip_verify: false\n      fail_if_ssl_not_present: true\n\n  # TCP port check (e.g., database)\n  tcp_connect:\n    prober: tcp\n    timeout: 5s\n    tcp:\n      preferred_ip_protocol: \"ip4\"\n\n  # ICMP ping\n  icmp:\n    prober: icmp\n    timeout: 5s\n    icmp:\n      preferred_ip_protocol: \"ip4\"\n\n  # DNS resolution check\n  dns_google:\n    prober: dns\n    timeout: 5s\n    dns:\n      query_name: \"google.com\"\n      query_type: \"A\"\n      valid_rcodes:\n        - NOERROR\n```\n\nLoad config into Kubernetes:\n\n```bash\nkubectl create configmap blackbox-exporter-config \\\n  -n monitoring \\\n  --from-file=blackbox.yml \\\n  --dry-run=client -o yaml | kubectl apply -f -\n```\n\n**Got:** Multiple probe modules configured for different check types.\n\n**If fail:** Validate YAML syntax. Check Blackbox Exporter logs for config errors.\n\n### Step 3: Configure Prometheus Scrape\n\nAdd Blackbox targets to Prometheus config:\n\n```yaml\n# prometheus.yml\nscrape_configs:\n  # Blackbox exporter itself\n  - job_name: 'blackbox-exporter'\n    static_configs:\n      - targets: ['blackbox-exporter:9115']\n\n  # HTTP endpoint checks\n  - job_name: 'blackbox-http'\n    metrics_path: \u002Fprobe\n    params:\n      module: [http_2xx]\n    static_configs:\n      - targets:\n          - https:\u002F\u002Fapi.company.com\u002Fhealth\n          - https:\u002F\u002Fwww.company.com\n          - https:\u002F\u002Fapp.company.com\u002Flogin\n    relabel_configs:\n      - source_labels: [__address__]\n        target_label: __param_target\n      - source_labels: [__param_target]\n        target_label: instance\n      - target_label: __address__\n        replacement: blackbox-exporter:9115\n\n  # SSL certificate expiry checks\n  - job_name: 'blackbox-ssl'\n    metrics_path: \u002Fprobe\n    params:\n      module: [http_2xx_ssl]\n    static_configs:\n      - targets:\n          - https:\u002F\u002Fapi.company.com\n          - https:\u002F\u002Fwww.company.com\n    relabel_configs:\n      - source_labels: [__address__]\n        target_label: __param_target\n      - source_labels: [__param_target]\n        target_label: instance\n      - target_label: __address__\n        replacement: blackbox-exporter:9115\n\n  # TCP connectivity checks (databases, etc.)\n  - job_name: 'blackbox-tcp'\n    metrics_path: \u002Fprobe\n    params:\n      module: [tcp_connect]\n    static_configs:\n      - targets:\n          - postgres.internal:5432\n          - redis.internal:6379\n    relabel_configs:\n      - source_labels: [__address__]\n        target_label: __param_target\n      - source_labels: [__param_target]\n        target_label: instance\n      - target_label: __address__\n        replacement: blackbox-exporter:9115\n```\n\nReload Prometheus config:\n\n```bash\n# Reload Prometheus (if running in Docker)\ndocker exec prometheus kill -HUP 1\n\n# Or Kubernetes\nkubectl rollout restart deployment\u002Fprometheus -n monitoring\n```\n\n**Got:** Prometheus scraping Blackbox Exporter, metrics visible in Prometheus UI.\n\n**If fail:** Check Prometheus logs for scrape errors. Verify Blackbox Exporter is reachable.\n\n### Step 4: Create Uptime Alerts\n\nDefine alerting rules:\n\n```yaml\n# uptime-alerts.yml\ngroups:\n  - name: uptime\n    interval: 30s\n    rules:\n      - alert: EndpointDown\n        expr: probe_success == 0\n        for: 2m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"Endpoint {{ $labels.instance }} is down\"\n          description: \"{{ $labels.instance }} has been unreachable for 2 minutes.\"\n\n      - alert: SSLCertificateExpiringSoon\n        expr: (probe_ssl_earliest_cert_expiry - time()) \u002F 86400 \u003C 14\n        for: 1h\n        labels:\n          severity: warning\n        annotations:\n          summary: \"SSL certificate for {{ $labels.instance }} expires in {{ $value | humanizeDuration }}\"\n          description: \"Certificate expires on {{ $labels.instance }}. Renew soon.\"\n\n      - alert: SSLCertificateExpired\n        expr: (probe_ssl_earliest_cert_expiry - time()) \u003C 0\n        for: 5m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"SSL certificate for {{ $labels.instance }} has EXPIRED\"\n          description: \"URGENT: Certificate expired. Service may be inaccessible.\"\n\n      - alert: SlowResponseTime\n        expr: probe_http_duration_seconds > 3\n        for: 5m\n        labels:\n          severity: warning\n        annotations:\n          summary: \"Slow response from {{ $labels.instance }}\"\n          description: \"HTTP request took {{ $value }}s (threshold: 3s).\"\n\n      - alert: HTTPStatusNot200\n        expr: probe_http_status_code != 200\n        for: 2m\n        labels:\n          severity: warning\n        annotations:\n          summary: \"HTTP {{ $labels.instance }} returned {{ $value }}\"\n          description: \"Expected 200, got {{ $value }}.\"\n```\n\nLoad into Prometheus:\n\n```bash\n# Add to prometheus.yml\nrule_files:\n  - \u002Fetc\u002Fprometheus\u002Fuptime-alerts.yml\n\n# Reload\ndocker exec prometheus kill -HUP 1\n```\n\n**Got:** Alerts fire when endpoints are unreachable or SSL certs expiring.\n\n**If fail:** Check Prometheus alerts page for rule evaluation errors.\n\n### Step 5: Build Uptime Dashboard\n\nCreate Grafana dashboard:\n\n```json\n{\n  \"dashboard\": {\n    \"title\": \"Uptime Monitoring\",\n    \"panels\": [\n      {\n        \"title\": \"Endpoint Availability (7 days)\",\n# ... (see EXAMPLES.md for complete configuration)\n```\n\n**Got:** Dashboard showing uptime %, SSL expiry, response times.\n\n**If fail:** Check Prometheus data source in Grafana, verify metrics are being scraped.\n\n### Step 6: Set Up Status Page\n\nOption A: Use Statuspage.io (SaaS):\n\n```bash\n# Integrate with Statuspage.io API\ncurl -X POST https:\u002F\u002Fapi.statuspage.io\u002Fv1\u002Fpages\u002FPAGE_ID\u002Fincidents \\\n  -H \"Authorization: OAuth YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"incident\": {\n      \"name\": \"API Degradation\",\n      \"status\": \"investigating\",\n      \"impact_override\": \"minor\",\n      \"body\": \"We are investigating elevated error rates on the API.\"\n    }\n  }'\n```\n\nOption B: Self-hosted Cachet:\n\n```yaml\n# docker-compose.yml for Cachet\nversion: '3'\nservices:\n  cachet:\n    image: cachethq\u002Fdocker:latest\n    ports:\n# ... (see EXAMPLES.md for complete configuration)\n```\n\nOption C: Custom status page from Prometheus metrics:\n\n```html\n\u003C!-- Simple status page (served via Nginx or GitHub Pages) -->\n\u003C!DOCTYPE html>\n\u003Chtml>\n\u003Chead>\n  \u003Ctitle>Company Status\u003C\u002Ftitle>\n  \u003Cscript src=\"https:\u002F\u002Fcdn.jsdelivr.net\u002Fnpm\u002Faxios\u002Fdist\u002Faxios.min.js\">\u003C\u002Fscript>\n# ... (see EXAMPLES.md for complete configuration)\n```\n\n**Got:** Public status page shows current service status and incidents.\n\n**If fail:** Ensure status page URL is reachable by customers, not behind VPN.\n\n## Validation\n\n- [ ] Blackbox Exporter deployed and accessible\n- [ ] Prometheus scraping Blackbox metrics\n- [ ] Uptime checks configured for all critical endpoints\n- [ ] SSL certificate expiry alerts configured (14-day warning)\n- [ ] Alerts tested (simulate endpoint down, check alert fires)\n- [ ] Grafana dashboard shows uptime and SSL expiry\n- [ ] Status page accessible to customers\n- [ ] Alert notifications reach on-call engineers\n\n## Pitfalls\n\n- **Internal-only checks**: Blackbox Exporter inside cluster can't detect external DNS\u002Frouting issues. Deploy probes in multiple clouds\u002Fregions.\n- **Too frequent scraping**: Checking every 10 seconds generates load. 30-60s is usually sufficient.\n- **No SSL monitoring**: Expired certificates are embarrassing and preventable. Always monitor.\n- **Status page not automated**: Manually updating status pages during incidents wastes time. Automate from Prometheus alerts.\n- **False positives**: Single failed check shouldn't alert. Use `for: 2m` to avoid transient network blips.\n\n## Related Skills\n\n- `configure-alerting-rules` - create alerts for uptime failures\n- `setup-prometheus-monitoring` - Prometheus backend for Blackbox Exporter\n","# Set Up Uptime Checks\n\nMonitor service availability from external vantage points and prevent SSL certificate expirations.\n\n## When to Use\n\n- Monitoring customer-facing endpoints (APIs, websites)\n- Tracking SSL certificate expiration\n- Validating service availability from multiple regions\n- Creating public status pages\n- Meeting SLA requirements for uptime reporting\n\n## Inputs\n\n- **Required**: List of HTTP\u002FHTTPS endpoints to monitor\n- **Required**: Prometheus instance for metric collection\n- **Optional**: Multiple geographic probe locations\n- **Optional**: Status page tool (Statuspage.io, Cachet, custom)\n- **Optional**: Alert notification channels (PagerDuty, Slack)\n\n## Procedure\n\n> See [Extended Examples](references\u002FEXAMPLES.md) for complete configuration files and templates.\n\n\n### Step 1: Deploy Blackbox Exporter\n\nInstall Blackbox Exporter via Docker or Kubernetes:\n\n```bash\n# Docker deployment\ndocker run -d \\\n  --name blackbox-exporter \\\n  -p 9115:9115 \\\n  -v $(pwd)\u002Fblackbox.yml:\u002Fetc\u002Fblackbox_exporter\u002Fconfig.yml \\\n  prom\u002Fblackbox-exporter:latest \\\n  --config.file=\u002Fetc\u002Fblackbox_exporter\u002Fconfig.yml\n```\n\nKubernetes deployment:\n\n```yaml\n# blackbox-exporter-deployment.yaml\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: blackbox-exporter\n  namespace: monitoring\nspec:\n  replicas: 1\n  selector:\n    matchLabels:\n      app: blackbox-exporter\n  template:\n    metadata:\n      labels:\n        app: blackbox-exporter\n    spec:\n      containers:\n      - name: blackbox-exporter\n        image: prom\u002Fblackbox-exporter:latest\n        ports:\n        - containerPort: 9115\n        volumeMounts:\n        - name: config\n          mountPath: \u002Fetc\u002Fblackbox_exporter\n      volumes:\n      - name: config\n        configMap:\n          name: blackbox-exporter-config\n---\napiVersion: v1\nkind: Service\nmetadata:\n  name: blackbox-exporter\n  namespace: monitoring\nspec:\n  selector:\n    app: blackbox-exporter\n  ports:\n  - port: 9115\n    targetPort: 9115\n```\n\n**Got:** Blackbox Exporter running and accessible on port 9115.\n\n**If fail:** Check firewall rules, ensure config volume is mounted correctly.\n\n### Step 2: Configure Blackbox Modules\n\nCreate `blackbox.yml` with various probe types:\n\n```yaml\n# blackbox.yml\nmodules:\n  # Basic HTTP 200 check\n  http_2xx:\n    prober: http\n    timeout: 5s\n    http:\n      valid_status_codes: [200]\n      method: GET\n      follow_redirects: true\n      preferred_ip_protocol: \"ip4\"\n\n  # HTTP with authentication\n  http_2xx_auth:\n    prober: http\n    timeout: 5s\n    http:\n      valid_status_codes: [200]\n      method: GET\n      headers:\n        Authorization: \"Bearer ${AUTH_TOKEN}\"\n\n  # API health check (expects JSON response)\n  http_json_health:\n    prober: http\n    timeout: 5s\n    http:\n      valid_status_codes: [200]\n      method: GET\n      fail_if_body_not_matches_regexp:\n        - '\"status\":\"healthy\"'\n\n  # SSL certificate check\n  http_2xx_ssl:\n    prober: http\n    timeout: 5s\n    http:\n      valid_status_codes: [200]\n      method: GET\n      tls_config:\n        insecure_skip_verify: false\n      fail_if_ssl_not_present: true\n\n  # TCP port check (e.g., database)\n  tcp_connect:\n    prober: tcp\n    timeout: 5s\n    tcp:\n      preferred_ip_protocol: \"ip4\"\n\n  # ICMP ping\n  icmp:\n    prober: icmp\n    timeout: 5s\n    icmp:\n      preferred_ip_protocol: \"ip4\"\n\n  # DNS resolution check\n  dns_google:\n    prober: dns\n    timeout: 5s\n    dns:\n      query_name: \"google.com\"\n      query_type: \"A\"\n      valid_rcodes:\n        - NOERROR\n```\n\nLoad config into Kubernetes:\n\n```bash\nkubectl create configmap blackbox-exporter-config \\\n  -n monitoring \\\n  --from-file=blackbox.yml \\\n  --dry-run=client -o yaml | kubectl apply -f -\n```\n\n**Got:** Multiple probe modules configured for different check types.\n\n**If fail:** Validate YAML syntax. Check Blackbox Exporter logs for config errors.\n\n### Step 3: Configure Prometheus Scrape\n\nAdd Blackbox targets to Prometheus config:\n\n```yaml\n# prometheus.yml\nscrape_configs:\n  # Blackbox exporter itself\n  - job_name: 'blackbox-exporter'\n    static_configs:\n      - targets: ['blackbox-exporter:9115']\n\n  # HTTP endpoint checks\n  - job_name: 'blackbox-http'\n    metrics_path: \u002Fprobe\n    params:\n      module: [http_2xx]\n    static_configs:\n      - targets:\n          - https:\u002F\u002Fapi.company.com\u002Fhealth\n          - https:\u002F\u002Fwww.company.com\n          - https:\u002F\u002Fapp.company.com\u002Flogin\n    relabel_configs:\n      - source_labels: [__address__]\n        target_label: __param_target\n      - source_labels: [__param_target]\n        target_label: instance\n      - target_label: __address__\n        replacement: blackbox-exporter:9115\n\n  # SSL certificate expiry checks\n  - job_name: 'blackbox-ssl'\n    metrics_path: \u002Fprobe\n    params:\n      module: [http_2xx_ssl]\n    static_configs:\n      - targets:\n          - https:\u002F\u002Fapi.company.com\n          - https:\u002F\u002Fwww.company.com\n    relabel_configs:\n      - source_labels: [__address__]\n        target_label: __param_target\n      - source_labels: [__param_target]\n        target_label: instance\n      - target_label: __address__\n        replacement: blackbox-exporter:9115\n\n  # TCP connectivity checks (databases, etc.)\n  - job_name: 'blackbox-tcp'\n    metrics_path: \u002Fprobe\n    params:\n      module: [tcp_connect]\n    static_configs:\n      - targets:\n          - postgres.internal:5432\n          - redis.internal:6379\n    relabel_configs:\n      - source_labels: [__address__]\n        target_label: __param_target\n      - source_labels: [__param_target]\n        target_label: instance\n      - target_label: __address__\n        replacement: blackbox-exporter:9115\n```\n\nReload Prometheus config:\n\n```bash\n# Reload Prometheus (if running in Docker)\ndocker exec prometheus kill -HUP 1\n\n# Or Kubernetes\nkubectl rollout restart deployment\u002Fprometheus -n monitoring\n```\n\n**Got:** Prometheus scraping Blackbox Exporter, metrics visible in Prometheus UI.\n\n**If fail:** Check Prometheus logs for scrape errors. Verify Blackbox Exporter is reachable.\n\n### Step 4: Create Uptime Alerts\n\nDefine alerting rules:\n\n```yaml\n# uptime-alerts.yml\ngroups:\n  - name: uptime\n    interval: 30s\n    rules:\n      - alert: EndpointDown\n        expr: probe_success == 0\n        for: 2m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"Endpoint {{ $labels.instance }} is down\"\n          description: \"{{ $labels.instance }} has been unreachable for 2 minutes.\"\n\n      - alert: SSLCertificateExpiringSoon\n        expr: (probe_ssl_earliest_cert_expiry - time()) \u002F 86400 \u003C 14\n        for: 1h\n        labels:\n          severity: warning\n        annotations:\n          summary: \"SSL certificate for {{ $labels.instance }} expires in {{ $value | humanizeDuration }}\"\n          description: \"Certificate expires on {{ $labels.instance }}. Renew soon.\"\n\n      - alert: SSLCertificateExpired\n        expr: (probe_ssl_earliest_cert_expiry - time()) \u003C 0\n        for: 5m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"SSL certificate for {{ $labels.instance }} has EXPIRED\"\n          description: \"URGENT: Certificate expired. Service may be inaccessible.\"\n\n      - alert: SlowResponseTime\n        expr: probe_http_duration_seconds > 3\n        for: 5m\n        labels:\n          severity: warning\n        annotations:\n          summary: \"Slow response from {{ $labels.instance }}\"\n          description: \"HTTP request took {{ $value }}s (threshold: 3s).\"\n\n      - alert: HTTPStatusNot200\n        expr: probe_http_status_code != 200\n        for: 2m\n        labels:\n          severity: warning\n        annotations:\n          summary: \"HTTP {{ $labels.instance }} returned {{ $value }}\"\n          description: \"Expected 200, got {{ $value }}.\"\n```\n\nLoad into Prometheus:\n\n```bash\n# Add to prometheus.yml\nrule_files:\n  - \u002Fetc\u002Fprometheus\u002Fuptime-alerts.yml\n\n# Reload\ndocker exec prometheus kill -HUP 1\n```\n\n**Got:** Alerts fire when endpoints are unreachable or SSL certs expiring.\n\n**If fail:** Check Prometheus alerts page for rule evaluation errors.\n\n### Step 5: Build Uptime Dashboard\n\nCreate Grafana dashboard:\n\n```json\n{\n  \"dashboard\": {\n    \"title\": \"Uptime Monitoring\",\n    \"panels\": [\n      {\n        \"title\": \"Endpoint Availability (7 days)\",\n# ... (see EXAMPLES.md for complete configuration)\n```\n\n**Got:** Dashboard showing uptime %, SSL expiry, response times.\n\n**If fail:** Check Prometheus data source in Grafana, verify metrics are being scraped.\n\n### Step 6: Set Up Status Page\n\nOption A: Use Statuspage.io (SaaS):\n\n```bash\n# Integrate with Statuspage.io API\ncurl -X POST https:\u002F\u002Fapi.statuspage.io\u002Fv1\u002Fpages\u002FPAGE_ID\u002Fincidents \\\n  -H \"Authorization: OAuth YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"incident\": {\n      \"name\": \"API Degradation\",\n      \"status\": \"investigating\",\n      \"impact_override\": \"minor\",\n      \"body\": \"We are investigating elevated error rates on the API.\"\n    }\n  }'\n```\n\nOption B: Self-hosted Cachet:\n\n```yaml\n# docker-compose.yml for Cachet\nversion: '3'\nservices:\n  cachet:\n    image: cachethq\u002Fdocker:latest\n    ports:\n# ... (see EXAMPLES.md for complete configuration)\n```\n\nOption C: Custom status page from Prometheus metrics:\n\n```html\n\u003C!-- Simple status page (served via Nginx or GitHub Pages) -->\n\u003C!DOCTYPE html>\n\u003Chtml>\n\u003Chead>\n  \u003Ctitle>Company Status\u003C\u002Ftitle>\n  \u003Cscript src=\"https:\u002F\u002Fcdn.jsdelivr.net\u002Fnpm\u002Faxios\u002Fdist\u002Faxios.min.js\">\u003C\u002Fscript>\n# ... (see EXAMPLES.md for complete configuration)\n```\n\n**Got:** Public status page shows current service status and incidents.\n\n**If fail:** Ensure status page URL is reachable by customers, not behind VPN.\n\n## Validation\n\n- [ ] Blackbox Exporter deployed and accessible\n- [ ] Prometheus scraping Blackbox metrics\n- [ ] Uptime checks configured for all critical endpoints\n- [ ] SSL certificate expiry alerts configured (14-day warning)\n- [ ] Alerts tested (simulate endpoint down, check alert fires)\n- [ ] Grafana dashboard shows uptime and SSL expiry\n- [ ] Status page accessible to customers\n- [ ] Alert notifications reach on-call engineers\n\n## Pitfalls\n\n- **Internal-only checks**: Blackbox Exporter inside cluster can't detect external DNS\u002Frouting issues. Deploy probes in multiple clouds\u002Fregions.\n- **Too frequent scraping**: Checking every 10 seconds generates load. 30-60s is usually sufficient.\n- **No SSL monitoring**: Expired certificates are embarrassing and preventable. Always monitor.\n- **Status page not automated**: Manually updating status pages during incidents wastes time. Automate from Prometheus alerts.\n- **False positives**: Single failed check shouldn't alert. Use `for: 2m` to avoid transient network blips.\n\n## Related Skills\n\n- `configure-alerting-rules` - create alerts for uptime failures\n- `setup-prometheus-monitoring` - Prometheus backend for Blackbox Exporter\n",{"name":5,"locale":23,"license":14,"metadata":24,"translator":31,"description":32,"allowed-tools":33,"source_commit":34,"source_locale":35,"translation_date":36},"caveman-lite",{"tags":25,"author":26,"domain":27,"version":28,"language":29,"complexity":30},"uptime, blackbox-exporter, ssl-monitoring, status-page, health-checks","Philipp Thoss","observability","1.0","multi","basic","Julius Brussee homage — caveman","Configure external uptime monitoring using Blackbox Exporter and Prometheus. Implement SSL certificate monitoring, HTTP endpoint health checks, and status pages for customer-facing visibility. Use when monitoring customer-facing endpoints such as APIs and websites, tracking SSL certificate expiration, validating service availability from multiple regions, creating public status pages, or meeting SLA requirements for uptime reporting.\n","Read Write Edit Bash Grep Glob","82c77053","en","2026-05-03","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fsetup-uptime-checks",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add roohe\u002Fagentic-super-skills --skill setup-uptime-checks",{"tool":51,"command":52},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill setup-uptime-checks",{"tool":54,"command":55},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill setup-uptime-checks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fsetup-uptime-checks\u002FSKILL.md",true,[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002FEXAMPLES.md","REFERENCE","参考文档",9053,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fsetup-uptime-checks\u002Freferences\u002FEXAMPLES.md",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]