# Aerospike # Introducción **Ver**. 28-12-2022 Plugin con el que se puede monitorizar Aerospike
**Sistemas donde se ha probado** | CentOS 7, Fedora, rocky linux |
**Sistemas donde debería funcionar** | Cualquier sistema linux |
--host | Ip o host |
--namespace | Nombre del namespace que monitorizar |
--agent\_alias | Alias del agente |
--use\_alias\_as\_name | Usar el alias del agente como nombre |
--module\_prefix | Para ponerle un prefijo a los módulos |
--port | Por defecto 3000 |
--database | Nombre de la base de datos |
--protocol | Por defecto : TCPIP |
--tentacle\_port | Puerto de tentacle.Por defecto 41121(opcional) |
--tentacle\_address | Ip del servidor tentacle al que mandar los datos(opcional) |
-g,--group | Grupo de destino de Pandora FMS (opcional) |
--data\_dir | Directorio de datos de Pandora FMS. **Por defecto** es /var/spool/pandora/data\_in/ (opcional) |
--as\_agent\_plugin | Es opcional, si quieres que el plugin sea de agente y te meta los módulos en el agente de pandora, ejecuta esto con un 1 (opcional) |
Recuerda que la ruta recomendada para el uso de los plugins de servidor es: /usr/share/pandora\_server/util/plugin/
Y en parámetros del plugin introduciremos estos seguidos de la macro "\_field<N>\_", son obligatorios los parámetros de conexion, --host y --namespace,. El puerto se puede cambiar si no se usa el de por defecto.Recuerda que puedes ponerle un nombre personalizado a los agentes con el parámetro --agent\_name
Una vez hecho esto, daremos a "crear". Una vez hecho esto, solo queda llamarlo por lo que iremos a la vista de algún agente y crearemos un módulo de complementos: [](https://pandorafms.com/guides/public/uploads/images/gallery/2022-03/image-1646741530197.png) Le daremos un nombre y en el apartado "plugin" pondremos el que acabamos de configurar. Una vez hecho esto, damos a crear. Si el modulo se muestra con 1, quiere decir que se esta ejecutando correctamente. # Módulos generados por el plugin El plugin creará un agente con los siguientes módulos:current_time | The current time represented as Aerospike epoch time. |
memory_used_bytes | The total bytes of memory used by this namespace on this node.", |
memory_used_data_bytes | The amount of memory occupied by data. |
memory_used_index_bytes | The amount of memory occupied by the index for this namespace. |
memory_used_sindex_bytes | The amount of memory occupied by secondary indexes for this namespace on this node. |
memory_free_pct | The percentage of memory capacity free for this namespace. |
xmem_id | The extended memory id of the namespace |
available_bin_names | The remaining number of unique bins that the user can create for this namespace. |
device_total_bytes | The total bytes of disk space allocated to this namespace on this node. |
device_used_bytes | The total bytes of disk space used by this namespace on this node. |
device_free_pct | The percentage of disk capacity free for this namespace. This is the amount of free storage across all devices in the namespace. |
device_available_pct | The minimum contiguous disk space for all disks in a namespace. |
cache_read_pct | The percentage of read transactions that are hitting the post write queue and will save an io to the underlying storage device. |
record_proto_uncompressed_pct | The percentage of single-record transaction client responses with uncompressed protocol message data. |
record_proto_compression_ratio | The average compressed size to uncompressed size ratio for protocol message data in single-record transaction client responses. |
migrate_tx_instances | The number of instance objects managing emigrations. |
migrate_rx_instances | The number of instance objects managing immigrations. |
migrate_tx_partitions_active | The number of partitions currently emigrating from this node. |
migrate_rx_partitions_active | The number of partitions currently immigrating to this node. |
migrate_tx_partitions_remaining | The number of migrations this node not yet sent during the current migration cycle for this namespace. |
migrate_rx_partitions_remaining | The number of migrations this node has not yet received during the current migration cycle for this namespace. |
migrate_signals_active | For finished partition migrations on this node, the number of outstanding clean-up signals, sent to participating member nodes, waiting for clean-up acknowledgment. |
migrate_signals_remaining | For unfinished partition migrations on this node, the number of clean-up signals to send to participating member nodes, as migration completes |
appeals_tx_active | The number of partition appeals not yet sent. Partition appeals will happen for namespaces operating under the strong-consistency mode when a node needs to validate the records it has when joining the cluster. |
appeals_rx_active | The number of partition appeals currently being received. Partition appeals will happen for namespaces operating under the strong-consistency mode when a node needs to validate the records it has when joining the cluster. |
appeals_tx_remaining | The number of partition appeals currently being sent. |
client_tsvc_error | The number of client transactions that failed in the transaction service before attempting to handle the transaction. |
client_tsvc_timeout | The number of client transactions that timed out while in the transaction service before attempting to handle the transaction. |
client_proxy_complete | The number of completed proxy transactions initiated by a client request. |
client_proxy_error | The number of proxy transactions initiated by a client request that failed with an error. |
client_proxy_timeout | The number of proxy transactions initiated by a client request that timed out. |
client_read_success | The number of successful client read transactions. |
client_read_error | The number of client read transaction errors. |
client_read_timeout | The number of client read transaction that timed out. |
client_read_not_found | The number of client read transaction that resulted in not found. |
client_read_filtered_out | The number of client read transactions that did not happen because the record was filtered out via a predicate expression. |
client_write_success | The number of write requests initiated by XDR that succeeded on the namespace on this node. |
client_write_error | The number of write requests initiated by XDR that failed on the namespace on this node. |
client_write_timeout | The number of write requests initiated by XDR that failed on the namespace on this nod |
client_write_filtered_out | The number of client write transactions that did not happen because the record was filtered out via a predicate expression. |
xdr_client_write_success | The number of write requests initiated by XDR that succeeded on the namespace on this node. |
xdr_client_write_error | The number of write requests initiated by XDR that failed on the namespace on this node. |
xdr_client_write_timeout | The number of write requests initiated by XDR that timed out on the namespace on this node. |
client_delete_success | The number of delete requests initiated by XDR that succeeded on the namespace on this node. |
client_delete_error | The number of client delete transactions that failed with an error. |
client_delete_timeout | The number of client delete transactions that timed out. |
client_delete_not_found | The number of delete requests initiated by XDR that failed on the namespace on this node due to the record not being found. |
client_delete_filtered_out | The number of client delete transactions that did not happen because the record was filtered out via a predicate expression. |
xdr_client_delete_success | The number of delete requests initiated by XDR that succeeded on the namespace on this node. |
xdr_client_delete_error | The number of delete requests initiated by XDR that failed on the namespace on this node. |
xdr_client_delete_timeout | The number of delete requests initiated by XDR that timed out on the namespace on this node. |
xdr_client_delete_not_found | The number of delete requests initiated by XDR that failed on the namespace on this node due to the record not being found. |
client_udf_complete | The number of completed udf transactions initiated by the client. |
client_udf_error | The number of failed udf transactions initiated by the client. |
client_udf_timeout | The number of udf transactions initiated by the client that timed out. |
client_udf_filtered_out | The number of client udf transactions that did not happen because the record was filtered out via a predicate expression. |
client_lang_read_success | The number of successful client initiated udf read transactions. |
client_lang_write_success | The number of successful client initiated udf write transactions. |
client_lang_delete_success | The number of client initiated udf transactions that successfully deleted a record. |
client_lang_error | The number of client initiated udf transactions that failed with an error. |