Acceldata
 Pulse
Search documentation… ⌘K

Post-Installation Steps for Pulseaxn Agent

Configure Pulse to recognize and execute actions on standalone Pulseaxn agents by:

  1. Updating hydra_host.yml
  2. Pushing configuration to Pulse
  3. Enabling standalone actions mode in ad-axnserver

Prerequisites

  • Pulseaxn agent installation is completed and running
  • You know the PULSE_HOSTNAME values configured in:
    • pulseaxn_env.sh (VM)
    • or Kubernetes deployment env (PULSE_HOSTNAME)
  • Access to:
    • Manager Server API (for Kubernetes Pulse)
    • accelo CLI (for non-Kubernetes Pulse)

Step 1: Update hydra_host.yml

On the node where Pulse is installed (VM or Kubernetes cluster), edit the host section of hydra_host.yml.

Example:

cluster:
hosts:
"adaxn.standalone": ""
"adaxn.agent": ""
Important notes:
  • Hostnames must exactly match the value of PULSE_HOSTNAME configured in the Pulseaxn agent.
  • If multiple standalone Pulseaxn agents exist, list all of them under cluster.hosts.

Step 2: Push hydra_host.yml configuration to Pulse

A. Pulse running on Kubernetes

Use the push-config API to update the configuration in MongoDB:

curl --request PUT \
--url http://<Ingress API for the Manager Server>/api/v1/mserver/dbpush/<clustername> \
--header 'Authorization: Basic cHVsc2U6MjYzZjlmNTE2ZjdmNTA5OTE5NGI5MjZlZGJkZmY0ZmY='
This pushes the updated hydra_host.yml to the cluster configuration store.
B. Non-Kubernetes Pulse installation (VM / Docker)
Run the following command on the Pulse node:

accelo admin database push-config
Ensure you are pushing the config for the correct cluster where the standalone Pulseaxn agent is configured.

Step 3: Enable standalone actions mode in ad-axnserver

Pulse must be explicitly configured to read hosts from hydra_host.yml instead of Victoria Metrics.

A. Pulse on Kubernetes

Edit the ad-axnserver deployment:

kubectl edit deployment ad-axnserver -n <pulse_namespace>
Add the following environment variable under env:

- name: STANDALONE_ACTIONS_ENABLED
- value: "true"
Save and exit.
Kubernetes automatically rolls out a new pod with updated configuration.
B. Non-Kubernetes Pulse deployment
Step 1: Ensure the config file exists
If the file does not exist, create it:

accelo admin makeconfig ad-axnserver
This creates:

$AcceloHome/config/docker/addons/ad-axnserver.yml
Step 2: Edit the config file
Add the following under the environment: section:

- STANDALONE_ACTIONS_ENABLED=true
Step 3: Restart ad-axnserver

accelo restart ad-axnserver