> For the complete documentation index, see [llms.txt](https://docs.xygeni.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xygeni.io/xygeni-products/anomaly-detection/xygeni-sensors/xygeni-sensor-for-github/github-audit-log-processing.md).

# GitHub Audit Log Processing

As an alternative to the [Xygeni Sensor for GitHub](/xygeni-products/anomaly-detection/xygeni-sensors/xygeni-sensor-for-github.md) you can use [GitHub Webhooks](https://docs.github.com/en/webhooks-and-events/webhooks/webhook-events-and-payloads).

The sensor is a [GitHub App](https://docs.github.com/en/apps/using-github-apps/about-using-github-apps) that extends GitHub’s functionality. By defining a Webhook, GitHub will send a real-time webhook event to Xygeni for subscribed events.

In any of those approaches, when Xygeni detects an unusual activity, it will raise an alert for tracking the origin and taking immediate action to mitigate the risk and prevent further damage.

See [Webhook events](https://docs.github.com/en/webhooks-and-events/webhooks/webhook-events-and-payloads) for further information on the events and payloads sent from GitHub to Xygeni platform.

{% hint style="info" %}
The webhook URL is `https://api.xygeni.io/githubapp/webhook` for the Xygeni cloud platform. The webhook is secured with a shared secret and TLS, following the recommendations in [Securing your webhooks](https://docs.github.com/en/webhooks-and-events/webhooks/securing-your-webhooks).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xygeni.io/xygeni-products/anomaly-detection/xygeni-sensors/xygeni-sensor-for-github/github-audit-log-processing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.