Share a Tip

Run Event Service as a single-node cluster

Maciej_Popek
Engager

Hello, 

Per the official AppDynamics documentation, a single node Event Service cluster is not supported for production and should be used for PoV or testing purposes only. By default Event Service will be installed as "production" deployment, and expects such deployment to be on, hence it will fail/crash if it is run on single node.

To run a Single node, you will need to configure the events-service-api-store.yml accordingly:

  1. Comment out the following line (by putting "#" in front of the below line):

    cluster.initial_master_nodes: ${ad.es.cluster.initial_master_nodes}
  2. Add the following line under the above:

    discovery.type: single-node
  3. Comment out the following line  (by putting "#" in front of the below line):
    discovery.seed_hosts: ${ad.es.node.unicast.hosts}
  4. Restart Event Service to apply new configs.

Reference:
https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html#single-node-di...

If you encounter any issues when running the above configurations, please reach out to the AppDynamics support organization.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...