> ## Documentation Index
> Fetch the complete documentation index at: https://docs.appsignal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vector

<Warning>
  🔐 Do not send <strong>Personal Identifiable Information (PII)</strong> to AppSignal. Filter PII (e.g., names, emails) from logs and use an ID, hash, or pseudonymized identifier instead. <br /> <br /> For **HIPAA-covered entities**, more information about signing a Business Associate Agreement (BAA) can be found in our [Business Add-Ons documentation](/support/business-add-ons).
</Warning>

AppSignal can ingest logs via your Vector instance.

To send data from your Vector sources to AppSignal, you need to set up the AppSignal Vector sink in your Vector configuration and create a new Vector logging source.

You can read more about AppSignal's Vector integration in our [Vector documentation](/vector).

## Configure Sink

To do this, create a new Vector sink with the type `appsignal`. You can define your logging sources via the `inputs` attribute in this sink. To successfully send logging data to AppSignal, you must also provide your [app-level Push API Key](https://appsignal.com/redirect-to/app?to=api_keys\&key_tab=app) via the `push_api_key` attribute:

<CodeGroup>
  ```toml TOML theme={null}
  # vector.toml example
  # Other config here
  # Add this AppSignal sink section
  [sinks.appsignal]
  type = "appsignal"
  inputs = [ "internal_logs", "your_log_source" ]
  push_api_key = "YOUR_APP_LEVEL_API_KEY"
  ```
</CodeGroup>

## Create Logging Source

Once your Vector Sink is configured, create a new [logging source](/logging/configuration#creating-a-log-source) and select Vector as the platform.

Once created, AppSignal Logging will begin to display the configured logs. If you cannot see any logs, please [contact us](mailto:support@appsignal.com) for support.