Operational Guidance

Topic	Guidance
Deployment location	Deploy the script and all dependencies on each relevant Provider Agent machine. Verify that the command can run successfully under the service context used by RAS.
Logging	Use RAS logs plus script-side diagnostics. The framework documentation defines dedicated logs for protocol traffic and stderr output.
Failure handling	Expect transient and development-time failures. Connectors should fail cleanly, return structured errors, and avoid partial state corruption.
Backoff and resiliency	Frequent failures should not lead to aggressive retry loops. Build retry behavior carefully around provider APIs and rate limits.
Validation	A validation tool is planned so scripts can be checked against the contract before onboarding into RAS or escalation through support.
Concurrency	Do not rely on global files, registry keys, or other shared mutable state that would break when multiple connector instances execute concurrently.

Expected RAS-side logs

• CustomProvider.log - JSON communication between RAS and the script.

• CustomProvider.out.log - script stderr output, including exceptions and diagnostic messages.

• Vdiagent.log - Custom Provider activity, similar to other Tier 1 providers, including VM IDs, enumeration events, and command execution details.