Telemetry pipelines, instrumentation and monitoring for engineering teams. Work directly with Jacky Pham, from the first investigation to handover.
Inspect a synthetic event as its fields are checked, its destination fails and delivery recovers.
A service name, environment and correlation ID let a responder connect this event to an investigation.
The synthetic email is deliberately included to test redaction. In production, unnecessary personal data should be omitted at the source.
{
"service": "snoogz-demo",
"event": "request.completed",
"environment": "sandbox",
"correlation_id": "demo-1042",
"customer_email": "guest@example.test"
}The email has been removed. The fields needed to find the event remain unchanged.
Agree on an allowed schema, test the output at every destination and keep credentials out of telemetry.
{
"service": "snoogz-demo",
"event": "request.completed",
"environment": "sandbox",
"correlation_id": "demo-1042"
}The destination is unavailable in this example. The redacted event waits for a bounded retry; delivery is still pending.
A real pipeline needs agreed buffer limits, retry limits and an owner to alert when events are rejected or capacity is exhausted.
{
"service": "snoogz-demo",
"event": "request.completed",
"environment": "sandbox",
"correlation_id": "demo-1042"
}The destination is restored in this example. The same redacted event can be found using its original correlation ID.
Test recovery against the selected collector and destination. Document duplicates, drops and delivery guarantees rather than assuming them.
{
"service": "snoogz-demo",
"event": "request.completed",
"environment": "sandbox",
"correlation_id": "demo-1042"
}A browser-only simulation using synthetic data. Nothing is collected or sent. Actual buffering, retention and delivery behaviour depend on the tools and configuration agreed for your project.
Bring a difficult investigation. We trace the path from application to collector, pipeline and monitoring tool, then scope the change.
Observability pipelines with Edge Delta. Platform ownership of Splunk and Datadog, alongside AI tooling and use-case development.
Grafana, Prometheus, Loki and OpenTelemetry instrumentation, with production incident support.
Experience from Jacky’s roles within these teams. Each Snoogz engagement has its own scope, access and review process.
Agree on acceptance before changing the pipeline. Review the test results and remaining limits together.
The agreed configuration or code, test evidence, dashboards and a short runbook. Deployment, rollback, account access and alert ownership each have a named owner.
Choose a defined project or embedded engineering. Ongoing maintenance, response hours and incident responsibilities are scoped separately.
Start with an assessmentIf access or feasibility needs to be established first.That is the starting point. We review the current collection and monitoring setup, the questions it must answer and the constraints on changing it. A new tool is an option when the existing setup cannot meet an agreed requirement.
A project or embedded engagement does not automatically include round-the-clock monitoring or incident response. Response hours, alert ownership and support responsibilities are agreed explicitly before work begins.
Possible uses include preparing an incident summary or helping a responder search approved runbooks. We assess the information available to the tool and how its output will be checked. Access to production data and automated actions require an agreed scope; they are not assumed.
Start with one difficult investigation, the tools involved and the result your team needed. Share sanitised examples first. We agree on access before reviewing production systems or sensitive telemetry.
Tell me which workflow or system needs attention. Five short questions help outline a review, project or embedded engagement you can discuss by email.
Start a project Review your brief, then continue in email.Snoogz Software is based in Canada and uses Google Workspace for email. These services may process your information outside your country. Please avoid sensitive personal information. Read our privacy notice.