Product
The Runtime Control Plane for Production Logging
Changing log behavior in production should not require a deployment. SieveCore gives engineering teams real-time control over log levels with scoped policies, scheduled windows, automatic rollback, and full revision history — without code changes or restarts.
What It Does
Runtime log control. Without the deployment cycle.
SieveCore gives engineering teams governance over production logging at runtime. Default policies set the baseline. Runtime policies override them for a time window. Every change is recorded.
Runtime Log Control
Change log levels on running production services instantly. No code changes, no pull requests, no CI pipelines.
Dynamic Log Levels
Switch between DEBUG, INFO, WARN, and ERROR at runtime. Changes take effect in seconds.
Scheduled Logging
Define recurring logging windows. Enable verbose logging on a schedule without manual intervention.
Runtime Policies
Create temporary, scheduled, or manual policies with automatic expiration and rollback.
Signal Aggregation
Collapse repetitive log lines into single operational signals with occurrence counts and time ranges.
Operational Audit
Complete audit trail for every logging change. Who, what, when, and which service. Compliance-ready.
How It Works
Define the baseline. Override at runtime.
Default policies define your logging baseline. Runtime policies override them for specific time windows. The Effective Policy Inspector shows which policy is active and why.
Need visibility
An incident occurs. You need more log data.
Select deployment
Choose the specific service, deployment, or node.
Enable DEBUG
Set log level and duration. Change takes effect instantly.
Investigate
Analyze the verbose logs. Find the root cause.
Automatic rollback
Policy expires. Log level returns to original state.
See how engineers use it in practice.
Five steps. No redeployment. Full audit trail. Book a live demo to see the control plane in action.
Benefits
Governance that matters during operations.
Runtime-first design, automatic rollback, scoped targeting, revision history, effective policy visibility, and production-safe governance.
Runtime-first
Policy changes take effect at runtime. No container rebuilds, no CI pipelines, no deployment coordination.
Automatic rollback
Runtime policies expire and roll back automatically. No configuration drift. No forgotten DEBUG logging.
Governance by default
Every policy change is recorded with revision history. Know who changed what, when, and why.
Effective policy visibility
See exactly which policy is active and why across the full hierarchy from client to application.
Scoped targeting
Apply policies at client, cluster, namespace, or application scope. Only the selected scope is affected.
Revision history
Every change creates a revision. Review and roll back to any previous state.
Targeting
Control logging at any scope.
Visibility changes apply only where you select. From entire clusters down to individual pods.
Cluster
Apply logging policies across an entire cluster.
Node
Target a specific node within the cluster.
Namespace
Scope changes to a Kubernetes namespace.
Deployment
Target a specific deployment or service.
Pod
Apply changes to an individual pod.
Runtime Policies
Four policy types. One control plane.
Every policy type includes automatic expiration and rollback. No change persists without explicit intent.
Temporary policies
Set a duration — 30 minutes, 2 hours, or any custom window. When the time expires, the policy rolls back automatically.
Scheduled policies
Define recurring logging windows. Enable DEBUG every Saturday from 00:00 to 06:00. SieveCore manages the schedule.
Manual policies
Create a policy that persists until you explicitly remove it. Full control over activation and deactivation.
Emergency policies
Enable verbose logging immediately during an incident. Fastest path to diagnostic data when every second counts.
checkout-servicePolicy Rules
Signal Aggregation
Focus on signals instead of repetition.
Repetitive log lines collapse into a single operational signal with occurrence count and time range.
Database timeout
Built for Customer-Controlled Environments
Your logging governance, your infrastructure.
SieveCore runs inside your Kubernetes cluster. Your logging governance operates within your infrastructure, alongside your existing observability stack.
Customer-controlled deployment
SieveCore runs inside your Kubernetes cluster. Your logging governance stays close to your infrastructure.
Kubernetes-native
Designed for Kubernetes. Understands pods, deployments, namespaces, and clusters natively.
Revision history
Every policy change creates a revision. Review changes and roll back to any previous state.
Scoped access
Control who can create policies at each level of the hierarchy. Separate duties across teams.
Production-safe
Every change is reversible. Automatic rollback. No change persists without explicit intent.
Scheduled windows
Define when runtime policies are active. Automatic activation and deactivation.
Screenshots
See the control plane in action.
Real product screens showing policy management, log exploration, and audit trails.
SieveCore policy overview showing active logging policies with status, targets, and log levels
Questions
Frequently Asked Questions
Ready to control your production logs?
See how SieveCore gives your engineering team runtime control over production logging.