logo

Monitoring & observability

Unified observability with Prometheus, Grafana and OpenTelemetry

See what your systems are doing before your customers tell you. Metrics, logs and traces in one open-source stack, with dashboards people use and alerts that only wake someone up for a real problem.

Plan my observability stack Zabbix monitoring

We reply within one business day.

Metrics · Logs · Traces

in one Grafana

Open source

no per-host or per-GB licences

Fixed price

scope agreed in writing before work starts

OpenTelemetry and exporters → Prometheus and Loki → Grafana alerts to Slack and PagerDuty

OpenTelemetry and exporters → Prometheus and Loki → Grafana alerts to Slack and PagerDuty

Works with

Prometheus

Grafana

Loki

Tempo / Jaeger

OpenTelemetry

Alertmanager

Zabbix

Elastic

PagerDuty

In short

We build open-source observability stacks: Prometheus for metrics, Grafana for dashboards and alerting, Loki for logs, Tempo or Jaeger for traces, and OpenTelemetry to instrument applications, all vendor-neutral and without proprietary agents. It runs in your cloud, on Kubernetes or fully on-prem. We design retention and storage so costs stay predictable, tune alerts with clear ownership and runbooks, and connect alerts to Slack, Teams or PagerDuty. For network devices and classic IT we combine this with Zabbix.

Services

What we do in observability

Metrics with Prometheus

Exporters, service discovery, recording rules and long-term storage (Thanos or Mimir) sized for your scale.

Logs with Loki

Central logs from apps, Kubernetes and servers, with retention you can afford and fast search.

Tracing and OpenTelemetry

Instrumentation that shows which service and which query makes a request slow.

Alerting that works

Alerts tied to user impact (SLOs), with owners, runbooks and routing to Slack, Teams or PagerDuty.

Grafana dashboards

Dashboards for engineers, management and customers, versioned as code.

Proof

Related work we delivered

Real projects. We name clients only with their permission.

Log platformCloud security provider (name withheld)

Zscaler and Okta logs in one searchable security platform

Challenge

Security events from several cloud services sat in separate consoles, which made investigations slow.

What we did

Ingest pipelines and Elastic Common Schema mappings for Zscaler and Okta logs, with dashboards for the security team.

Result

One place to search and correlate security events across services.

ElasticsearchECSZscalerOktaKibana
Elasticsearch, logging and SIEM →

Examples

Typical observability projects

Alert stormSLOs + ownershipRunbooksQuiet nights

Too many alerts, nobody trusts them

Alerts reworked around user impact so the on-call phone rings less and every page matters.

Datadog / New RelicOpenTelemetryPrometheus + LokiPredictable cost

Observability bill out of control

The same visibility on open source, with storage and retention you control.

Clusterkube-prometheusGrafanaAlerts

Kubernetes without visibility

Cluster, workload and application metrics in one place within days.

ZabbixPrometheusGrafanaOne dashboard

Zabbix plus Prometheus in one view

Network and classic IT from Zabbix next to cloud-native metrics, without replacing either.

How to start

How to start with observability

Observability review

Fixed priceagreed after a short call
  • Current tools, costs and gaps

  • Alert noise analysis

  • Target stack

  • About 1 week

Book the review
MOST POPULAR

Stack build

Fixed priceper phase, scoped in writing
  • Prometheus, Grafana, Loki

  • Dashboards and alerts as code

  • Retention and storage design

  • Handover

Plan the build

Managed observability

Monthly plansized to your needs
  • Upgrades and capacity

  • Alert tuning

  • New dashboards

  • Response times in writing

Ask about managed

Process

Getting started with observability

1

Review

What you monitor, what it costs, and which alerts get ignored.

2

Build

Stack, dashboards and alerts as code, rolled out service by service.

3

Tune and run

Alert reviews and upkeep, by your team or ours.

Why it matters

Why monitoring fails the people on call

Most teams have dashboards. Fewer have monitoring that tells the right person, at the right time, that users are affected.

Alert fatigue

Hundreds of noisy alerts train people to ignore all of them, including the real one.

Blind spots

Infrastructure is watched, but user-facing errors and slow requests are not.

Logs in many places

Investigations take hours when logs are spread across servers and services.

No traces

In distributed systems, finding which service made a request slow needs tracing.

Rising tool bills

Per-host and per-gigabyte pricing grows faster than the value you get.

No ownership

Alerts without owners and runbooks get passed around instead of fixed.

When you may not need a new stack

An honest note before you book.

  • A small system where your cloud provider's monitoring already covers it.

  • A paid tool you are happy with at its price.

  • If the main gap is alert tuning, start with an alert review instead of a rebuild.

Paid SaaS vs open source

Commercial observability SaaS vs an open-source stack run well

Area
Commercial SaaS
Open-source stack with us
Cost growth
Commercial SaaS: Per host, per gigabyte and per user.
Open-source stack with us: Storage and compute you control, with retention you choose.
Data location
Commercial SaaS: In the vendor's cloud.
Open-source stack with us: In your infrastructure and region.
Setup effort
Commercial SaaS: Quick to start.
Open-source stack with us: More setup, which we do for you.
Lock-in
Commercial SaaS: Proprietary agents and query languages.
Open-source stack with us: OpenTelemetry and open formats.
Fit for your alerts
Commercial SaaS: Defaults that need tuning anyway.
Open-source stack with us: Alerts designed around your services and SLOs.

Commercial tools are excellent and quick to start. Open source wins when volumes grow, data location matters or licence costs outgrow the value.

FAQ

Observability FAQ

Straight answers. Ask us anything else on a call.

Prometheus or Zabbix?

Prometheus fits cloud-native and Kubernetes; Zabbix is strong for network devices, VMware and classic servers. Many teams use both with Grafana on top.

Can we keep our current tools?

Yes. Grafana can show data from Prometheus, Zabbix, Elasticsearch, cloud monitoring and more, so you can migrate gradually or not at all.

How long does it take to set up?

A first useful stack with key dashboards and alerts typically takes a few weeks; coverage then grows service by service.

Can you add monitoring to our Odoo or n8n?

Yes: application, database and worker metrics, error logs and uptime checks, connected to the same alerting.

What is a unified observability platform?

One place where metrics, logs and traces are collected, linked and searched together, so you can jump from an alert to the slow trace and the matching log lines. With open source this is usually Prometheus or Mimir for metrics, Loki for logs, Tempo for traces and Grafana on top.

Can it ingest OpenTelemetry without proprietary agents?

Yes. The OpenTelemetry Collector receives metrics, logs and traces over OTLP and sends them to Prometheus or Mimir, Loki and Tempo. Your applications are instrumented once with open standards, so you can change the backend later without touching the code.

Can we run the observability stack on-prem?

Yes. Prometheus, Loki, Tempo and Grafana run on your own servers or Kubernetes clusters, including air-gapped networks, with object storage such as MinIO or Ceph for long-term retention.

Can you help reduce our Datadog bill?

Yes. We start with a review of your Datadog usage: custom metric cardinality, log indexing and retention, APM spans and host counts. Then we fix what can be fixed inside Datadog. If the bill is still too high, we move logs and infrastructure metrics to Loki and Prometheus (a hybrid setup), or the whole stack to open source with OpenTelemetry, running both in parallel until the new stack is proven.

Prometheus and Grafana: do we need both?

Usually yes. Prometheus collects and stores metrics and evaluates alert rules; Grafana shows dashboards and can alert across Prometheus, Loki, Tempo, Zabbix and other sources in one view.

Related

Related services

On-prem observability stack guide

Next step

Talk to an engineer about observability

Send a few details, and pick up to 3 times if you would like a call. We reply within one business day.

You talk to the expert who would do the work

Written scope and price after the call

No obligation

info@opensource.consulting
+1 514 577 8599

OpenSource Consulting

Open source solutions integrator: we design, build, integrate and support Odoo, n8n, Zabbix, Grafana, Kubernetes and databases.

info@opensource.consulting

+1 514 577 8599

Canada · Netherlands · UAE

Services

© 2026 OpenSource Consulting. All rights reserved. · Privacy · Cookies · Terms

Our brands: elasticsearch.expert · zd-inc.net · opsfinitive.io

Plan my observability stack