# 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 locally while the server is offline. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/6617/beaconing-analytics-webhook

## Description

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.

## Health score

6/100 (Low), based on 3 of 4 factors.
- Maintained: 0 (last commit 2839 days ago)
- Popular: 0 (0 GitHub stars)
- Easy to install: 25 (0 install platforms, install notes, Docker image)

## Links

- Docker Hub: https://hub.docker.com/r/eucm/beaconing-analytics-webhook
- GitHub: https://github.com/e-ucm/beaconing-analytics-webhook
- Official website: http://e-ucm.github.io/a2

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/6617/beaconing-analytics-webhook), the self-hosted and open-source app directory.
