Storing context on job runs

[tabro]

I am using TickerQ to periodically fetch entities retrieved from different endpoints, and storing them locally.
I would love to have the ability to "store information" on the job run - i.e. the number of new entities retrieved etc.

This would enable me to look through the different job runs in the dashboard, and get some context of what happened during the different runs.

Could be as simple as storing a simple string per job run and exposing in the dashboard.

[Spinks90]

Someone has suggested implementing something like Hangfire.Console.
#39

What I did was hook it up with Serilog sink, and everytime I used the ILogger it would write to the current job so you can view the logs. Example:

So, anytime I'd call _logger.Information or other log types it would store them against the job using Hangfire.Console and Seq and disk.

I totally agree with you. This is one of the reasons I've not moved to TickerQ just yet.

[Daniel-GabrielN]

I am using TickerQ to periodically fetch entities retrieved from different endpoints, and storing them locally. I would love to have the ability to "store information" on the job run - i.e. the number of new entities retrieved etc.

This would enable me to look through the different job runs in the dashboard, and get some context of what happened during the different runs.

Could be as simple as storing a simple string per job run and exposing in the dashboard.

does this help?
https://tickerq.net/how-to/extend-entites.html

[Spinks90]

Bumping this. Any thoughts from maintainers?