You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Deploy complex environments and capture meterics
3
3
linkTitle: Deployment
4
-
weight: 3
4
+
weight: 4
5
5
---
6
6
7
7
**Objective:** Learn how to efficiently deploy complex infrastructure components such as Kafka and MongoDB to demonstrate metrics collection with Splunk O11y IM integrations
@@ -12,167 +12,185 @@ weight: 3
12
12
13
13
A prospect uses Kafka and MongoDB in their environment. Since there are integrations for these services, you’d like to demonstrate this to the prospect. What is a quick and efficient way to set up a live environment with these services and have metrics collected?
14
14
15
-
1. Where can I find helm charts?
16
-
a. Google “myservice helm chart”
17
-
b. https://artifacthub.io/ (**Note:** Look for charts from trusted organizations, with high star count and frequent updates)
18
-
2. Review Apache Kafka packaged by Bitnami. We will deploy the helm chart with these options enabled:
19
-
a. `replicaCount=3`
20
-
b. `metrics.jmx.enabled=true`
21
-
c. `metrics.kafka.enabled=true`
22
-
d. `deleteTopicEnable=true`
23
-
3. Review MongoDB(R) packaged by Bitnami. We will deploy the helm chart with these options enabled:
5. Use information for each Helm chart and Splunk O11y Data Setup to generate values.yaml for capturing metrics from Kafka and MongoDB. **Note:** values.yaml for the different services will be passed to the Splunk Helm Chart at installation time. These will configure the OTEL collector to capture metrics from these services.
15
+
### 1. Where can I find helm charts?
16
+
17
+
- Google “myservice helm chart”
18
+
-`https://artifacthub.io/` (**Note:** Look for charts from trusted organizations, with high star count and frequent updates)
19
+
20
+
### 2. Review Apache Kafka packaged by Bitnami
21
+
22
+
We will deploy the helm chart with these options enabled:
23
+
24
+
-`replicaCount=3`
25
+
-`metrics.jmx.enabled=true`
26
+
-`metrics.kafka.enabled=true`
27
+
-`deleteTopicEnable=true`
28
+
29
+
### 3. Review MongoDB(R) packaged by Bitnami
30
+
31
+
We will deploy the helm chart with these options enabled:
Use information for each Helm chart and Splunk O11y Data Setup to generate values.yaml for capturing metrics from Kafka and MongoDB.
69
+
70
+
{{% alert title="Note" color="info" %}}
71
+
`values.yaml` for the different services will be passed to the Splunk Helm Chart at installation time. These will configure the OTEL collector to capture metrics from these services.
72
+
{{% /alert %}}
59
73
60
74
- References:
61
-
a. Apache Kafka packaged by Bitnami
62
-
b. Configure application receivers for databases » Apache Kafka
63
-
c. Kafkametricsreceiver
75
+
- Apache Kafka packaged by Bitnami
76
+
- Configure application receivers for databases » Apache Kafka
77
+
- Kafkametricsreceiver
64
78
65
-
- Example kafka.values.yaml:
79
+
#### 4.1 Example kafka.values.yaml
66
80
67
-
``` yaml
68
-
otelAgent:
81
+
```yaml
82
+
otelAgent:
83
+
config:
84
+
receivers:
85
+
receiver_creator:
86
+
receivers:
87
+
smartagent/kafka:
88
+
rule: type == "pod" && name matches "kafka"
89
+
config:
90
+
#endpoint: '`endpoint`:5555'
91
+
port: 5555
92
+
type: collectd/kafka
93
+
clusterName: sl-kafka
94
+
otelK8sClusterReceiver:
95
+
k8sEventsEnabled: true
96
+
config:
97
+
receivers:
98
+
kafkametrics:
99
+
brokers: kafka:9092
100
+
protocol_version: 2.0.0
101
+
scrapers:
102
+
- brokers
103
+
- topics
104
+
- consumers
105
+
service:
106
+
pipelines:
107
+
metrics:
108
+
receivers:
109
+
#- prometheus
110
+
- k8s_cluster
111
+
- kafkametrics
112
+
```
113
+
114
+
#### 4.2 Example mongodb.values.yaml
115
+
116
+
```yaml
117
+
otelAgent:
69
118
config:
70
119
receivers:
71
120
receiver_creator:
72
121
receivers:
73
-
smartagent/kafka:
74
-
rule: type == "pod"&& name matches "kafka"
122
+
smartagent/mongodb:
123
+
rule: type == "pod" && name matches "mongo"
75
124
config:
76
-
#endpoint: '`endpoint`:5555'
77
-
port: 5555
78
-
type: collectd/kafka
79
-
clusterName: sl-kafka
80
-
otelK8sClusterReceiver:
81
-
k8sEventsEnabled: true
125
+
type: collectd/mongodb
126
+
host: mongodb.default.svc.cluster.local
127
+
port: 27017
128
+
databases: ["admin", "O11y", "local", "config"]
129
+
sendCollectionMetrics: true
130
+
sendCollectionTopMetrics: true
131
+
```
132
+
133
+
#### 4.3 Example zookeeper.values.yaml
134
+
135
+
```yaml
136
+
otelAgent:
82
137
config:
83
138
receivers:
84
-
kafkametrics:
85
-
brokers: kafka:9092
86
-
protocol_version: 2.0.0
87
-
scrapers:
88
-
- brokers
89
-
- topics
90
-
- consumers
91
-
service:
92
-
pipelines:
93
-
metrics:
139
+
receiver_creator:
94
140
receivers:
95
-
#- prometheus
96
-
- k8s_cluster
97
-
- kafkametrics
98
-
```
141
+
smartagent/zookeeper:
142
+
rule: type == "pod" && name matches "kafka-zookeeper"
143
+
config:
144
+
type: collectd/zookeeper
145
+
host: kafka-zookeeper
146
+
port: 2181
147
+
```
99
148
100
-
- Example mongodb.values.yaml:
149
+
### 5. Install the Splunk OTEL helm chart
101
150
102
-
``` yaml
103
-
otelAgent:
104
-
config:
105
-
receivers:
106
-
receiver_creator:
107
-
receivers:
108
-
smartagent/mongodb:
109
-
rule: type == "pod"&& name matches "mongo"
110
-
config:
111
-
type: collectd/mongodb
112
-
host: mongodb.default.svc.cluster.local
113
-
port: 27017
114
-
databases: ["admin", "O11y", "local", "config"]
115
-
sendCollectionMetrics: true
116
-
sendCollectionTopMetrics: true
117
-
```
118
-
119
-
- Example zookeeper.values.yaml:
120
-
121
-
``` yaml
122
-
otelAgent:
123
-
config:
124
-
receivers:
125
-
receiver_creator:
126
-
receivers:
127
-
smartagent/zookeeper:
128
-
rule: type == "pod"&& name matches "kafka-zookeeper"
8. Verify that out of the box dashboards forKafka, MongoDB and Zookeeper are populatedin the Infrastructure Monitor landing page. Drill down into each component to view granular details for each service.
Verify that out of the box dashboards for Kafka, MongoDB and Zookeeper are populated in the Infrastructure Monitor landing page. Drill down into each component to view granular details for each service.
0 commit comments