Kepler service failed to start after three attempts

Description

The alert is active when Kepler service failed to start after three attempts.

Alert Details

Alert ID: 8b899465-f542-46a1-9ea3-90c8db0acad2

Tags: Each tag should follow "key:value" format.

  • FeatureDomain:Service Host
  • PageType:Dashboard
  • PageID:7e6aa709-13ee-42f5-ac1f-8c5d50c3247c
  • CreatedBy:Relativity
  • ResolutionText:Restart the 'kCura Service Host Manager' Windows service
  • Resolution

Metric/Log/Trace Details

Log Name: Application *

Rule details

Alert Condition Description: Alert triggers when Kepler service failed to start after three attempts.

Name Value Description
Rule Type Elastic Query
Data View Logs-*
Filter Query when the count OF LOG ENTRIES with labels.event_type :"health_check" and labels.event_source :"relsvr.servicehost" and labels.name:"relsvr.servicehost.startup_service.failure"
Threshold > 0 Count greater than 0, alert triggers
Time Window 3 min Verified data for last 3 min
Frequency 1 min Checks for every 1 min

Requires User Intervention

  • Yes: alert immediately
    • Min time before the alert is active/inactive: 3 minutes

Kibana dashboard Kepler Service Overview link

One or more Resource Servers are inactive.