Symptoms
Aria Operations management packs may generate alerts that state certain Aria Automation services are in a 'stopped' state.An example of such services may include but not limited to:
lemans-resourceslemans-gatewayprivate-cloud-gatewayextensibility-servicedocker-artifactory idem-service-event-ingestionkube-proxy
The health check API used by Aria Operations (“<vRA-LB-FQDN>:8008/api/v1/services/cluster“ ) returns the following for the services in question:
"category": "app",
"name": "idem-service-event-ingestion",
"scope": "cluster",
"serviceInstances": [],
"state": "stopped"
Cause
vRA introduces new services on a regular basis to its platform. Those services may not always be immediately leveraged by any exposed features or their desired status may depend on what specific features are enabled in any given environment.
Resolution
In general, services that are reported as "stopped" by the 'vracli service status' command should not be regarded as problematic. Only a finding that a service is "started" but not "healthy" would require further investigation.
The state of services can be validated directly in vRA itself by connecting via SSH with root user credentials and running the below command:
vracli service status
Related Information
As of Aria Automation version 8.13.1 the idem-service-event-ingestion & kube-proxy services should no longer be flagged as stopped by the Aria Operations query to the health check url.
