CronRadar.Hangfire 0.0.3

.NET 6.0 This package targets .NET 6.0. The package is compatible with this framework or higher. .NET Standard 2.0 This package targets .NET Standard 2.0. The package is compatible with this framework or higher.
Suggested Alternatives

CronRadar.Hangfire 0.0.9

There is a newer version of this package available.
See the version list below for details. 
dotnet add package CronRadar.Hangfire --version 0.0.3
                    


                    

                
NuGet\Install-Package CronRadar.Hangfire -Version 0.0.3
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="CronRadar.Hangfire" Version="0.0.3" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="CronRadar.Hangfire" Version="0.0.3" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="CronRadar.Hangfire" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add CronRadar.Hangfire --version 0.0.3
                    


                    

                
#r "nuget: CronRadar.Hangfire, 0.0.3"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package CronRadar.Hangfire@0.0.3
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=CronRadar.Hangfire&version=0.0.3
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=CronRadar.Hangfire&version=0.0.3
                    


                            Install as a Cake Tool

CronRadar.Hangfire

Automatic monitoring for Hangfire background jobs. Get alerts when jobs fail or don't run on schedule.

Installation

dotnet add package CronRadar.Hangfire

Quick Start

Add CronRadar monitoring to your Hangfire configuration with one line:

services.AddHangfire(configuration => configuration
    .UsePostgreSqlStorage(connectionString)
    .UseCronRadar()); // That's it!

Configuration

Set your API key via environment variable:

export CRONRADAR_API_KEY=ck_app_xxxxx_yyyyy

Or pass it directly:

.UseCronRadar(apiKey: Configuration["CronRadar:ApiKey"])

How It Works

When you add .UseCronRadar() to your Hangfire configuration:

  1. All successful job executions automatically ping CronRadar
  2. Jobs are tracked using clean, readable monitor keys (e.g., email-send-daily-digest)
  3. CronRadar alerts you if jobs fail or don't run on schedule

Custom Monitor Keys

Use the [CronRadar] attribute for custom monitor keys:

[CronRadar("critical-backup")]
public void BackupDatabase()
{
    // Your job logic
}

Sync Jobs (Advanced)

For framework extensions that need to declare jobs upfront:

await CronRadarSync.SyncJobsAsync(new List<RecurringJobInfo>
{
    new RecurringJobInfo
    {
        Id = "check-billing",
        Name = "Check Billing Periods",
        Schedule = "0 0 * * *",
        GracePeriod = 300
    }
});

Requirements

  • .NET 6.0+ or .NET Standard 2.0+
  • Hangfire 1.7.0+
  • CronRadar API key from cronradar.com

License

Proprietary - © 2025 CronRadar. All rights reserved.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  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. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version 0.0.3:
- Improved monitor key generation (clean kebab-case format)
- Removed dependency on application ID configuration
- Application ID now extracted from API key automatically
- Added sync API for declaring jobs upfront
- Simplified integration - truly one line setup
- Better handling of job naming conventions