Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Asimov Asimov
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Asimov
  • AsimovAsimov
  • Merge requests
  • !36

New log collector

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Daniel Williams requested to merge 14-improve-logging-and-error-messages into review Jan 20, 2022
  • Overview 0
  • Commits 4
  • Pipelines 4
  • Changes 7

What?

Asimov is capable both of generating its own events, log messages, and errors, but is also responsible for monitoring third-party scripts for runtime events.

This merge request intends to implement a new interface for logging events both within the asimov code and within those external programs, so that they can be reported for each individual run and event being analysed.

Why?

In order to maintain flexibility, and so that asimov can run in both "multi-user" and single user modes, the back-end should be capable of using either a performant database engine, or a local database such as sqlite. For smaller projects a normal log file can also be used.

How?

The collector will run as a small server process which will receive log messages as POST requests containing the message, GW event, production name, pipeline and sub-pipeline details, time, and username. The server will allow events to be retrieved for each GW-event, filtered by pipeline and other columns.

Who?

This work was done by Daniel Williams (daniel.williams@ligo.org)

Checklist

  • New code
  • Tests
  • Documentation & examples
  • Release target

Notes

Closes #14

Edited Feb 21, 2022 by Daniel Williams
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: 14-improve-logging-and-error-messages