Semih Yesilyurt
45f7e3f5a4
Some checks failed
QA Gate (P0/P1) / Test affected app (pull_request) Has been cancelled
One row per proxied upstream attempt (pcat call/capture/validate, emex http) written fire-and-forget by the new ProxyTelemetryService (buffered, capped, errors swallowed — telemetry can never hurt the request path). - banned = upstream 403/429 (IP-block signal), distinct from auth/data errors - sticky legs (pcat capture, emex floxy) carry a session_key; pcat capture also resolves the actual residential exit IP via a parallel ipify probe through the same sticky session → concrete banned-IP tracking - rotating legs log provider + outcome (ban *rate* instead of per-IP) - 30-day retention piggybacked on the query-cleanup job Feeds the Süper Panel /analytics/proxy page (provider grading + banned IPs). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
12 lines
372 B
TypeScript
12 lines
372 B
TypeScript
import { Module } from "@nestjs/common";
|
|
import { ProxyTelemetryModule } from "../proxy-telemetry/proxy-telemetry.module";
|
|
import { EmexBrowserService } from "./emex.browser";
|
|
import { EmexService } from "./emex.service";
|
|
|
|
@Module({
|
|
imports: [ProxyTelemetryModule],
|
|
providers: [EmexBrowserService, EmexService],
|
|
exports: [EmexService],
|
|
})
|
|
export class EmexModule {}
|