Tracking Reliability - Sai #76
Draft
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Started the code for tracking reliability. Right now, I basically just collect all the loki logs, then based on that, calculate their response time, if they are accessible, etc. And based on this, it outputs the report on the things that loki is logging.
Right now, I still need to refactor the code and cut down where it needs it. Also, I am not able to test it because I am running into some errors with docker-compose that I put in the Thingweb group chat. I made this pr to show the status of where I am and having incremental PRs as requested.
To run the code, simply go to the monitoring/loki-analyzer directory and do npm start.