Keryhe.Telemetry.Timescale
1.2.4
dotnet add package Keryhe.Telemetry.Timescale --version 1.2.4
NuGet\Install-Package Keryhe.Telemetry.Timescale -Version 1.2.4
<PackageReference Include="Keryhe.Telemetry.Timescale" Version="1.2.4" />
<PackageVersion Include="Keryhe.Telemetry.Timescale" Version="1.2.4" />
<PackageReference Include="Keryhe.Telemetry.Timescale" />
paket add Keryhe.Telemetry.Timescale --version 1.2.4
#r "nuget: Keryhe.Telemetry.Timescale, 1.2.4"
#:package Keryhe.Telemetry.Timescale@1.2.4
#addin nuget:?package=Keryhe.Telemetry.Timescale&version=1.2.4
#tool nuget:?package=Keryhe.Telemetry.Timescale&version=1.2.4
Keryhe.Telemetry.Timescale
TimescaleDB provider for Keryhe Telemetry — a
hypertable-aware write path on top of Npgsql/Dapper, reusing the
Keryhe.Telemetry.PostgreSQL read repositories.
What it provides
AddTimescaleCollectorServices(configuration)— registers a singletonNpgsqlDataSource(fromConnectionStrings:Collector),ITelemetryBulkWriter, andITenantResolver, targeting TimescaleDB's hypertables for the metric data-point tables andlog_records.AddTimescaleApiServices(configuration)— registers a singletonNpgsqlDataSource(fromConnectionStrings:Api) and the read repositories (includingIRetentionSettingsRepository), derived from the PostgreSQL implementations since the query surface is identical.
Install this package alongside Keryhe.Telemetry.Collector (write side) and/or
Keryhe.Telemetry.Api (read side), and set Database:Provider to Timescale.
Usage
builder.Services.AddTimescaleCollectorServices(builder.Configuration);
builder.Services.AddTimescaleApiServices(builder.Configuration);
Configuration:
Database:Provider— must beTimescale.ConnectionStrings:Collector/ConnectionStrings:Api— Npgsql connection strings, e.g.Host=localhost;Port=5432;Database=telemetry;Username=postgres;Password=<password>.- In the all-in-one host (
Keryhe.Telemetry.Server), the write and read connection strings must be identical — the underlyingNpgsqlDataSourceis a process-wide singleton.
Apply schema/Timescale-Schema.sql (or schema/apply-schema.sh timescale) before first use. It
sets up hypertables on the metric data-point tables and log_records, compression starting at 7
days, retention (metrics 180 days, logs 90 days), and a continuous aggregate
(log_severity_stats_daily, refreshed every 5 minutes) behind the log_severity_stats view.
Documentation
See the project README and CLAUDE.md for the full architecture and setup guide.
License
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Dapper (>= 2.1.79)
- Keryhe.Telemetry.Core (>= 1.2.4)
- Keryhe.Telemetry.PostgreSQL (>= 1.2.4)
- Npgsql (>= 10.0.3)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.