Overview
Logz.io is a comprehensive observability platform that provides better visibility into applications and systems. The fully managed SaaS solution allows you to collect, parse, and analyze logs, metrics, traces, and security data in one place, using AI and machine learning to help identify and resolve issues, respond faster to incidents, and manage costs effectively. With Logz.io, you can aggregate and visualize your server log data in real-time, making it easier understanding the events happening across your infrastructure easier. Logz.io supports long-term log retention and is built with security in mind, providing features like role-based access control, ensuring that your sensitive log data is properly protected. Follow the steps below to configure shipping data from Control Plane to Logz.io:Step 1 - Generate Token Credentials
Logz.io requires an authorization token in order to process data and logs. You’ll need to store the token as an Opaque Secret and configure external logging.- Log into your Logz.io account and open the Data shipping tokens page.
- Copy the listener URL and the relevant account token you want to use.
- Navigate to
Secrets
and create a new secret. - Name your secret and select
Opaque
from the Secret Type list. - Paste the Logz.io token string into the content text box and click Create.
Step 2 - Configuring Shipping Data to Logz.io
You need to enable logging from your UI Console or CLI.Enable 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. - Select
Logz.io
and fill out the required fields. - Select the Opaque secret created to authenticate to Logz.io. Refer to the generate token credentials section to obtain and configure the necessary credentials.
- Click Save.
The
Listener Host
value is shown on the Manage tokens page.Enable Logging using the CLI
The external logging configuration can be created / updated using the CLI’scpln org patch ORG_NAME -f FILE.yaml
command.
Below is an example of an Org manifest (in YAML). Edit and save the YAML as a file and use it as an input to the CLI’s cpln org patch ORG_NAME -f FILE.yaml
command.
Refer to the generate token credentials section to obtain and configure the necessary credentials.
- Substitute:
ORG_NAME
,OPAQUE_SECRET
, and possibly the listener host.
YAML