Hi Peter,
A possible approach for reporting on past job executions would be:
1. Create a data graph asset collection (or custom asset collection type) such
as “Job Execution Log”
2. Modify the job so that it updates this asset collection and inserts desired
information about its execution
3. Devise SPARQL or GraphQL queries to retrieve this information in an
appropriate format
4. Use your preferred front-end development technology to create a view based
on these query results; this could be a view inside EDG, or an external
application that queries EDG via the SPARQL/GraphQL endpoints
A possible approach for reporting on upcoming job executions would start with
this SPARQL query which uses the teamwork:scheduledJobStatus property function:
PREFIX teamwork: <http://topbraid.org/teamwork#>
SELECT * {
?job teamwork:scheduledJobStatus (?schedule ?nextFireTime
?currentExecutionId ?currentExecutionDurationMs ?schedulingUser)
}
1. The SPARQL query returns currently defined jobs including their cron
schedule expression and each job's next fire time
2. Devise a way to calculate future execution times from the cron expression.
We don't have any APIs that help with this beyond the ?nextFireTime above.
3. Use your preferred front-end development technology to create a view based
on the SPARQL query results; this could be a view inside EDG, or an external
application that queries EDG via the SPARQL/GraphQL endpoints
Manipulating the schedule of upcoming executions is not possible, with the
exception of triggering a job execution right now, and modifying the cron
expression for user-scheduled jobs.
I don't have the skills to advise on front-end questions like calendar views
etc.
Richard
> On 29 Mar 2022, at 03:34, Peter Philips <[email protected]>
> wrote:
>
> Hi team,
>
> As a function of Scheduling Jobs in EDG, we have a use case for being able to
> view upcoming jobs that are scheduled to run, and viewing the state of
> previously run scheduled job in EDG (using the scheduler/automation
> scripting).
>
> The team let me know there is limited out-of-the-box support for viewing
> previously run and pending scheduling jobs. We wanted to ask if there's
> available guidance on creating these particular views or any examples of
> these views (like a calendar view). If this is possible with a potential tab
> or an 'admin view' to allow inspection of jobs and even including potential
> manipulation of schedules, we'd like some guidance from TQ, and/or pointing
> to to available resources to assist with building these views/functions.
>
> Kind Regards,
>
> Peter
>
> --
> You received this message because you are subscribed to the Google Groups
> "TopBraid Suite Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/6e7a63f3-e1f7-453f-8d7b-d71554463d3cn%40googlegroups.com
>
> <https://groups.google.com/d/msgid/topbraid-users/6e7a63f3-e1f7-453f-8d7b-d71554463d3cn%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/FAFD19AA-8A20-4EF8-8980-ACE2F6F30A09%40topquadrant.com.
