Beaconing Analytics Webhook

Beaconing Analytics Webhook is a self-hosted webhook service that receives event notifications and forwards analytics data to a central server, caching it…

  • Automation
  • Databases
  • Tools & Utilities
Beaconing Analytics Webhook is a self-hosted webhook service that receives event notifications and forwards analytics data to a central server, caching it locally while the server is offline. Built by the e-UCM research group for the H2020 BEACONING project, it lets you create and manage webhooks that notify your own endpoints, consolidating activity tracking in one place.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

6/100 Low

Maintained
0last commit 2839 days ago
Popular
00 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
0
Open issues
0
Last commit
2019-02-12
Latest release
v2.0
Activity
stale

Checked yesterday - source: GitHub (e-ucm/beaconing-analytics-webhook)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Managing webhooks Webhooks and events are created and deleted through HTTP routes; accessing the webhook interface requires a configured password. Events are stored locally and re-sent once the analytics server is reachable again. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I manage webhooks and events in Beaconing Analytics Webhook?

Webhooks and events are created and deleted through HTTP routes. Accessing the webhook interface requires a password configured in the analytics framework.

What happens to analytics data while the central server is unavailable?

The service stores analytics information locally until the server becomes available again. It then sends the stored analytics information to the server.

How do I send a custom collector event to registered webhooks?

Post the event body to the collector route for the event type. The webhook endpoints receive the body plus a header containing the event type.

Are Beaconing special events handled like normal webhooks?

No, the five special events are hardcoded and behave synchronously instead of using the normal async webhook workflow. They must be authenticated with a valid A2 Authentication header.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads