Interface IPersonalDataAnalyzerProbe

Namespace

MailFathom.Application.SensitiveContent.Detection

Assembly

MailFathom.Application.dll

Establishes that the personal-data analyzer this deployment configured answers, and can be asked again whenever that has to be established.

public interface IPersonalDataAnalyzerProbe

Remarks

The personal-data scanner reaches an analyzer deployed beside the service, and the port above it fails closed: with the Pii switch on and that analyzer absent, every guarded read, write, and egress is refused. A deployment in that state is not degraded, it is stopped — which is why the question is asked directly rather than discovered one refused operation at a time, and why the answer removes an instance from traffic rather than softening what it serves.

The analyzer is a sidecar with a lifetime of its own, so the answer is not a fact about start-up. It may become reachable after this process does and may stop answering long afterwards, which is why the readiness probe asks on every scrape rather than a gate asking once.

It is a port of its own rather than a member of ISensitiveContentScanner because the two ask different questions of the same analyzer. A scan asks what a text carries and says nothing an operator can act on; this asks whether the analyzer is there at all, and its failure exists precisely to name the configuration key an operator has to fix. Neither one puts the analyzer's address in a message: this one carries it on the failure's own property instead.

Nothing registers an implementation unless the switch is on, so a deployment that never opted in never probes anything.

Methods

VerifyAvailableAsync(CancellationToken)

Verifies that the configured analyzer answers, and that it recognises at least one entity of every category this deployment switched on.