BackgroundJob.Enqueue<IMediator>( x => x.Send(new MyCommand(entity_id), cancellationToken));
This works just fine, the problem is that in the dashboard all jobs capture the expression method as name, and when something goes wrong I have to inspect each item in the dashboard to get its parameters.
Looking back there seemed to be a IDashboardJobNameProvider which got refactored into DisplayNameFunc in DashboardOptions. But consider this
endpoints.MapHangfireDashboard("/hangfire", new DashboardOptions {
DisplayNameFunc = (DashboardContext context, Job job) => {
// ??? neither the context nor the job has any property that could be used to get the job name
// job.id?
// context.PropertyBag?
// job.PropertyBag?
// anything?
}
});
Am I missing something? I love the framework and do understand the design choice behind not too much dynamic data, but this is a simple use case I have and I am stuck.
This is my dispatching to the queue
BackgroundJob.Enqueue<IMediator>( x => x.Send(new MyCommand(entity_id), cancellationToken));
This works just fine, the problem is that in the dashboard all jobs capture the expression method as name, and when something goes wrong I have to inspect each item in the dashboard to get its parameters.
Looking back there seemed to be a
IDashboardJobNameProvider
which got refactored intoDisplayNameFunc
inDashboardOptions
. But consider thisAm I missing something? I love the framework and do understand the design choice behind not too much dynamic data, but this is a simple use case I have and I am stuck.