-
Notifications
You must be signed in to change notification settings - Fork 733
/
conf.yaml.example
222 lines (193 loc) · 8.11 KB
/
conf.yaml.example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
## Every instance is scheduled independently of the others.
#
instances:
## @param host - string - required
## HBase Master host to connect to.
#
- host: localhost
## @param port - integer - required
## JMX port to connect to.
#
port: 10101
## @param user - string - optional
## User to use when connecting to JMX.
#
# user: <USER>
## @param password - string - optional
## Password to use when connecting to JMX.
#
# password: <PASSWORD>
## @param process_name_regex - string - optional
## Instead of using a host and port, the Agent can connect using the attach API.
## This requires the JDK to be installed and the path to tools.jar to be set below.
## Note: It needs to be set when process_name_regex parameter is set
## e.g. .*process_name.*
##
## Note: tools.jar was removed in Java 9: https://openjdk.java.net/jeps/220.
## This option is supported in Java 8 and below.
#
# process_name_regex: <PROCESS_NAME_REGEX>
## @param tools_jar_path - string - optional
## The tools.jar path to be used with the `process_name_regex` parameter,
## for example: /usr/lib/jvm/java-7-openjdk-amd64/lib/tools.jar
##
## Note: tools.jar was removed in Java 9: https://openjdk.java.net/jeps/220.
## This option is supported in Java 8 and below.
#
# tools_jar_path: <TOOLS_JAR_PATH>
## @param name - string - optional
## Set the instance name to be used as the `instance` tag.
#
# name: <NAME>
## @param java_bin_path - string - optional
## `java_bin_path` should be set if the Agent cannot find your java executable.
#
# java_bin_path: <JAVA_BIN_PATH>
## @param java_options - string - optional
## A list of Java JVM options, for example: "-Xmx200m -Xms50m".
#
# java_options: <JAVA_OPTIONS>
## @param trust_store_path - string - optional
## The path to your trusted store.
## `trust_store_path` should be set if SSL is enabled.
#
# trust_store_path: <TRUST_STORE_PATH>
## @param trust_store_password - string - optional
## The password for your TrustStore.jks file.
## `trust_store_password` should be set if SSL is enabled.
#
# trust_store_password: <TRUST_STORE_PASSWORD>
## @param key_store_path - string - optional
## The path to your key store.
## `key_store_path` should be set if client authentication is enabled on the target JVM.
#
# key_store_path: <KEY_STORE_PATH>
## @param key_store_password - string - optional
## The password to your key store.
## `key_store_password` should be set if client authentication is enabled on the target JVM.
#
# key_store_password: <KEY_STORE_PASSWORD>
## @param rmi_registry_ssl - boolean - optional - default: false
## Whether or not the Agent should connect to the RMI registry using SSL.
#
# rmi_registry_ssl: false
## @param rmi_connection_timeout - number - optional - default: 20000
## The connection timeout, in milliseconds, when connecting to a remote JVM.
#
# rmi_connection_timeout: 20000
## @param rmi_client_timeout - number - optional - default: 15000
## The timeout to consider a remote connection, already successfully established, as lost.
## If a connected remote JVM does not reply after `rmi_client_timeout` milliseconds jmxfetch
## will give up on that connection and retry.
#
# rmi_client_timeout: 15000
## @param collect_default_jvm_metrics - boolean - optional - default: true
## Configures the collection of default JVM metrics.
#
# collect_default_jvm_metrics: true
## @param tags - list of strings - optional
## A list of tags to attach to every metric and service check emitted by this instance.
##
## Learn more about tagging at https://docs.datadoghq.com/tagging
#
# tags:
# - <KEY_1>:<VALUE_1>
# - <KEY_2>:<VALUE_2>
## @param service - string - optional
## Attach the tag `service:<SERVICE>` to every metric, event, and service check emitted by this integration.
##
## Overrides any `service` defined in the `init_config` section.
#
# service: <SERVICE>
## @param min_collection_interval - number - optional - default: 15
## This changes the collection interval of the check. For more information, see:
## https://docs.datadoghq.com/developers/write_agent_check/#collection-interval
#
# min_collection_interval: 15
## @param empty_default_hostname - boolean - optional - default: false
## This forces the check to send metrics with no hostname.
##
## This is useful for cluster-level checks.
#
# empty_default_hostname: false
## All options defined here are available to all instances.
#
init_config:
## @param is_jmx - boolean - required
## Whether or not this file is a configuration for a JMX integration.
#
is_jmx: true
## @param collect_default_metrics - boolean - optional - default: false
## Whether or not the check should collect all default metrics.
#
collect_default_metrics: true
## @param new_gc_metrics - boolean - optional - default: false
## Set to true to use better metric names for garbage collection metrics.
## jvm.gc.cms.count => jvm.gc.minor_collection_count
## jvm.gc.major_collection_count
## jvm.gc.parnew.time => jvm.gc.minor_collection_time
## jvm.gc.major_collection_time
## The default value is false to ensure backward compatibility.
#
new_gc_metrics: true
## @param service_check_prefix - string - optional
## Custom service check prefix. e.g. `my_prefix` to get a service check called `my_prefix.can_connect`.
## If not set, the default service check used is the integration name.
#
# service_check_prefix: <SERVICE_CHECK_PREFIX>
## @param conf - list of mappings - optional
## The list of metrics to be collected by the integration
## Read http://docs.datadoghq.com/integrations/java/ to learn how to customize it
## The default metrics to be collected are kept in metrics.yaml, but you can still
## add your own metrics here.
#
# conf:
# - include:
# bean: <BEAN_NAME>
# attribute:
# MyAttribute:
# alias: my.metric.name
# metric_type: gauge
## @param service - string - optional
## Attach the tag `service:<SERVICE>` to every metric, event, and service check emitted by this integration.
##
## Additionally, this sets the default `service` for every log source.
#
# service: <SERVICE>
## Log Section
##
## type - required - Type of log input source (tcp / udp / file / windows_event).
## port / path / channel_path - required - Set port if type is tcp or udp.
## Set path if type is file.
## Set channel_path if type is windows_event.
## source - required - Attribute that defines which integration sent the logs.
## encoding - optional - For file specifies the file encoding. Default is utf-8. Other
## possible values are utf-16-le and utf-16-be.
## service - optional - The name of the service that generates the log.
## Overrides any `service` defined in the `init_config` section.
## tags - optional - Add tags to the collected logs.
##
## Discover Datadog log collection: https://docs.datadoghq.com/logs/log_collection/
#
# logs:
# - type: file
# path: /var/log/hbase/hbase-hbase-master-*.log
# source: hbase
# log_processing_rules:
# - type: multi_line
# name: new_log_start_with_date
# pattern: \d{4}\-\d{2}\-\d{2} \d{2}:\d{2}:\d{2},\d{3}
# - type: file
# path: /var/log/hbase/hbase-hbase-rest-*.log
# source: hbase
# log_processing_rules:
# - type: multi_line
# name: new_log_start_with_date
# pattern: \d{4}\-\d{2}\-\d{2} \d{2}:\d{2}:\d{2},\d{3}
# - type: file
# path: /var/log/hbase/hbase-hbase-thrift-*.log
# source: hbase
# log_processing_rules:
# - type: multi_line
# name: new_log_start_with_date
# pattern: \d{4}\-\d{2}\-\d{2} \d{2}:\d{2}:\d{2},\d{3}