One or more expected Kepler application services are not available

Description

This alert is triggered when one or more expected Kepler application services are not available

API calls to the affected Kepler service will fail.
Any associated Relativity application functionality dependent on that service will also fail.
If not resolved, this may result in application-level outages or degraded user experiences.

Go to the host where the alert was triggered.
Open the Services control panel on the host.
Locate the kCura Service Host Manager Windows service.
If any Kepler application/service is not running, restart the kCura Service Host Manager service.
Wait approximately 5 minutes to allow all services to be deleted and recreated.
Refresh Kibana or your monitoring dashboard to verify the alert clears. Note: Ensure there are no active processing jobs are running when restarting the Service Host Manager as this will disrupt ongoing processing. Imaging Jobs: OCR Jobs PDF Generation Jobs Processing Jobs Export Jobs Relativity Analytics Jobs Database Cleanup or Housekeeping Jobs Custom Agent Jobs
Navigate to the Agents tab in Relativity.
Filter by the affected Agent Server.
Investigate the Last Message field for each agent:
Working agents should display: working on job in workspace
Idle agents will display: Completed

This alert is triggered for the following condition in Relativity:

Name	Value	Description
Rule Type	Elastic Query
Data View	logs-*
Filter Query	labels.event_type :"health_check" AND labels.status_state: "unhealthy" AND labels.event_source :"relsvr.servicehost" AND labels.name:"relsvr.servicehost.retry"
Group	Count
Threshold	> 0	Count greater than 0, alert triggers
Time Window	5 min	Verified data for last 5 minutes
Frequency	1 min	Checks for every 1 minute

Feedback

Why was this not helpful?

Check one that applies.

I could not find the information I was looking for.

The information was incorrect.

The instructions are confusing or unclear.

The instructions did not work.