honeycombio/kubernetes-manifests

Name: kubernetes-manifests

Owner: Honeycomb

Description: Example deployment manifests for Kubernetes integrations

Created: 2017-08-03 22:48:43.0

Updated: 2018-05-16 17:22:32.0

Pushed: 2018-05-16 17:22:29.0

Homepage: null

Size: 14

Language: null

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

This repository contains example manifests for deploying Honeycomb's Kubernetes integrations.

The Honeycomb Kubernetes agent provides a flexible way to ingest logs from applications running on Kubernetes. Honeycomb can also leverage Heapster and kube-state-metrics to explore your cluster's state and resource use.

To start collecting data, grab your Honeycomb write key from your account page. Then run

ctl create secret generic honeycomb-writekey --from-literal=key=$YOUR_WRITEKEY -n kube-system

to save your write key as a Kubernetes secret.

Next, clone this repository and apply the manifests:

clone https://github.com/honeycombio/kubernetes-manifests
ctl apply -f kubernetes-manifests/logs
ctl apply -f kubernetes-manifests/metrics

After a few seconds, you should see the following datasets in the Honeycomb UI:

• kubernetes-state-metrics: This contains metrics describing the state of Kubernetes objects. For example, to see the number of running replicas per deployment, run the query

• breakdown: deployment

• calculate per group: MIN(kube_deployment_status_replicas)

  tip: Under “graph settings”, toggle “omit missing values” to get smoother graphs.

• kubernetes-resource-metrics: This dataset contains metrics describing system resource use by pods and containers (CPU/memory/IO/etc). For example, to see the containers using the most CPU, run the query

• break down: container_name

• calculate per group: MAX(cpu/usage_rate)

• order: MAX(cpu/usage_rate) desc.

• kubernetes-cluster-events: This dataset contains events describing cluster state changes. It's similar to the output you'd see by running kubectl get events --watch. For example, you might use this dataset to set a trigger on the query

• calculate: COUNT

• filter: kind = Pod, reason = Killing

  to alert you when too many pods are being killed.

• kubernetes-logs: This contains logs from applications running on Kubernetes. Note that by default, the agent only parses logs from Kubernetes system components. You'll want to adjust its configuration to parse logs from your applications! See the agent docs for configuration details.