Adds mosquito api for Executors #147
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mosquito::Apiis a new module designed to facilitate visibility into a running mosquito cluster. This is the first member class of the module, and it allows inspecting a single executor by ID.The
Mosquito::Apiis a read-only interface. For an existentRunner::Executor, the API allows querying:#current_job- the job run id that the executor is currently working on#current_job_queue- the queue which held the job run#last_heartbeat- a timestamp which was last updated when the executor finished a job run.The
Runner::Executorchecks in with the API through an interface calledObservability::Executor, which is the write interface paired with the API.