Feedback
034d0230-bd3b-4c50-b17d-7b7fdd85ccd0
One or more Required Agents does not exist
Description
This alert is triggered when there are no Agent instances for Agent Types that require at least one Agent.
Resolution Guidance
Impact When Active
-
Missing required agents lead to important workflow failures in Relativity.
- Core Relativity operations performed by the missing Agent Type will not run.
- Automated or background jobs that rely on the missing Agent Type may fail or may not be scheduled.
- System health and performance may degrade depending on the role of the missing Agent Type.
How To Resolve
- Click on the Alert link in Relativity to go to the Kibana search named
[Relativity] Required Agents that do not exist - The Kibana search identifies the Agent Type of the missing agents.
- In Relativity, navigate to the Agents Tab. Then create a new Agent, of the identified Agent Type.
Alert Details
Alert Condition Details
| Name | Value |
|---|---|
| Rule Type | Elastic Query |
| Data View | metrics-* |
| Filter Query | relsvr.agent.exists : 0 and labels.relsvr_agent_required : 1 |
| Group | Count |
| Threshold | >= 1 |
| Time Window | Last 35 sec |
| Frequency | 5 min |
Alert Metric Details
Metric Name:relsvr.agent.exists
Metric Description: Whether the agent exists
- A value of
0indicates that the Agent does not exist. - A value of
1indicates that at least one Agent does exist.
Metric Attributes:
| Attribute Name | Description |
|---|---|
| host.name | Hostname of the affected Agent Server |
| labels.application_name | Application Name |
| labels.name | Name of the metric |
| labels.relsvr_system | System Name |
| labels.relsvr_subsystem | Subsystem Name |
| labels.relsvr_agent_required | Whether the agent is required |
| labels.relsvr_agent_type_name | Agent Type Name |
| labels.relsvr_agent_type_guid | Agent Type Guid |
| labels.message | Message describes the issue |