BCP Directory Is Not Accessible

Description

Triggered when the BCP directory is inaccessible due to permission restrictions or when the BCPPath directory is missing.

File import/export operations will fail.
If the BCP share becomes inaccessible, it will impact Processing, ARM, and Environment Watch, causing these components to malfunction or stop functioning properly.
Users will be unable to proceed with jobs that depend on access to the BCP directory.

Create a directory on the SQL Server in a location where the Relativity Service Account can read and write. Also ensure that SQL services have permissions to read from and write to this directory.
Update permissions on the BCPPath file share.
For more details, refer to Relativity Public Documentation to ensure the BCP share is correctly configured.

Name	Value	Description
Rule Type	Elastic Query
Data View	`metrics-*`
Filter Query	`relsvr.sqlbcp_networkshare.accessible : * and labels.state : "inaccessible"`	BCP directory cannot be accessed
Group	Count	Above 0 documents
Threshold	> 0	Count greater than 0 triggers the alert
Time Window	3 min	Evaluates data from the last 3 minutes
Frequency	2 min	Checks every 2 minutes

Metric Name:
relsvr.sqlbcp_networkshare.accessible

Metric Description:
Verifies whether the BCP share defined within the SQL Primary server is accessible from that server.

Metric Attributes:

Attribute Name	Description	Value
`labels.mount_point`	Location of metrics	`\\emttest\\BCPPath`
`labels.relsvr_host_installed_products`	Products installed	Invariant Queue Manager, Invariant Worker, Agent, Secret Store, Service Bus, Service Host, SQL Primary, Web
`labels.relsvr_server_type`	Servers to be verified	Agent, Invariant Queue Manager, Invariant Worker, SQL Primary, Secret Store, Service Bus, Service Host, Web
`labels.state`	State of metrics	accessible, inaccessible
`service.language.name`	Language	dotnet
`service.name`	Service Name	relsvr_infrawatch_agent
`service.version`	Version	V1