There should be an embedded view which allows to see what's happening inside a process that hosts Quartz. Some initial thoughts:
Marko,
I think all of the above are necessary
I'd like to suggest also:
The QuartzNetFeaturePack has a plugin that uses owin (nancy but that's because back then webapi didn't run outside of iis) and has a very simple api started. I just started yesterday on moving the front end to Aurelia, so I'm good with that as well.
Let me know how I can help. Happy to move that into the main project or keep it separate for now.
J
Marko,
what about a conmaker included
REST like API for basic scheduler tasks, "remoting V2"
Very much this, except replace basic with complete.
At the moment we've got a (far too basic) version of this embedded in our already existing admin app. I'd love to shift to a community supported version, but not too keen on standing up a separate admin app. As long as the data that it displays can be easily retrieved from a new REST API then I'd have the option of either using an out of the box UI or continuing to maintain a UI integrated with our existing app but sourcing the data from a REST API. The remoting API is a slightly hard to work with, especially when the scheduler is down.
In terms of features, supporting multiple schedulers would be good for us too. My plan had been to merge the data from both schedulers into a single view with an indication of which scheduler a job was running in.
Finally, I did write an Entity Framework 6 based persisted job execution history that I'd be happy to contribute. It's implemented as an IJobListener. It does have a slight dependency on Autofac at the minute just to get easy lifetime management (via the Owned concept) but this could be removed. Let me know if you're interested enough for me to package it up a bit to share it out.
Hi, where I can find a road map for 3.0 version, and when it will be available. Because right now I'm doing same - implementing web ui to handle quartz tasks...
Any dates for 3.0 version?
The current road map is roughly the issues listed in the tracker:
https://github.com/quartznet/quartznet/milestones/3.0
Some issues should then opened for discussion, just like this web dashboard one where we can discuss the individual requirements.
There's no date for 3.0, just the famous "it's done when it's done". As there is no dedicated personnel in this project it's all about finding the free time to spare. So unfortunately I can't give estimates because we'd be probably failing them...
Does bootstrap v3 used on fronted side?
What about security layer for the dashboard and api controllers? Does it implemented or it just in plans for now?
Yes, the UI is based on bootstrap at the moment. A security layer probably should be implemented too.
I'm dropping this from 3.0 to deliver the basic functionality of the core at least. Haven't had the required time for this undertaking.
Hi @lahma ,
Just want to know if the dashboard is still on the radar screen. Been using qrtz with asp.net core but dashboard would be seriously useful. Something like https://github.com/HangfireIO/Hangfire
It's open source and something similiar in qrtz would be great, i don't think anyone needs to reinvent the wheel here.
@Pinox I would love such a feature too. Contributions are more than welcome to get things rolling - PRs targeting the web project adding functionality etc.
As I was looking for this feature, I found my needs to be mostly covered by https://github.com/guryanovev/CrystalQuartz
@pierluca thanks bud, I did not know this.
Hi, I recently published new alternative web UI. You can manage jobs, triggers, calendars and most of the API which IScheduler provide. It is pluggable into existing OWIN and ASP.NET Core application or it creates embedded web server on it own. You can put strongly typed values to JobDataMap or edit existing JobDataMap of job or trigger. List and histograms for recently executed jobs is also included.
I'd like to ask both @jlucansky and @guryanovev for an opinion. Would it make sense to develop shared JSON API on Quartz's side (see API related requirements in issue description) and then adapt both of your UI parts to share?
I know that you both have put hard work into your management UIs and they probably are opionated and follow the requirements you have set for them, both possible having pros and cons. So my guess is that there's neither an easy merge of UI solutions nor much requirement to do so (unless you see the benefit).
Easily accessible REST'ish API would allow users to define Yet Another UI / console application / integration they need, also covering .NET Core which now has none from Quartz's side. I already had some effort on building one but now that there are three competing solutions for the same goal of having HTTP exposed management methods it feels a bit silly.
I created Quartzmin with no intention to be used as the universal REST API so it is not as clean and straightforward as it should be. But, as part for my another work project, I was forced to replace .NET remoting with web API and I crafted pretty complete API for IScheduler. Right now, it targets only full .NET Framework but it can be used as starting point or inspiration: https://gist.github.com/jlucansky/1c5b8e4befa3b745b4485184811caa2f
There is also working client side if you are interested...
I am completely new to using Quartz.net but I am trying to figure out whether it will work for our needs. I also need it to be a WebAPI basis and what you show looks very close to my needs. Question, are you running the Quartz instance on the same machine as the WebAPI or using a Windows service to do that task?
Most helpful comment
Hi, I recently published new alternative web UI. You can manage jobs, triggers, calendars and most of the API which IScheduler provide. It is pluggable into existing OWIN and ASP.NET Core application or it creates embedded web server on it own. You can put strongly typed values to JobDataMap or edit existing JobDataMap of job or trigger. List and histograms for recently executed jobs is also included.
https://github.com/jlucansky/Quartzmin