Questions about the private beta.
Short answers about what Foveus is, what it is not, and why the private beta is centered on execution evidence.
Is Foveus replacing logs, traces, and metrics?
No. Foveus uses those signals as evidence. The private beta is focused on finding executions, inspecting execution detail, linking logs, grouping recurring issues, and alerting engineers with links back to evidence.
What is Execution Context Search?
It lets engineers search for executions using business or operational identifiers like CustomerId, OrderId, transactionId, username, service, endpoint, status, trace ID, or issue ID.
Why is execution the center of the product?
Logs are evidence, metrics are signals, traces show paths, issues show patterns, and alerts notify the team. The execution is the concrete run where the team can inspect what actually happened.
Are issues the main product?
No. Issues are the pattern layer. Executions are the evidence layer. Issues should always point back to representative and related executions.
Does Foveus use AI for root-cause analysis?
The private beta should stay evidence-first. Foveus can assist explanations later, but the core promise is not magic root-cause guessing. It is execution evidence.
Is this a full observability platform?
No. Foveus is not trying to replace Datadog, New Relic, Grafana, Seq, or Application Insights in private beta. It is an execution-first investigation layer for .NET backend teams.
How fast is onboarding?
The target is first telemetry in about 3 minutes: create a workspace, copy an API key, install the SDK, add Foveus to the app, run it, and see the first execution or log.
Why start with .NET?
Foveus starts with .NET because the first version should be deep and useful for a focused backend audience, not shallow across every language.