General Settings
Graph Settings
Kubernetes Settings
Namespace scope
Scope which namespaces Edge maps into the resource graph, so blast radius and dependency maps cover only the workloads that matter to you. Filtering is off by default — every namespace is graphed.
Cluster-scoped resources (nodes, persistent volumes, storage classes) are always graphed regardless of mode. Namespace names must be valid DNS-1123 labels.
Allow-list — map only production workloads:
In
deny mode the same namespace list also seeds the Network Observability Hubble flow filter (netobs.excludeNamespaces), so dropped namespaces are excluded from traffic collection too.Services (DNSTap) Settings
Publisher Settings
Sentry Settings
Example Configuration (JSON)
Edge Proxy Configuration
These settings apply when you deploy on-prem connections alongside Edge. Adding anyonPremConnections entry automatically deploys the Edge Proxy.
Edge Proxy Stream Settings
These settings control the persistent gRPC connection between the Edge Proxy and NOFire.Edge Proxy HTTP Client Settings
These settings apply to HTTP requests made from the Edge Proxy to your data sources.PII Redaction
The Edge Proxy redacts sensitive data from response bodies before sending them to NOFire. Redaction is on by default.Standard PII Patterns
WhenstandardPII is true, these patterns are applied in order:
Patterns 13 (credit card) and 15 (phone) use validators to reduce false positives. Credit cards are checked with the Luhn algorithm. Phone numbers require separators or a
+ prefix.
Edge Proxy General Settings
Secret Key Reference
The Edge Proxy reads credentials from files mounted at{secretsPath}/{secretName}/{key}.
If both
token and username are present, token takes priority (except for MongoDB Atlas, which always uses digest auth).

