How to Get Started with Logz.io

After creating a Logz.io account, the first step is to send telemetry data to Logz.io. For those running workloads on Kubernetes, this is a fully automated process described in the steps below. Otherwise, see here for individual Logz.io integrations.

• Deploy the agent: Go into the Logz.io app and deploy Telemetry Collector by running an auto-generated script on your cluster.
• Select the relevant services: Click on Easy Connect, which automatically discovers every service running on your cluster, while providing the option to collect logs, metrics, and or traces from each one.
• Instrument with a click: Automatically instrument your applications to expose trace data. There’s no need to manually change your code—just click a button.

Once your data is in Logz.io, segregate it into separate Logz.io Sub Accounts and assign user permissions to each account – all from a single location. This ensures every team only accesses the data relevant to them to drive autonomy and compliance.

Easily monitor data volumes across teams to find opportunities for cost reduction. Set caps to prevent bursty data from running up your bill.

Learn more about configuring and managing Logz.io Accounts here.

With Logz.io, you don’t have to set up dashboards; we do it for you. Using our Service Overview and Kubernetes 360 features, you get an out-of-the-box overview of your application and infrastructure health and performance.

• Service Overview provides immediate insights into the current state of microservices performance – an ideal place to begin an incident investigation.
• For infrastructure observability, Kubernetes 360 unifies the most critical telemetry data from Kubernetes-based infrastructure in a single view – making it easy to spot production issues across your clusters.
• Build custom monitoring dashboards to identify trends within logs and metrics and to slice and dice your data.