​
Finding Logz.io Region

You can find your account’s region by selecting ⚙️ > Settings > General from the top menu. Your two-letter region code is at the start of the region designation. Another option is to sign in to your Logz.io account and look at the URL in the address bar.

If you see app.logz.io, your account is hosted in the US East (Northern Virginia). All other regions have a two-letter region code. For example, if you see app-eu.logz.io, then your account is in the Europe (Frankfurt) region.

​
Obtaining Tokens

From your account, go to the Manage Tokens > Data shipping tokens tab of your Operations workspace. It can be reached by selecting ⚙️ > Settings > Manage tokens in the ADMIN ZONE section of the side navigation menu.

​
Configuring Logz.io Backend

Create a new logz.io backend with the following configuration:

  • Name: A name for the backend.
  • Region: The region of your Logz.io account.
  • Tracing/Metrics/Logs Token: The token you obtained from Logz.io.

​
Adding a Destination to Odigos

Odigos makes it simple to add and configure destinations, allowing you to select the specific signals [traces/logs/metrics] that you want to send to each destination. There are two primary methods for configuring destinations in Odigos:

  1. Using the UI
    To add a destination via the UI, follow these steps:
    • Use the Odigos CLI to access the UI: Odigos UI
    odigos ui

  • In the left sidebar, navigate to the Destination page.

  • Click Add New Destination

  • Select Logz.io and follow the on-screen instructions.

  1. Using kubernetes manifests

Save the YAML below to a file (e.g., destination.yaml) and apply it using kubectl:

kubectl apply -f destination.yaml

apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: logzio-example
  namespace: odigos-system
spec:
  data:
    LOGZIO_REGION: <Region [listener.logz.io, listener-au.logz.io, listener-ca.logz.io,
      listener-eu.logz.io, listener-nl.logz.io, listener-uk.logz.io, listener-wa.logz.io]>
  destinationName: logzio
  # Uncomment the secretRef below if you are using the optional Secret.
  # secretRef:
  #   name: logzio-secret

  signals:
  - TRACES
  - METRICS
  - LOGS
  type: logzio

---
# The following Secret is optional. Uncomment the entire block if you need to use it.
# apiVersion: v1
# data:
#   LOGZIO_LOGS_TOKEN: <base64 Logs token>
#   LOGZIO_METRICS_TOKEN: <base64 Metrics token>
#   LOGZIO_TRACING_TOKEN: <base64 Tracing token>
# kind: Secret
# metadata:
#   name: logzio-secret
#   namespace: odigos-system
# type: Opaque
LightstepLoki