What are the settings used in the installation of a new Cassandra agent? (4227164)

DB Connection

• Hostname, port, username, and password - These are client connection details for a regular database connection, such as for connecting with the cqlsh shell.
• Collection periods - The frequency with which to retrieve data from the database and submit to the FMS.

Aliases

• Host Aliases – The host alias list is a mapping from uniquely identifying Host IDs (UUID strings) to hostname aliases. This enables overriding the hostname as discovered by the agent from the cluster in case this is different from the external hostname used to connect directly to the node. In particular, it enables linking the Cassandra hosts to the Hosts dashboard. The Foglight operator can either let the agent run for a few periods until the Host IDs are collected, then update the agent properties with the appropriate mapping read from the Nodes Table on the Cassandra Clusters dashboard, or can query individual database servers from the cqlsh shell to determine their Host IDs ahead of time: SELECT host_id FROM system.local WHERE key='local'; See JMX Connections below for a potentially more straight-forward way to set up host aliasing that can be used in some situations.

JMX Connections

• Default settings - Because it is common and simplest to configure JMX across the cluster with the same user/password combination and listening at the same port, we provide default fields for these so that in such a case the Node Connections list can be simply a list of addresses.
• Node Connections - A list of Cassandra nodes, from a single cluster, that have remote JMX enabled. If the port or JMX user varies with the host, these can be entered individually here. There is also a checkbox option "Use as Host Alias?". If checked, the agent will use the value in the Hostname field as an alias for this node, regardless of how else the hostname may turn up, for example in system tables. Since usually the Foglight operator will create an entry in this list to collect JMX data from every node in the cluster, if the hostname entered for it here is the same as will be used for host monitoring, which is likely, this provides a simpler way to stabilize the hostname than does the Host Alias list utilizing UUID Host IDs.