-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add config specs #7318
Merged
Merged
Add config specs #7318
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||
---|---|---|---|---|
@@ -0,0 +1,61 @@ | ||||
name: Cassandra Nodetool | ||||
files: | ||||
- name: cassandra_nodetool.yaml | ||||
options: | ||||
- template: init_config | ||||
options: | ||||
- name: nodetool | ||||
description: | | ||||
The command or path to nodetool (for example, /usr/bin/nodetool or docker exec container nodetool) | ||||
can be overwritten on an instance. | ||||
Note: Agent v6.11+ on Windows runs as an unprivileged user (`ddagentuser`). That user needs to be granted | ||||
access to the nodetool installation directory for the check to work. | ||||
The nodetool installation also sets some environment variables (for example, `CASSANDRA_HOME` | ||||
and `DSCINSTALLDIR`), but sets them as variables only for the user doing the nodetool installation. | ||||
You should set those environment variables as system-wide variables. | ||||
required: true | ||||
value: | ||||
type: string | ||||
example: nodetool | ||||
- template: init_config/default | ||||
- template: instances | ||||
options: | ||||
- name: keyspaces | ||||
description: | | ||||
The list of keyspaces to monitor. | ||||
An empty list results in no metrics being sent. | ||||
required: true | ||||
value: | ||||
type: array | ||||
items: | ||||
type: string | ||||
- name: host | ||||
description: Host that the Datadog Cassandra Nodetool check connects to. | ||||
value: | ||||
type: string | ||||
example: localhost | ||||
- name: port | ||||
description: The port JMX listens to for connections. | ||||
value: | ||||
type: integer | ||||
example: 7199 | ||||
- name: username | ||||
description: | | ||||
Username from the credentials needed to connect to the host. These are the credentials for the JMX server. | ||||
For the check to work, this user must have a read/write access so that the Datadog Cassandra Nodetool | ||||
check can execute the `status` command | ||||
value: | ||||
type: string | ||||
- name: password | ||||
description: | | ||||
Password from the credentials needed to connect to the host. These are the credentials for the JMX server. | ||||
For the check to work, this user must have a read/write access so that the Datadog Cassandra Nodetool | ||||
check can execute the `status` command | ||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||
value: | ||||
type: string | ||||
- name: ssl | ||||
description: Whether to use the --ssl parameter with nodetool to initiate a connection over SSL to the JMX server. | ||||
value: | ||||
type: boolean | ||||
example: false | ||||
- template: instances/default |
75 changes: 52 additions & 23 deletions
75
cassandra_nodetool/datadog_checks/cassandra_nodetool/data/conf.yaml.example
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,60 +1,89 @@ | ||
## All options defined here are available to all instances. | ||
# | ||
init_config: | ||
|
||
## @param nodetool - string - required | ||
## command or path to nodetool (e.g. /usr/bin/nodetool or docker exec container nodetool) | ||
## can be overwritten on an instance | ||
## Note: Agent v6.11+ on Windows runs as an unprivileged user (`ddagentuser`). That user needs to be granted | ||
## access to the nodetool installation directory for the check to work. | ||
## The nodetool installation also sets some environment variables (e.g. `CASSANDRA_HOME` and `DSCINSTALLDIR`), | ||
## but sets them as variables only for the user doing the nodetool installation. Those environment variables should | ||
## be set as system-wide variables. | ||
# | ||
# nodetool: /usr/bin/nodetool | ||
## @param nodetool - string - required | ||
## The command or path to nodetool (for example, /usr/bin/nodetool or docker exec container nodetool) | ||
## can be overwritten on an instance. | ||
## Note: Agent v6.11+ on Windows runs as an unprivileged user (`ddagentuser`). That user needs to be granted | ||
## access to the nodetool installation directory for the check to work. | ||
## The nodetool installation also sets some environment variables (for example, `CASSANDRA_HOME` | ||
## and `DSCINSTALLDIR`), but sets them as variables only for the user doing the nodetool installation. | ||
## You should set those environment variables as system-wide variables. | ||
# | ||
nodetool: nodetool | ||
|
||
## @param service - string - optional | ||
## Attach the tag `service:<SERVICE>` to every metric, event, and service check emitted by this integration. | ||
hithwen marked this conversation as resolved.
Show resolved
Hide resolved
|
||
## | ||
## Additionally, this sets the default `service` for every log source. | ||
# | ||
# service: <SERVICE> | ||
|
||
## Every instance is scheduled independent of the others. | ||
# | ||
instances: | ||
|
||
## @param keyspaces - list of string - required | ||
## @param keyspaces - list of strings - required | ||
## The list of keyspaces to monitor. | ||
## An empty list results in no metrics being sent. | ||
# | ||
- keyspaces: | ||
- <KEYSPACE_1> | ||
- <KEYSPACE_2> | ||
- keyspaces: [] | ||
|
||
## @param host - string - optional | ||
## @param host - string - optional - default: localhost | ||
## Host that the Datadog Cassandra Nodetool check connects to. | ||
# | ||
# host: localhost | ||
|
||
## @param port - integer - optional | ||
## The port JMX is listening to for connections. | ||
## @param port - integer - optional - default: 7199 | ||
## The port JMX listens to for connections. | ||
# | ||
# port: 7199 | ||
|
||
## @param username - string - optional | ||
## Username from the credentials needed to connect to the host. These are the credentials for the JMX server. | ||
## For the check to work, this user must have a read/write access so that the Datadog Cassandra nodetool | ||
## For the check to work, this user must have a read/write access so that the Datadog Cassandra Nodetool | ||
## check can execute the `status` command | ||
# | ||
# username: <USERNAME> | ||
|
||
## @param password - string - optional | ||
## Username from the credentials needed to connect to the host. These are the credentials for the JMX server. | ||
## Password from the credentials needed to connect to the host. These are the credentials for the JMX server. | ||
## For the check to work, this user must have a read/write access so that the Datadog Cassandra Nodetool | ||
## check can execute the `status` command | ||
# | ||
# password: <PASSWORD> | ||
|
||
## @param ssl - boolean - optional - default: false | ||
## Whether or not to use the --ssl parameter to nodetool to initiate a connection over SSL to the JMX server. | ||
## Whether to use the --ssl parameter with nodetool to initiate a connection over SSL to the JMX server. | ||
# | ||
# ssl: false | ||
|
||
## @param tags - list of key:value element - optional | ||
## List of tags to attach to every metric, event and service check emitted by this integration. | ||
## @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: https://docs.datadoghq.com/tagging/ | ||
## 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. | ||
hithwen marked this conversation as resolved.
Show resolved
Hide resolved
|
||
## | ||
## 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: | ||
hithwen marked this conversation as resolved.
Show resolved
Hide resolved
|
||
## https://docs.datadoghq.com/developers/write_agent_check/#collection-interval | ||
# | ||
# min_collection_interval: 15 | ||
|
||
## @param empty_default_hostname - boolean - optional - default: false | ||
hithwen marked this conversation as resolved.
Show resolved
Hide resolved
|
||
## This forces the check to send metrics with no hostname. | ||
hithwen marked this conversation as resolved.
Show resolved
Hide resolved
|
||
## | ||
## This is useful for cluster-level checks. | ||
# | ||
# empty_default_hostname: false |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why removing this?