Export Telemetry Data to Privacera Cloud (D2P Mode)¶

Introduction¶

This guide describes how to export telemetry data metrics, logs, and traces to Privacera Cloud in D2P mode. By configuring the export settings, you can forward monitoring data to Privacera Cloud for centralized observability and analysis.

Prerequisites¶

Prerequisite	Description
D2P Mode Deployment	This configuration applies to D2P mode deployments.
Privacera Cloud Access	Ensure you have access to Privacera Cloud and configured the necessary variables in the `vars.privacera-cloud.yml` file
Required Variables	Make sure you have configured `PRIVACERA_CLOUD_BASE_URL` and `PRIVACERA_CLOUD_API_KEY` in the `vars.privacera-cloud.yml` file

Process¶

Step 1: Access Privacera Manager Instance¶

SSH into the instance where Privacera Manager is installed.

Step 2: Navigate to Configuration Directory¶

Navigate to the config directory using the following command:

Bash
1	`cd ~/privacera/privacera-manager/config/`

Step 3: Copy Configuration File¶

Copy the vars.privacera-cloud.yml file from the sample-vars folder to the custom-vars folder:

Note

If this file already exists in custom-vars folder, you can skip this step.

Bash
1	`cp sample-vars/vars.privacera-cloud.yml custom-vars/`

Step 4: Edit Configuration File¶

Open the vars.privacera-cloud.yml file for editing:

Bash
1	`vi custom-vars/vars.privacera-cloud.yml`

Required Configuration Variables

Before enabling telemetry export, ensure that the following variables are configured in the vars.privacera-cloud.yml file:

PRIVACERA_CLOUD_BASE_URL - The base URL for Privacera Cloud
PRIVACERA_CLOUD_API_KEY - The API key for authenticating with Privacera Cloud

These variables are required for the export functionality to work properly.

Step 5: Enable Telemetry Export to Privacera Cloud¶

Uncomment the following variables in the file, based on the data you want to export:

Export Metrics to Privacera Cloud¶

By default, metrics are exported to Privacera Cloud. To disable metrics export, uncomment the following variable:

YAML
EXPORT_METRICS_PCLOUD: "false"

Export Logs to Privacera Cloud¶

Uncomment this variable if you want to export logs to Privacera Cloud:

YAML
EXPORT_LOGS_PCLOUD: "true"

Export Traces to Privacera Cloud¶

Uncomment this variable if you want to export traces to Privacera Cloud:

YAML
EXPORT_TRACES_PCLOUD: "true"

Tip

You can enable one or more of these export options based on your requirements. All three can be enabled simultaneously, if needed.

Step 6: Save and Exit¶

Save the file and exit the editor:

Press Esc to ensure you are in command mode.
Type :wq and press Enter to save and exit.

Step 7: Redeploy Monitoring Components¶

Once the configuration is complete, redeploy the monitoring components:

a. Go to privacera-manager directory.

Bash
1	`cd ~/privacera/privacera-manager`

b. Run setup to generate the required files.

Bash
1	`./privacera-manager.sh setup`

c. Install the monitoring components.

Bash
1	`./pm_with_helm.sh install-monitoring`

d. Run install to update the Grafana.

Bash
1	`./pm_with_helm.sh install`

e. Once done, run post-install.

Bash
1	`./privacera-manager.sh post-install`

Verification¶

After redeploying, you can verify that telemetry data is being exported to Privacera Cloud by:

Checking the OTEL Collector logs for successful export messages.
Reviewing the status of the monitoring stack:

Bash
kubectl get pods -n privacera-monitoring

Summary¶

By enabling the export variables in vars.privacera-cloud.yml, you can forward your telemetry data (metrics, logs, and traces) to Privacera Cloud for centralized monitoring and analysis in D2P mode deployments.

Prev Advanced Configuration