# Blueprints

Each Blueprint applies common transformations—like JSON parsing, timestamp normalization, or Windows event standardization—and can be added to a pipeline in one click. They’re pre-built processor bundles you can add with a single click and modify as you wish.

Blueprints enable you to:

* **Standardize** data processing across your organization
* **Reduce** development time by reusing proven processor configurations
* **Transform** telemetry data with pre-configured processing pipelines
* **Share** best practices across teams and projects

### What are Blueprints?

Blueprints are **ready-to-use pre-built processor bundles** stored in a shared library that can be accessed by any project in your Bindplane instance.

**Example Bundle Use Cases:**

* **Google SecOps Standardization**: A bundle that standardizes security logs for Google SecOps
* **Palo Alto Threat Logs Parsing**: A bundle that parses and processes Palo Alto threat logs
* **JSON Parsing and Reduction**: A bundle that parses JSON logs and reduces data volume

View all the **available Blueprints** below.

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/Ytv3LJH4aA22zif99yva/blueprints-2.png" alt=""><figcaption></figcaption></figure>

### Key Features

#### Public Library Access

* Blueprints are stored in a **public account**, separate from project-specific resources
* Available to all projects and organizations in your Bindplane instance
* Managed centrally by administrators with appropriate permissions

#### License Compatibility

* Blueprints include license compatibility checking
* Only Blueprints compatible with your current license are available for use
* Sub-processors within bundles are also checked for license compatibility
* Incompatible Blueprints are clearly marked with warning indicators

#### Preview Capability

* Preview Blueprints before adding them to your project
* View included sub-processors in bundles
* Understand the structure and purpose of each Blueprint

#### Easy Integration

* Add Blueprints to your project with a single click
* Automatically copied to your project's resource library
* Can be used in configurations just like any other processor

### Using Blueprints

#### Accessing the Blueprints Page

1. Navigate to the **Blueprints** page in the Bindplane UI
2. The page displays all available Blueprints in your instance
3. Use the search functionality to find specific Blueprints

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/dmd1YvzqQXsLCtG1SyfP/blueprints-3.png" alt=""><figcaption></figcaption></figure>

#### Previewing a Blueprint

1. Click the **Preview** button on any Blueprint card
2. **View** the Processors contained in the Blueprint

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/G2MKgbi4sgeTOa0CdNIY/blueprints-4.png" alt=""><figcaption></figcaption></figure>

#### Adding a Blueprint to Your Project

1. Click **Add to Project** on the Blueprint card
2. Provide a name for the processor bundle
3. The Blueprint is copied to your project's resource library
4. It can now be used in configurations like any other processor

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/TZDU9g2ZdTlZdS7Veqw6/blueprints-5.png" alt="" width="563"><figcaption></figcaption></figure>

#### Using Blueprints in Configurations

Once added to your project:

1. Navigate to a configuration editor
2. Add a processor to a source or destination
3. Select the Blueprint from your processor list
4. Configure any required parameters
5. The Blueprint will be applied to your telemetry pipeline

<figure><img src="https://content.gitbook.com/content/DBruzp1JKFyzeaBOInfR/blobs/kRWnKhf5XX4BkX9KOkKs/blueprints-6.png" alt="" width="563"><figcaption></figcaption></figure>

### Summary

Blueprints provide a powerful way to standardize and reuse processor configurations across your Bindplane deployment. Whether you're using pre-built Blueprints from the library or creating your own, they help streamline telemetry processing and ensure consistency across your observability pipelines.