In this version, we added another way to monitor your jobs. Status information on jobs is already available in multiple ways (via the Studio, email notification, or by processing SYSLOG tables in 3rd party tools). Based on feedback from customers using an ELK stack (Elasticsearch, Logstash, Kibana) we now also added job status changes to the server.log:
15:45:35,048 ERROR [JOB_STATUS_LOGGER] (teiid-async-threads - 1) Job id: 53, Job status: INTERRUPTED, Description: SELECT * FROM "neo4j_views.neo4j_mssql_join"
15:57:27,053 INFO [JOB_STATUS_LOGGER] (QuartzScheduler_Worker-10) Job id: 32770, Job status: SUCCESS, Description: SELECT * FROM "demo.mssql_as400_join"
Whenever a job terminates, a log entry is produced. Based on the result, the log level is adjusted accordingly (INFO or ERROR). This allows tracking whether certain jobs succeed or were executed on time which can be used for operational purposes.
- DVCORE-6681 (Improvement): Remove HTTP Basic Authentication for the main landing page
- DVCORE-6712: Update the email in the License window
- DVCORE-6645 (Improvement): Log job status changes to the server log
Please sign in to leave a comment.