Container Native Monitoring Insights with Elastic on IBM Cloud
By: Chris Rosen
Introduction to container native monitoring
In this blog post, we will discuss how Elastic easily deploys with the IBM Cloud Kubernetes Service (IKS). This provides full visibility of your containerized workloads and operational consistency with container deployments in a multi-cloud architecture. We will deploy a Kubernetes cluster in IBM Cloud and layer in the Elastic to provide container native monitoring.
About IBM Cloud
IBM Cloud (formerly IBM Bluemix) was announced in June 2014, providing users with a variety of compute choices and over 170 IBM and third-party services. IBM Cloud Kubernetes Service combines Docker and Kubernetes to deliver powerful tools, an intuitive user experience, and built-in security and isolation to enable rapid delivery of applications—all while leveraging Cloud Services, including cognitive capabilities from Watson.
Elastic builds software to make data usable in real time and at scale for search, logging, security, and analytics use cases. Founded in 2012, the company develops the open source Elastic Stack (Elasticsearch, Kibana, Beats, and Logstash), commercial features, and Elastic Cloud (a SaaS offering). To date, there have been more than 225 million cumulative downloads. The Elastic community is 100,000 members strong. Thousands of organizations (including Cisco, eBay, Goldman Sachs, NASA, Microsoft, Mayo Clinic, the New York Times, Wikipedia, and Verizon) use Elastic to power mission-critical systems. Backed by Benchmark Capital, Index Ventures, and NEA, with more than $100 million in funding, Elastic has a distributed workforce with more than 800 employees in 30 countries. Learn more at elastic.co.
Setting up a Kubernetes cluster in IBM Cloud
The first step in setting up a Kubernetes cluster in IBM Cloud is to create a IBM Cloud account. After you’ve successfully logged in, the left-hand navigation will take you to Containers.
Select the Kubernetes Cluster icon. We’re going to create a standard cluster below.
To create a standard cluster, set the following parameters:
Machine type: A flavor with pre-defined resources per worker node in your cluster
Number of workers: 1 to n based on capacity requirements (this can be scaled up or down after the cluster is running)
Private and Public VLAN: Choose networks for worker nodes (we’ll create for you if you don’t have any yet)
Hardware: Clusters and worker nodes are always single-tenant and isolated to you, but you can choose the level of isolation to meet your needs (shared workers have multi-tenant hypervisor and hardware whereas dedicated worker nodes are single-tenant down to the hardware level)
See the IBM Cloud documentation for more details on cluster creation. Once you are satisfied with your selections, click on the Create Cluster button.
Once the cluster is created, install the IBM Cloud Kubernetes Service CLI and APIs.
To create a cluster from the command line, use the following command:
bx cs cluster-create –name –location –workers 2 –machine-type u1c.2×4 –hardware shared –public-vlan –private-vlan
Deploying Elastic for container native monitoring
You can get started with Elastic by following a few easy steps.
Now that you have Elasticsearch ready to index, store, search, and analyze your data, learn about monitoring the logs and metrics of your IBM Cloud Kubernetes Service and the applications running in there with this blog and video from Elastic, the creators of Elasticsearch.
Start using container native monitoring
IBM Cloud Kubernetes Service makes it easy to set up a Kubernetes cluster to host your containerized applications. Deploying your apps may be the easy part compared to day two operations, which is where Elastic can provide insights to these workloads. Learn more about Elastic here.
Join us on Slack