> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/appliances/syslog-forwarder/onboarding-syslog-data.md).

# Onboarding Syslog Data

Once your **Syslog Forwarder VM** is deployed and configured, it is ready to accept syslog log sources.

***

## Sending Syslog Data

* Each log source should be configured to send syslog traffic to the **forwarder’s IP address**.
* Syslog ports are allocated starting from **60,000**.

Examples:

* Log Source 1 → Port **60,000**
* Log Source 2 → Port **60,001**
* Log Source 3 → Port **60,002**

This approach ensures each onboarded device uses a unique port for separation and management.

***

## Request Activation with ThreatDefence Support

After configuring your devices to send logs, raise a request with ThreatDefence Support so the sources can be activated in our backend.

**Steps to Raise a Ticket**:

1. Go to the **Service Desk** portal.
2. Create a new ticket with:
   * **Category:** `Onboarding`
   * **Sub-Category:** `Syslog Log Sources`
3. Provide the following details:
   * **Source IP address** of the device sending logs.
   * **Make/Model** of the data source (e.g., Cisco ASA, Palo Alto firewall, Fortinet, etc.).

ThreatDefence SOC will validate the request and enable the log source for ingestion into the platform.

***

Once enabled, events will be visible in the ThreatDefence Analyst Console and can be correlated with existing detections and dashboards.


---

# 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.threatdefence.com/appliances/syslog-forwarder/onboarding-syslog-data.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.