Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metadig Engine Quality Report Process Diagram #455

Open
doulikecookiedough opened this issue Jan 7, 2025 · 1 comment
Open

Metadig Engine Quality Report Process Diagram #455

doulikecookiedough opened this issue Jan 7, 2025 · 1 comment
Assignees

Comments

@doulikecookiedough
Copy link

The existing process for how a quality report is processed is a little vague, along with the actual required parameters (ex. QueueEntry and what is being utilized/parsed).

Create a process diagram to assist with forming a road map and steps for the changes necessary to fully integrate HashStore into all quality reports, not just the data.suite quality report.

The diagram to use as a base can be found here (Monitoring for stuck jobs):

@doulikecookiedough
Copy link
Author

qreprocess
ZenUML for Request Report Submission Process
zenuml
    title Quality Report Execution Process
    Client->RequestReport."Request Report"{
        execute()
        getPidsToProcess()
    }
    RequestReport->Controller.submitReportRequest(){
        processQualityRequest
        "qEntry = new QueueEntry(...)"
        writeInProcessChannel(message)
    }
    // Sends a message to the
    // RMQ Quality Queue
    Controller->RMQQualityQueue.basicPublish(){}

    // Retrieves a message
    Worker->RMQQualityQueue.basicConsume(){}
    //
    Worker->Worker.handleDelivery() {
        // Remove message from queue
        Worker->RMQQualityQueue.basicAck()
        // Create the quality report
        "run = wkr.processReport(qEntry)"
        // Confirm run
        "run.save()"
        Worker.returnReport() {
            .writeCompletedQueue(message);
        }
    }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant