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

# Signal Sciences source plugin

> Configure the Signal Sciences source plugin in Chronosphere Telemetry Pipeline to ingest logs for processing and routing.

export const entity_0 = "Signal Sciences source plugin"

export const plugin_0 = "Signal Sciences source plugin"

<Info>
  This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.
</Info>

The Signal Sciences [source plugin](/ingest/pipeline/plugins/source-plugins)
(name: `http_loader`) lets you query the Signal Sciences API to ingest data into
a telemetry pipeline.

This is a [pull-based](/ingest/pipeline/plugins/source-plugins#push-based-and-pull-based-source-plugins) source plugin.

<Note>
  This plugin doesn't support the use of a
  [descriptive metadata name](/ingest/pipeline/plugins#descriptive-names) in the
  Pipeline Builder interface.
</Note>

<Note>
  This plugin doesn't support duplicates of itself within the same pipeline.
  Additionally, this plugin can't be used in combination with these source plugins
  within the same telemetry pipeline:

  * [Absolute](/ingest/pipeline/plugins/source-plugins/absolute)
  * [HTTP API collector](/ingest/pipeline/plugins/source-plugins/http-collector)
  * [Mandiant ASM](/ingest/pipeline/plugins/source-plugins/mandiant-asm)
  * [Okta](/ingest/pipeline/plugins/source-plugins/okta)
  * [Slack](/ingest/pipeline/plugins/source-plugins/slack)
  * [Vectra M365](/ingest/pipeline/plugins/source-plugins/vectram365)
</Note>

## Supported telemetry types

The {plugin_0} for Chronosphere Telemetry Pipeline supports these telemetry types:

|                    Logs                    |             Metrics             |              Traces             |
| :----------------------------------------: | :-----------------------------: | :-----------------------------: |
| <Icon icon="circle-check" color="green" /> | <Icon icon="ban" color="red" /> | <Icon icon="ban" color="red" /> |

## Configuration parameters

Use the parameters in this section to configure the {entity_0}. The
Telemetry Pipeline web interface uses the items in the **Name** column to
describe these parameters. [Pipeline configuration files](/ingest/pipeline/v2/configure/config-files)
use the items in the **Key** column as YAML keys.

### General

The configured fields replace sections of the `url` field in the YAML file in the
following way:

```text theme={null}
https://dashboard.signalsciences.net{{with
  .Response.Body.next.uri}}.{{else}}/api/v0/corps/CORP/sites/SITENAME/requests?q=SEARCH_QUERY{{end}}
```

| Name                 | Key    | Description                                                               | Default |
| -------------------- | ------ | ------------------------------------------------------------------------- | ------- |
| **Corp**             | *none* | Required. Added to `url` field.                                           | *none*  |
| **Site Name**        | *none* | Required. Added to `url` field.                                           | *none*  |
| **Search Query**     | *none* | The query to pass to the Signal Sciences API, as part of the `url` field. | *none*  |
| **API Access Token** | *none* | Your Signal Sciences API access token.                                    | *none*  |

### Advanced

| Name                    | Key             | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Default |
| ----------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
| **Memory Buffer Limit** | `mem_buf_limit` | Sets a limit for how much buffered data the plugin can write to memory, which affects backpressure. This value must follow Fluent Bit's rules for [unit sizes](https://docs.fluentbit.io/manual/administration/configuring-fluent-bit#unit-sizes). If unspecified, no limit is enforced. <p />For v2 pipelines, this parameter affects only pipelines with the Deployment or DaemonSet [workload](/ingest/pipeline/v2/configure/kubernetes/workloads) type. To learn more, see the v2 [backpressure](/ingest/pipeline/v2/configure/backpressure) guide. <p />For v3 pipelines, this parameter is independent from the [OpenTelemetry `memory_limiter` and `batch` processors](/ingest/pipeline/v3#route-data-from-fluent-bit-to-opentelemetry). | *none*  |