Skip to main content

​
Getting Started

logzio 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 Destination Fields

✅ Traces ✅ Metrics ✅ Logs
  • LOGZIO_REGION string : Region. The region of your Logz.io account
    • This field is required
  • LOGZIO_TRACING_TOKEN string : Tracing token. The token you obtained from Logz.io
    • This field is optional
  • LOGZIO_METRICS_TOKEN string : Metrics token. The token you obtained from Logz.io
    • This field is optional
  • LOGZIO_LOGS_TOKEN string : Logs token. The token you obtained from Logz.io
    • This field is optional

​
Adding Destination to Odigos

There are two primary methods for configuring destinations in Odigos:
Using the UI
1
Use the Odigos CLI to access the UI
odigos ui
2
Click on Add Destination, select Logz.io and follow the on-screen instructions
Using Kubernetes manifests
1
Save the YAML below to a file (e.g. logzio.yaml)
apiVersion: odigos.io/v1alpha1
kind: Destination
metadata:
  name: logzio-example
  namespace: odigos-system
spec:
  data:
    LOGZIO_REGION: '<Region (options: [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
2
Apply the YAML using kubectl
kubectl apply -f logzio.yaml