Logz.io Streaming Output and Integration

George Alpizar
George Alpizar
  • Updated

Overview

The Logz.io output will stream analytics and insights to your Logz.io endpoint.


Review Sample Configuration

The following sample configuration displays an output without the name of the organization-level integration:

- name: logzio
  type: logzio
  endpoint: "https://app-eu.logz.io:8071"
  token: "<add logz.io log shipping token>"
  metric_token: "<add logz.io metric shipping token>"
  custom_tags:
    "app": "starbucks_pos_transaction_manager"
    "region": "us-west-2"
    "File Path": "{{.FileGlobPath}}"
    "K8s PodName": "{{.K8sPodName}}"
    "K8s Namespace": "{{.K8sNamespace}}"
    "K8s ControllerKind": "{{.K8sControllerKind}}"
    "K8s ContainerName": "{{.K8sContainerName}}"
    "K8s ContainerImage": "{{.K8sContainerImage}}"
    "K8s ControllerLogicalName": "{{.K8sControllerLogicalName}}"
    "ECSCluster": "{{.ECSCluster}}"
    "ECSContainerName": "{{.ECSContainerName}}"
    "ECSTaskVersion": "{{.ECSTaskVersion}}"
    "ECSTaskFamily": "{{.ECSTaskFamily}}"
    "DockerContainerName": "{{.DockerContainerName}}"
    "ConfigID": "{{.ConfigID}}"
    "Host": "{{.Host}}"
    "Source": "{{.Source}}"
    "SourceType": "{{.SourceType}}"
    "Tag": "{{.Tag}}"

Review Parameters

Review the following parameters that you can configure in the Edge Delta App.


name

Required

Enter a descriptive name for the output or integration.

For outputs, this name will be used to map this destination to a workflow.

Review the following example:

name: logzio

integration_name

Optional

This parameter refers to the organization-level integration created in the Integrations page. 

If you need to add multiple instances of the same integration into the config, then you can add a custom name to each instance via the name parameter. In this situation, the name should be used to refer to the specific instance of the destination in the workflows.

Review the following example:

integration_name: orgs-logzio

type

Required

Enter logzio.

Review the following example:

type: logzio

endpoint

Required

Enter the Logz.io endpoint. You can use a cloud endpoint or a self-hosted endpoint.

Review the following example:

endpoint: "https://app-eu.logz.io:8071"

token

Optional 

Enter the Logz.io log token.

This parameter is required if you want to support log stream.

Review the following example:

token: "<add logz.io log shipping token>"

metric_token

Optional

Enter the Logz.io metric token.

This parameter is required if you want to support metric stream.

Review the following example:

metric_token: "<add logz.io metric shipping token>"

custom_tags

Optional

This parameter defines key-value pairs that are streamed with every request.

Review the following example: 

custom_tags:
  "app": "starbucks_pos_transaction_manager"
  "region": "us-west-2"
  "File Path": "{{.FileGlobPath}}"
  "K8s PodName": "{{.K8sPodName}}"
  "K8s Namespace": "{{.K8sNamespace}}"
  "K8s ControllerKind": "{{.K8sControllerKind}}"
  "K8s ContainerName": "{{.K8sContainerName}}"
  "K8s ContainerImage": "{{.K8sContainerImage}}"
  "K8s ControllerLogicalName": "{{.K8sControllerLogicalName}}"
  "ECSCluster": "{{.ECSCluster}}"
  "ECSContainerName": "{{.ECSContainerName}}"
  "ECSTaskVersion": "{{.ECSTaskVersion}}"
  "ECSTaskFamily": "{{.ECSTaskFamily}}"
  "DockerContainerName": "{{.DockerContainerName}}"
  "ConfigID": "{{.ConfigID}}"
  "Host": "{{.Host}}"
  "Source": "{{.Source}}"
  "SourceType": "{{.SourceType}}"
"Tag": "{{.Tag}}"

features

Optional 

This parameter defines which data types to stream to the destination.

If you do not provide a value, then all will be set.

To learn more, review the Review Feature Types section in Stream Outputs and Integrations Overview.

Review the following example:

features: log

buffer_ttl

Optional

Enter a length of time to retry failed streaming data.

After this length of time is reached, the failed streaming data will no longer be tried.

Review the following example: 

buffer_ttl: 2h

buffer_path

Optional

Enter a folder path to temporarily store failed streaming data.

The failed streaming data will be retried until the data reaches its destinations or until the Buffer TTL value is reached.

If you enter a path that does not exist, then the agent will create directories, as needed.

Review the following example: 

buffer_path: /var/log/edgedelta/pushbuffer/

buffer_max_bytesize

Optional 

Enter the maximum size of failed streaming data that you want to retry.

If the failed streaming data is larger than this size, then the failed streaming data will not be retried.

Review the following example: 

buffer_max_bytesize: 100MB

 

Share this document