Repository navigation
RunSignal 0.1.0
First release.
Signals and specification
- The same OpenTelemetry metrics in every SDK: runs, duration, items, heartbeats, and the
since_successand
since_heartbeatgauges. Runs are also recorded as spans. - A workload manifest format (
spec/manifest.schema.json) and cross-language conformance vectors for naming
and signals.
SDKs and integrations
- .NET:
RunSignal.Core,RunSignal.DotNet,RunSignal.OpenTelemetry, plus Hangfire 1.8+ (RunSignal.Hangfire)
and Quartz.NET 3 and 4 (RunSignal.Quartz,RunSignal.Quartz4). - Go:
github.com/gokhanertogan/RunSignal/go, with robfig/cron (rscron). - Java:
io.github.gokhanertogan.runsignal:runsignalandrunsignal-spring-boot-starterfor Spring
@Scheduledand Spring Batch 5 and 6. - Node.js:
@runsignal/node, with BullMQ. - Rust:
runsignal.
Alerting
runsignalCLI:plan,diff,provisionanddestroyfor New Relic alert policies, NRQL conditions,
workflows and dashboards, andexport prometheusfor Prometheus alerting rules.- Alerts: missed, failed, stalled, overrun, low output, failure rate, item failure rate and not reporting.