Skip to content

Implement healthcheck monitoring for WhatsApp proxy container #440

Open

Description

@umairchudary3-art

Summary

Set up automated monitoring and alerts for the healthcheck status of the WhatsApp proxy container, based on the logic in proxy/src/healthcheck.sh.

Details

  • The healthcheck.sh script performs a Layer 4 healthcheck for the *.whatsapp.net backend via HAProxy stats on localhost:8199.
  • The script checks if the health check returned anything other than "Layer4 check passed" for *.whatsapp_net entries and will exit with a non-zero code if failures are detected.
  • When the check fails, an error message is printed and the container exits with code -1.

Tasks

  • Review and document the current healthcheck script implementation.
  • Set up monitoring to detect failed healthchecks, triggering an alert or notification whenever the script exits with failure.
  • Optionally, extend healthcheck logic for other backends or protocols if needed.
  • Ensure logging captures details from failed checks for diagnostics.

Reference

Acceptance Criteria

  • Monitoring and alerting are enabled for healthcheck failures.
  • Failure logs include description output for diagnosis.
  • No changes to functional healthcheck logic unless explicitly requested.

Activity

  1. sambaccessnow commented on Nov 29, 2025

    @sambaccessnow

    this is a basic feature will allow a wide usage of proxies for whatsapp.
    The healthcheck will inform the mantainer (and maybe also the user in future) on how the status of the proxy is

    Right now if the proxy doesn't work the client doesn't have any feedback from the app, it's just not receiving any messages anymore and it's an issue

    To mitigate this and improve the monitoring the proxy should be able to be inform via an healthcheck if the proxy operations are not working correctly

    👍 +1 for this

  2. getreidap-png commented on Nov 29, 2025

    @getreidap-png

    HBI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions