Skip to content
molesignal
Solution · Kubernetes observability

Turn Kubernetes telemetry into an investigation path, not another silo.

Onboard cluster logs through the guided Fluent Bit path, receive application metrics and traces through existing collectors, normalize workload context before storage, and move from a symptom to the responsible service or event.

Explore data pipelines See integrations
Solution · Kubernetes observability
MoleSignal data pipelines showing healthy log, metric, and trace processing workflows
guided log onboarding
Fluent Bit
application telemetry
OTLP
query surfaces
SQL + PromQL
deployment manifests
Kubernetes

Collect, shape, and investigate workload telemetry.

The current path focuses on open collectors and structured workload context rather than inventing a separate Kubernetes-only backend.

01

Guided Kubernetes onboarding

Generate a workspace endpoint and token, deploy the supplied Fluent Bit DaemonSet path, and verify that real log data arrived.

02

Pipeline normalization

Parse, enrich, redact, and route incoming workload telemetry before it becomes durable storage.

03

Structured workload investigation

Filter logs and events by namespace, pod, container, service, environment, or other collector-provided resource attributes.

04

Metrics and trace context

Use PromQL and OpenTelemetry traces to continue from service behavior into the request and dependency path.

workflow

From collector deployment to a correlated workload investigation.

Each step remains inspectable, from the endpoint and token to the received stream and downstream query.

  1. 101 · Connect

    Create the workspace ingestion path

    Use the guided datasource flow to obtain the endpoint, scoped token, and collector instructions.

  2. 202 · Collect

    Deploy Fluent Bit and existing OTel collectors

    Send container logs and application telemetry without introducing a proprietary node agent.

  3. 303 · Shape

    Normalize workload attributes in pipelines

    Keep namespace, pod, container, service, and environment fields useful while applying routing or redaction policy.

  4. 404 · Investigate

    Query the workload across signals

    Start with the affected resource scope and continue into service metrics, trace evidence, and exact events.

proof / shipped

The Kubernetes path is visible in the current product and repository.

The shipped surface includes guided datasource onboarding and receipt verification; the repository includes multi-role Kubernetes deployment manifests.

  • Fluent Bit DaemonSet onboarding instructions
  • Workspace endpoint, token, and real receipt verification
  • Logs, metrics, and traces pipeline processing
  • Router, ingester, querier, compactor, alert-manager, connector, and web manifests
Solution · Kubernetes observability

Turn Kubernetes telemetry into an investigation path, not another silo.

Onboard cluster logs through the guided Fluent Bit path, receive application metrics and traces through existing collectors, normalize workload context before storage, and move from a symptom to the responsible service or event.

Explore data pipelines See integrations