Send Kubernetes Data with Telemetry Collector
Telemetry Collector is currently available in all regions except for Japan. If you're located in this region, you can use Logz.io’s integrations hub to send your data.
To start sending your Kubernetes data through the Telemetry Collector, you'll need the following:
- Admin privileges in your Logz.io account
- Outgoing traffic to destination ports
8053and8071allowed
If you're unsure whether traffic is allowed to these ports, continue the process, and Logz.io will notify you if access is restricted.
Navigate to the Integration hub and choose one of the Kubernetes integrations available under the Quick Setup section.
To configure the Telemetry Collector, you must be logged into your main Logz.io account.
Send Kubernetes data
Activate your collector
Choose the platform on which you want to run the Telemetry Collector. You can choose between Helm, Mac, Windows, or Linux.
- Helm users - Connect to the Kubernetes cluster from which you want to send telemetry, copy the Helm Install snippet, replace the placeholders with the relevant values, and run it in your terminal.
- Mac users - Copy the snippet and run it in your terminal.
- Windows users - Copy the snippet and run it in your PowerShell x64 as Administrator (Note that PowerShell x86 and PowerShell ISE are currently not supported).
- Linux users - Copy the snippet and run it in your command line.
Some platforms require additional details, such as admin privileges or passwords, to complete the installation. These details are not sent to or stored by Logz.io.
Run the Telemetry Collector
The Telemetry Collector will create all setters needed for the Helm install command to install Logz.io Helm chart and deploy the chart with the relevant parameters. Once running, the Telemetry Collector will continuously collect the relevant data from your end, and you can view and manage it in Logz.io.
You can review the complete list of parameters and commands Logz.io runs in the background on the Logzio Monitoring GitHub repository.
It might take a while for the Telemetry Collector to get up and running, after which you can view your logs, metrics, or traces and get full observability into your system.
Optional - Configure data sources
You can configure the data sources collected by the Telemetry Collector. To do so, click on Advance settings at the top of the page. You can review and edit the telemetries collected by Logz.io.
Optional - Define your collector
You can edit your collector’s name and description and choose which Logs, Metrics, and Tracing accounts to use. To do so, click on Advance settings at the top of the Activate your collector page, and click Next to reach the Finalize Telemetry Collector page.
If you don't have Logs, Metrics, or Traces accounts, you can review the newly generated accounts.
Click Save changes to continue.
Optional - Configure log level
You can adjust the verbosity of the logs by setting the log level. This allows you to control the amount and type of information logged, which can be useful for debugging or monitoring purposes.
To set the log level:
- Locate the values.yaml file used for your Helm deployment.
- Add or modify the logLevel parameter under the processors section:
The log_level field is assigned based on a regex match in the message field. The configuration below sets different log levels depending on keywords found in the log message:
log_statements:
- context: log
statements:
# set log_level
- set(attributes["log_level"], "INFO")
- set(attributes["log_level"], "DEBUG") where (IsMatch(body, ".*\\b(?i:debug)\\b.*"))
- set(attributes["log_level"], "WARNING") where (IsMatch(body, ".*\\b(?i:warning|warn)\\b.*"))
- set(attributes["log_level"], "ERROR") where (IsMatch(body, ".*(?i:(?:error|fail|failure|exception|panic)).*"))
Setting a higher verbosity level such as DEBUG provides more detailed logs, which can help with troubleshooting. However, keep in mind that higher verbosity increases log volume.
Manage your Telemetry Collector:
To manage a Kubernetes Telemetry Collector, you can use the following commands:
| Description | Command |
|---|---|
| Show Helm Status: | helm status -n monitoring logzio-monitoring |
| Get Pods: | kubectl get pods -n monitoring |
| Show Pod's Logs: | kubectl logs <<POD_NAME>> -n monitoring |
| Show Pod's Info: | kubectl describe pod <<POD_NAME>> -n monitoring |
Replace <<POD_NAME>> with your pod's name.
If you're running your Kubernetes Telemetry Collector from a Windows machine, you can use the following commands to gain access to the Helm chart and Logz.io's logs:
| Description | Command |
|---|---|
| Logz.io Helm: | C:\Users\<<USERNAME>>\AppData\Roaming\LogzioAgent\LogzioKubernetes\logzio_helm.txt |
| Logz.io Telemetry Collector Logs: | C:\Users\<<USERNAME>>\AppData\Roaming\LogzioAgent\logzio_agent.log |
| Install Logz.io Helm: | Invoke-Expression -Command (Get-Content -Path C:\Users\<<USERNAME>>\AppData\Roaming\LogzioAgent\LogzioKubernetes\logzio_helm.txt) |
| Uninstall Logz.io Helm: | helm uninstall -n monitoring logzio-monitoring |
Replace <<USERNAME>> with your Windows user name.
If you have additional questions about managing your Telemetry Collector, contact Logz.io's Support team.
Remove your Telemetry Collector:
You can uninstall your Telemetry Collector from Kubernetes by running the following snippet in the same platform you've used to install it:
helm uninstall -n monitoring logzio-monitoring
- Mac - Run the snippet in your terminal.
- Windows - Run the snippet in your PowerShell x64 as Administrator.
- Linux - Run the snippet in your command line.
This snippet removes the collector from Logz.io and stops sending your data. Of course, you can always create a new collector or use Logz.io's Send your data to ship your data.
If you have additional questions about managing your Telemetry Collector, contact Logz.io's Support team.