Control Plane is a hybrid platform that integrates multiple cloud services, such as AWS, GCP, and Azure, providing a unified and flexible environment for developers to build and manage backend applications and services across various public and private clouds.
Deploy this integration to ship all
Org logs from your Control Plane account to Logz.io.
Before you begin, you'll need:
- Control Plane account
Store the Logz.io secret as an Opaque Secret
- Log in to Control Plane Console UI.
- Navigate to Secrets.
- Create a new secret.
- Give the secret a name.
Opaquefrom the Secret Type list.
<<LOG-SHIPPING-TOKEN>>into the content text box. This is the log shipping token of your Logz.io account.
- Click Create.
Enable Control Plane logging
Using the UI Console
- Open the Control Plane Console UI.
- Click on Org in the left menu.
- Click External Logs in the middle context menu.
Logz.ioand fill out the required fields.
- Select the Opaque secret created to authenticate to Logz.io.
- Click Save.
Using the CLI
- Prepare the YAML manifest:
<<ORG_NAME>> with your organization's name.
<<OPAQUE-SECRET-NAME>> with the name of the opaque secret created in the first step of these instructions.
<<LISTENER-HOST>> with the host for your region. For example,
listener.logz.io if your account is hosted on AWS US East, or
listener-nl.logz.io if hosted on Azure West Europe. The required port depends whether HTTP or HTTPS is used: HTTP = 8070, HTTPS = 8071.
Save the file, for example,
Open your command line interface (CLI) and navigate to the directory where the
logging-config.yamlfile is saved.
Execute the following command, replacing
ORG_NAMEwith your organization's name:
cpln org patch ORG_NAME -f logging-config.yaml
Check Logz.io for your logs
Spin up your Docker containers if you haven't done so already. Give your logs some time to get from your system to ours, and then open Open Search Dashboards.
If you still don't see your logs, see log shipping troubleshooting.