Outcold Solutions LLC

Monitoring Docker, OpenShift and Kubernetes - Version 5.10 - Security dashboards, multi-cluster monitoring

June 18, 2019

Minor update 5.10 is focused on the usability improvements for the multi-cluster monitoring and security monitoring use-cases.

Security and audit dashboards

With version 5.10 we improved existing security and audit monitoring and introduced new set of dashboards grouped under Security tab.

If you have Security use-cases that we haven't covered yet, feel free to send us a feature request at contact@outcoldsolutions.com.

Access dashboard

Review ssh sessions, super user sessions, exec sessions on your pods and forbidden requests to API server.

Security access

Audit (users and projects)

Additionally to the Audit dashboard, we introduced new dashboard focused on the access to the API server from the users (excluding system accounts). Now you can easily find who worked on the specific project in the last 72 hours, list of actions they executed, and the number of requests they have made.

Audit (users and projects)

Network (traffic)

Monitor the network traffic per your hosts and namespaces/projects

Network (traffic)

Network (connections)

Review the connections from your nodes and namespaces, track cross-namespace connections.

Network (connections)

Objects (pods)

This dashboard is based on the streaming of Pods objects from API server. Now you can review all pods that are running on the host network, pods age (if you have a policy how often the pods need to be updated), review image pull policy and image versions, review all pods that mount host paths, and pods that change their security context.

Objects (pods)

Improved Multi-cluster monitoring

With the previous releases, we suggested to use node labels (or docker engine labels) for identifying the cluster names. Although an easy to use solution, it's not always available in cases when you don't have control over your cluster.

We have introduced custom fields with earlier versions. Custom fields can be attached to any data, that collectord forwards to Splunk. Now we use custom fields to help you identify the clusters in our applications. For backward compatibility we extract cluster name from node labels cluster as well. If you have different node label that identifies your clusters, you will have to update calc fields kubernetes_cluster_eval, openshift_cluster_eval or docker_cluster_eval accordingly. Or you can just switch to the custom fields as described in our installation instructions.

In case of OpenShift just update the ConfigMap (make sure to restart pods after update)

fields.openshift_cluster = development

Most dashboards in application have filter Cluster, that can help you filter the data from specific cluster.

Cluster filter

Dashboard: Clusters (Allocations and usage)

For multi-cluster setup we also included a dashboard that can help you to review allocations and usage for the clusters.

Cluster (Allocations and usage)

Improved support for custom sourcetypes

You can override sourcetypes for the container logs with the annotations collectord.io/logs-type=.... Before release 5.10 you would need to update the macro macro_openshift_logs (in case of OpenShift) to be able to see these logs in our application. Starting from version 5.10 we will identify logs by source /openshift/logs/..., /kubernetes/logs/... and /docker/logs/..., so now you can easily change the sourcetype without worrying about updating macros.

Base macro for configuring indexes

With version 5.10 we introduced base macro, that can help you configure indexes by modifing only base macros macro_docker_base, macro_openshift_base or macro_kubernetes_base.

Improved support for OpenShift 4.x

We've updated our configuration page with the instructions on how to install Monitoring OpenShift for OpenShift 4.x following public release.

For the OpenShift 4.x we also provide RHEL8 certified images with the prefix -ubi8, build from base images -ubi8-minimal. You can find configuration for OpenShift 4.x that refers -ubi8 images.

Support for volatile journald storage

With 5.10 we can automatically forward logs from the journald volatile storage. Please refer to our updated configurations. We include a mount for /run/log and allow you to configure multiple paths for input.journald.

You can find more information about other minor updates by following links below.

Release notes

Upgrade instructions

Installation instructions

docker, kubernetes, openshift, splunk

About Outcold Solutions

Outcold Solutions provides solutions for monitoring Kubernetes, OpenShift and Docker clusters in Splunk Enterprise and Splunk Cloud. We offer certified Splunk applications, which give you insights across all containers environments. We are helping businesses reduce complexity related to logging and monitoring by providing easy-to-use and deploy solutions for Linux and Windows containers. We deliver applications, which help developers monitor their applications and operators to keep their clusters healthy. With the power of Splunk Enterprise and Splunk Cloud, we offer one solution to help you keep all the metrics and logs in one place, allowing you to quickly address complex questions on container performance.