Skip to main content
Nathan Claire Group
Edge platformEdge Datalake
LAKE · Edge platform module

Edge Datalake: the unified performance data behind every insight

The single repository that unifies telemetry from all twelve Edge modules. Every metric, trace, log and event stored together, queryable together, and retained under your sovereignty terms.

LAKE
Edge Datalake
Edge platform · Module
One of twelve modules writing to the Edge Datalake. All signals correlated across modules automatically.
Ingest rateStorage utilisationQuery latencyCross-module correlation depthRetention coverage+1 more
Live dashboard preview

See exactly what your team will see

Live data simulation
EdgeProductionEdge Datalake
Last 1h
LIVE
Events / sec
98,700
all sources combined
Ingested today
2.4 TB
465B events
Stored total
18.2 TB
across 3 tiers
Pipeline health
99.98%
processing success
Query latency
1.2s
p95 across all queries
Ingestion pipelinereal-time flow
Ingest98.7K/sProcessschema · enrichStore18.2 TBRetainhot · warm · coldQuery1.2s p95Hot (30d)4.8 TBWarm (90d)8.1 TBArchive (1y)5.3 TB
Source breakdowntoday · 2.4 TB total
RUM
180 GB·22.1M
APM Traces
240 GB·8.4M
Logs
820 GB·361M
Infrastructure
210 GB·48.2M
Synthetic
18 GB·2.1M
Network
95 GB·12.8M
Transactions
41 GB·4.4M
Database
52 GB·6.1M
One data foundation
Telemetry from all 12 Edge modules arrives here — 48 sources, unified.
2.4 TB ingested today
Across all sources: RUM, APM, Logs, Infrastructure, Synthetic, Network and more.
2.4 TB / day
Pipeline: 99.98% health
Processing success rate. 0.02% failures are schema mismatches, auto-quarantined.
Retention policy active
Hot: 30 days · Warm: 90 days · Archive: 1 year — fully automated tiering.
Connected toOpenTelemetry — pipeline APM — distributed traces Overwatch — analysis
Capabilities

What it puts in front of your teams

Every capability is available from day one. No additional instrumentation required beyond the initial agent deployment.

See a live demonstration
01

Single repository

All twelve modules write to one lake. Every metric, trace, log and event is queryable together with no silos.

02

Prediction ready

The historical depth and breadth of the lake enables the forecasting and anomaly detection models that power Edge AI.

03

Feeds automation

Every playbook, alert and AI recommendation draws from the lake, ensuring decisions are based on the full picture.

04

Data sovereignty

Deployed inside your infrastructure. Data never leaves your environment or crosses a border without your explicit control.

05

Tiered storage with full query

Hot data stays fast; cold data remains accessible. No blackout periods on historical queries regardless of retention tier.

06

Custom retention policies

Define retention rules per signal type, per regulation or per business unit, and prove compliance with an audit log.

How it works

From signal to action in seconds

01

Deploy once

A lightweight Edge agent deploys to your environment. Auto-discovery maps services, hosts and applications without manual configuration.

02

Collect everything

30 days of database latency data reveals a pattern: every Thursday at 23:00, a batch job causes contention that persists into Friday morning. A scheduled alert and preemptive maintenance window fix the problem permanently.

03

Act with confidence

Anomaly detection, root cause analysis and AI-assisted recommendations give your teams the context to act fast and correctly.

What it measures

Signals captured by LAKE

Ingest rateStorage utilisationQuery latencyCross-module correlation depthRetention coverageData sovereignty boundary
In practice
Real scenario

30 days of database latency data reveals a pattern: every Thursday at 23:00, a batch job causes contention that persists into Friday morning. A scheduled alert and preemptive maintenance window fix the problem permanently.

Business outcomes

What changes for the business

01

Whole picture analytics

Query across every signal type in one place. No joining data from separate tools or exporting to spreadsheets.

02

Cost optimised retention

Tiered storage keeps hot data fast and cold data affordable, with full query access across both.

03

Foundation for AI

The breadth and depth of the lake is what makes Edge AI recommendations meaningful rather than generic.

Platform ecosystem

Better together with the Edge platform

LAKE writes its data to the Edge Datalake, making it queryable and correlatable alongside every other module in real time.

EDGE Platform · Service Topology
COLLECTIONAPPLICATIONINFRASTRUCTUREINTELLIGENCEReal UserBrowser · MobileSyntheticGlobal probesTransactionsE2E tracingApp PerformanceCode-level APMLog MonitoringStructured · tailNetwork Mon.Flow · topologyInfrastructureHosts · VMs · K8sDatabaseQuery insightsSchedulerJob trackingAI AgentAIOps · OverwatchOpenTelemetryOTLP · gRPCEDGE DatalakeUNIFIED · REAL-TIME · QUERYABLE11MODULES100+SOURCES99.99% uptime SLA11 nodes · 11 connections · 1 unified datalakeNCG Africa Ltd
11Modules
< 2%Agent CPU
1Unified Datalake
100+Connectors
Questions

Edge Datalake questions, answered

What is enterprise observability?

Enterprise observability is the ability to understand the internal state of complex distributed systems by examining the outputs they produce — metrics, traces, logs, and events — at the scale and depth required by large organisations. It goes beyond basic monitoring to provide the context needed to understand why a system is behaving a certain way, not just that something is wrong.

What is observability?

Observability is a measure of how well the internal state of a system can be inferred from its external outputs. In software and IT operations, observable systems produce rich telemetry — metrics, distributed traces, structured logs, and events — that together allow teams to understand system behaviour, detect problems, and diagnose root causes without having to predict failure modes in advance.

Why is observability important?

Modern applications are distributed, dynamic, and complex. Traditional monitoring — checking whether a server is up or a threshold has been crossed — cannot provide sufficient context when something goes wrong in a microservices architecture or cloud-native environment. Observability gives teams the data and tools to ask arbitrary questions about system behaviour and get useful answers quickly, which directly reduces incident duration and prevents repeat failures.

How does observability improve system reliability?

Observability improves system reliability by giving teams the information they need to detect problems early, understand their scope, and resolve them quickly. It also supports proactive reliability work — identifying bottlenecks, understanding dependencies, and validating that changes have the expected effect — before problems reach production.

What does Edge Datalake monitor?

Edge Datalake captures signals including ingest rate, storage utilisation, query latency, cross-module correlation depth, retention coverage, data sovereignty boundary, and provides single repository, prediction ready, feeds automation and more.

How is Edge Datalake deployed?

Edge connects through lightweight agents or agentless connectors — typically 2–4 hours for a standard environment — and can be deployed on-premises, in your private cloud or in a regional cloud, so monitoring data stays within your jurisdiction.

Does it work with the monitoring tools we already use?

Yes. Edge is designed for a no-rip-and-replace approach and connects alongside your existing stack, with 100+ integrations across cloud, containers, databases, APM agents, telemetry standards and alerting channels.

How is it priced?

Pricing is tailored to the scale of your environment, the modules you choose and your deployment model. Start with a short, no-obligation discovery session and NCG will prepare a scoped proposal.

More answers in the FAQ library, or book a demo to see LAKE on your own environment.

LAKE · Edge platform

Ready to see Edge Datalake live?

We deploy a proof of value in your environment. You keep it if it delivers. No long commitments, no surprises.