Skip to content
This repository was archived by the owner on Feb 22, 2022. It is now read-only.

Next agent release (ciprod01092019) #11167

Merged
merged 1 commit into from
Feb 12, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion incubator/azuremonitor-containers/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ apiVersion: v1
appVersion: 2.0.0-3
description: Helm chart for deploying Azure Monitor container monitoring agent in Kubernetes
name: azuremonitor-containers
version: 0.4.0
version: 0.5.0
keywords:
- monitoring
- azuremonitor
Expand Down
8 changes: 4 additions & 4 deletions incubator/azuremonitor-containers/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ This article describes how to set up and use [Azure Monitor - Containers](https:

2. [Add the 'AzureMonitor-Containers' Solution to your Log Analytics workspace.](http://aka.ms/coinhelmdoc)

3. [For ACS-engine K8S cluster, add Log Analytics workspace tag to cluster resources, to be able to use Azure Container monitoring User experience (aka.ms/azmon-containers)](http://aka.ms/coin-acs-tag-doc)
3. [For AKS-Engine or ACS-Engine K8S cluster, add required tags on cluster resources, to be able to use Azure Container monitoring User experience (aka.ms/azmon-containers)](http://aka.ms/coin-acs-tag-doc)

---

Expand Down Expand Up @@ -58,7 +58,7 @@ The following table lists the configurable parameters of the MSOMS chart and the
| `omsagent.secret.wsid` | Azure Log analytics workspace id | Does not have a default value, needs to be provided |
| `omsagent.secret.key` | Azure Log analytics workspace key | Does not have a default value, needs to be provided |
| `omsagent.domain` | Azure Log analytics cloud domain (public / govt) | opinsights.azure.com (Public cloud as default), opinsights.azure.us (Govt Cloud) |
| `omsagent.env.clusterName` | Name of your cluster | Does not have a default value, needs to be provided. If ACS-engine cluster, it is recommended to provide either one of the below as cluster name, to be able to use Azure Container monitoring User experience (aka.ms/azmon-containers) <br/> <br/> - Azure Resource group resource ID of ACS-Engine cluster <br/> - Provide a friendly name here and ensure this name is used to 'tag' the cluster master node(s) - see step-3 in pre-requisites above |
| `omsagent.env.clusterName` | Name of your cluster | Does not have a default value, needs to be provided. If AKS-Engine or ACS-Engine K8S cluster, it is recommended to provide either one of the below as cluster name, to be able to use Azure Container monitoring User experience (aka.ms/azmon-containers) <br/> <br/> - Azure Resource group resource ID of ACS-Engine cluster <br/> - Provide a friendly name here and ensure this name is used to 'tag' the cluster master node(s) - see step-3 in pre-requisites above |
|`omsagent.env.doNotCollectKubeSystemLogs`| Disable collecting logs from containers in 'kube-system' namespace | true|
| `omsagent.rbac` | rbac enabled/disabled | true (i.e enabled) |

Expand All @@ -70,7 +70,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
```bash

$ helm install --name myrelease-1 \
--set omsagent.secret.wsid=<your_workspace_id>,omsagent.secret.key=<your_workspace_key>,omsagent.env.clusterName=<my_Acs-engine_k8s_cluster_RG_ResourceID> incubator/azuremonitor-containers
--set omsagent.secret.wsid=<your_workspace_id>,omsagent.secret.key=<your_workspace_key>,omsagent.env.clusterName=<my_AKS-Engine_k8s_cluster_RG_ResourceID> incubator/azuremonitor-containers
```

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
Expand All @@ -83,4 +83,4 @@ $ helm install --name myrelease-1 -f values.yaml incubator/azuremonitor-containe

After you successfully deploy the chart, you will be able to see your data in the [azure portal](aka.ms/azmon-containers)

If you need help with this chart, please reach us out thru [this](mailto:askcoin@microsoft.com) email.
If you need help with this chart, please reach us out through [this](mailto:askcoin@microsoft.com) email.
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,8 @@ spec:
value: {{ .Values.omsagent.env.clusterName | quote }}
- name: DISABLE_KUBE_SYSTEM_LOG_COLLECTION
value: {{ .Values.omsagent.env.doNotCollectKubeSystemLogs | quote }}
- name: CONTROLLER_TYPE
value: "DaemonSet"
- name: NODE_IP
valueFrom:
fieldRef:
Expand All @@ -44,7 +46,7 @@ spec:
- containerPort: 25224
protocol: UDP
volumeMounts:
- mountPath: /var/run/docker.sock
- mountPath: /var/run/host
name: docker-sock
- mountPath: /var/log
name: host-log
Expand Down Expand Up @@ -72,7 +74,7 @@ spec:
volumes:
- name: docker-sock
hostPath:
path: /var/run/docker.sock
path: /var/run
- name: container-hostname
hostPath:
path: /etc/hostname
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,8 @@ spec:
value: {{ .Values.omsagent.env.clusterName | quote }}
- name: DISABLE_KUBE_SYSTEM_LOG_COLLECTION
value: {{ .Values.omsagent.env.doNotCollectKubeSystemLogs | quote }}
- name: CONTROLLER_TYPE
value: "ReplicaSet"
- name: NODE_IP
valueFrom:
fieldRef:
Expand All @@ -48,7 +50,7 @@ spec:
- containerPort: 25224
protocol: UDP
volumeMounts:
- mountPath: /var/run/docker.sock
- mountPath: /var/run/host
name: docker-sock
- mountPath: /var/log
name: host-log
Expand All @@ -73,7 +75,7 @@ spec:
volumes:
- name: docker-sock
hostPath:
path: /var/run/docker.sock
path: /var/run
- name: container-hostname
hostPath:
path: /etc/hostname
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,54 +5,54 @@ data:
kube.conf: |
# Fluentd config file for OMS Docker - cluster components (kubeAPI)

#Kubernetes pod inventory
<source>
#Kubernetes pod inventory
<source>
type kubepodinventory
tag oms.containerinsights.KubePodInventory
run_interval 60s
log_level debug
</source>
</source>

#Kubernetes events
<source>
#Kubernetes events
<source>
type kubeevents
tag oms.api.KubeEvents.CollectionTime
tag oms.containerinsights.KubeEvents
run_interval 60s
log_level debug
</source>
</source>

#Kubernetes logs
<source>
#Kubernetes logs
<source>
type kubelogs
tag oms.api.KubeLogs
run_interval 60s
</source>
</source>

#Kubernetes services
<source>
#Kubernetes services
<source>
type kubeservices
tag oms.api.KubeServices.CollectionTime
tag oms.containerinsights.KubeServices
run_interval 60s
log_level debug
</source>
</source>

#Kubernetes Nodes
<source>
#Kubernetes Nodes
<source>
type kubenodeinventory
tag oms.containerinsights.KubeNodeInventory
run_interval 60s
log_level debug
</source>
</source>

#Kubernetes perf
<source>
#Kubernetes perf
<source>
type kubeperf
tag oms.api.KubePerf
run_interval 60s
log_level debug
</source>
</source>

<match oms.containerinsights.KubePodInventory**>
<match oms.containerinsights.KubePodInventory**>
type out_oms
log_level debug
num_threads 5
Expand All @@ -65,23 +65,24 @@ data:
retry_limit 10
retry_wait 30s
max_retry_wait 9m
</match>
</match>

<match oms.api.KubeEvents**>
type out_oms_api
<match oms.containerinsights.KubeEvents**>
type out_oms
log_level debug
num_threads 5
buffer_chunk_limit 5m
buffer_type file
buffer_path %STATE_DIR_WS%/out_oms_api_kubeevents*.buffer
buffer_path %STATE_DIR_WS%/out_oms_kubeevents*.buffer
buffer_queue_limit 10
buffer_queue_full_action drop_oldest_chunk
flush_interval 20s
retry_limit 10
retry_wait 30s
</match>
max_retry_wait 9m
</match>

<match oms.api.KubeLogs**>
<match oms.api.KubeLogs**>
type out_oms_api
log_level debug
buffer_chunk_limit 10m
Expand All @@ -91,10 +92,10 @@ data:
flush_interval 20s
retry_limit 10
retry_wait 30s
</match>
</match>

<match oms.api.KubeServices**>
type out_oms_api
<match oms.containerinsights.KubeServices**>
type out_oms
log_level debug
num_threads 5
buffer_chunk_limit 20m
Expand All @@ -106,9 +107,9 @@ data:
retry_limit 10
retry_wait 30s
max_retry_wait 9m
</match>
</match>

<match oms.containerinsights.KubeNodeInventory**>
<match oms.containerinsights.KubeNodeInventory**>
type out_oms
log_level debug
num_threads 5
Expand All @@ -121,9 +122,22 @@ data:
retry_limit 10
retry_wait 30s
max_retry_wait 9m
</match>
</match>

<match oms.api.ContainerNodeInventory**>
type out_oms_api
log_level debug
buffer_chunk_limit 20m
buffer_type file
buffer_path %STATE_DIR_WS%/out_oms_containernodeinventory*.buffer
buffer_queue_limit 20
flush_interval 20s
retry_limit 10
retry_wait 15s
max_retry_wait 9m
</match>

<match oms.api.KubePerf**>
<match oms.api.KubePerf**>
type out_oms
log_level debug
num_threads 5
Expand All @@ -136,7 +150,7 @@ data:
retry_limit 10
retry_wait 30s
max_retry_wait 9m
</match>
</match>
metadata:
name: omsagent-rs-config
namespace: kube-system
Expand Down
6 changes: 3 additions & 3 deletions incubator/azuremonitor-containers/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,10 @@
## ref: https://github.com/Microsoft/OMS-docker/tree/ci_feature_prod
omsagent:
image:
tag: "ciprod11292018"
tag: "ciprod01092019"
pullPolicy: IfNotPresent
dockerProviderVersion: "3.0.0-2"
agentVersion: "1.6.0-163"
dockerProviderVersion: "3.0.0-3"
agentVersion: "1.8.1.256"
## To get your workspace id and key do the following
## You can create a Azure Loganalytics workspace from portal.azure.com and get its ID & PRIMARY KEY from 'Advanced Settings' tab in the Ux.

Expand Down