1. The APM view #
Services at a glance.
Services #
The Services page lists each service with its RED metrics (throughput, error rate, p50/p95/p99 latency) computed from spans. A service's page details its key operations, its database and external calls, and gives access to the corresponding traces.
| View | Usage |
|---|---|
| Services | Health of each service |
| Service map | Dependencies between services |
| Traces explorer | Trace search and analysis, timeline |
| Logs explorer | Log search, link to the associated trace |
| Exceptions | Errors grouped by type, with stack trace |
| Dashboards | Custom dashboards |
2. Querying #
Three ways.
Query builder, ClickHouse, PromQL #
The query builder builds queries from filters and aggregations, without knowing the schema. To go further, you write ClickHouse SQL or PromQL on metrics directly.
-- Exemple de requête ClickHouse dans un panneau SigNoz (le schéma exact dépend de la version)
SELECT serviceName AS service, count() AS erreurs
FROM signoz_traces.distributed_signoz_index_v3
WHERE timestamp > now() - INTERVAL 1 HOUR AND hasError = true
GROUP BY service
ORDER BY erreurs DESCGood to know: Check the table schema (SHOW TABLES FROM signoz_traces) before writing SQL queries: names and columns change between SigNoz versions.3. Alerts and dashboards #
Monitoring.
Alerts #
| Alert type | Example |
|---|---|
| Metrics | checkout p95 latency > 500 ms for 5 min |
| Logs | More than 100 level=error logs in 5 min for a service |
| Traces | More than 2% of spans in error on an operation |
| Exceptions | New exception appeared |
Notification channels (Slack, email, webhook, PagerDuty, Opsgenie, Teams) are configured in the settings. Ready-made dashboards exist for hosts, Kubernetes, databases and runtimes (JVM, Go).
My progress
Sign in to track your progress and take notes. Sign in
💬 Questions about this lesson
No questions yet: be the first to ask for help or share your configuration.
Recommended Articles
SigNoz, ClickStack and ClickHouse best practices for observability
Best practices for observability on ClickHouse with SigNoz or ClickStack: OpenTelemetry instrumen...
Observability on ClickHouse: why a columnar database changes the game
Why more and more observability platforms store logs, traces and metrics in ClickHouse: columnar ...
SigNoz: architecture and installation
SigNoz components (OpenTelemetry collector, ClickHouse, query service, interface, alerts), instal...
Operating an observability platform on ClickHouse and choosing a tool
Operate ClickHouse for telemetry (replication, disks, merges, object storage, monitoring) and com...
Telemetry in ClickHouse: schema, SQL, materialized views and retention
Telemetry in ClickHouse: otel_logs, otel_traces, otel_metrics_* and hyperdx_sessions tables, sort...
Alerts and dashboards in ClickStack
Building charts and dashboards in ClickStack, creating alerts on a search or a chart, sending the...
The observability trilemma: cost, completeness and performance, and how solutions resolve it
Understanding the observability trilemma (cost, data completeness, query performance), its three ...
Datadog APM and OpenTelemetry: traces, services and correlation with logs
Instrument applications for Datadog APM (dd-trace, single step instrumentation, OpenTelemetry), u...
Exploring with the ClickStack UI: sources, search, traces, sessions and SQL
Using the ClickStack UI (HyperDX): data sources, property and full-text search syntax, SQL mode, ...