-
Notifications
You must be signed in to change notification settings - Fork 27
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
feat: add prometheus metrics #572
Merged
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
89433a8
to
dba7773
Compare
Signed-off-by: Sacha Froment <[email protected]>
11ab460
to
a347d29
Compare
Flamegraph.com reportCreated by Flamegraph.com Github Action |
Coverage Report
File Coverage
|
Signed-off-by: Sacha Froment <[email protected]>
a347d29
to
70de130
Compare
Signed-off-by: Sacha Froment <[email protected]>
* origin: style: 🎨 allow printWidth 120 (#596) fix: use the correct obj (#595) Feat: interval drp reconnect bootstrap (#579) fix(interval-discovery)!: now use a != topic in order not to have many invalid operation logs (#589) feat!: restrict set key access (#582) fix: log_config pass down to disco interval (#590) feat(object): drpobject become generic (#565) chore(deps): bump @opentelemetry/sdk-trace-web from 1.30.1 to 2.0.0 (#585) fix!: testcase handle sync message correctly (#588) feat: expose the peerId that created the operations (#551) Fix: testcase incorrect (#557) chore(deps-dev): bump eslint-import-resolver-typescript from 3.8.7 to 4.2.0 (#583) fix: add log config to createObject option to be passed down to finality store (#574) feat: add logger template (#576)
* origin: fix: wait for ACL (#578)
Signed-off-by: Sacha Froment <[email protected]>
c95e828
to
f1efb55
Compare
JanLewDev
approved these changes
Mar 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
anhnd350309
approved these changes
Mar 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
trungnotchung
approved these changes
Mar 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
e1b89be
to
9a9a6f9
Compare
Signed-off-by: Sacha Froment <[email protected]>
Signed-off-by: Sacha Froment <[email protected]>
…heus-metrics * origin: fix: remove duplicate bench (#603) * main: fix: remove duplicate bench
sfroment
added a commit
that referenced
this pull request
Mar 22, 2025
* origin: feat: add prometheus metrics (#572)
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.
What type of PR is this?
Add prometheus gossip sub metrics
Description
Implment the gossip sub metrics register to work with prometheus
Related Issues and PRs
Added/updated tests?
Additional Info
add instructions or screenshots on what you might think is relevant or instructions on how to manually test it
[optional] Do we need to perform any post-deployment tasks?