Closed
Conversation
…tead of panicking and let the user deal with the consequences (#9)
* feat: add option for enabling websocket compression * feat: add option for enabling websocket compression on the client * docs: add compression docs
* Added OCPP configuration manager * docs: update
* Added ocppj and websocket server metrics * Added metrics support to examples and observability stack * Added commands to run the observability with examples in makefile * Added context with expiry for metrics * Added notes * Added error log if websocket metrics arent initialized properly * Added readme instructions on configuring and testing observability * docs: add observability setup instructions * fix: typos * feat: additional websocket metrics * feat: additional ocpp server metrics - request queue size * chore: add tests for new functions * chore: rename struct * chore: rename method * feat: add errors for metrics * feat: add dispatcher metrics
* Added ocppj and websocket server metrics * Added context with expiry for metrics * feat: additional ocpp server metrics - request queue size * chore: rename method * feat: add pyroscope to observability * feat: add pyroscope integration to examples * chore: remove pyroscope, as it is already included in newest LGTM stack image * fix: simulator profiling fixes * feat: added k6 and profiling for ocpp system * feat(wip): Performance tests * fix: typo * feat: adjust example metric interval to be able to sample high frequency reconnects * fix: support for multiple profiles
* feat: k6 runs on CI * fix: making the examples thread-safe * fix: ci * Apply automatic changes * fix: PR comment * fix: PR comment action
* feat: make validation atomic * fix: make html escaping atomic
* chore: use suite assertions instead of package assertions * Apply automatic changes
* chore: add tests for ocpp package, made features package-private. They should only be retrieved/manipulated via methods. * chore: add ocpp to coverage * Apply automatic changes
* fix: tests * chore: unify ci and local test runs
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.
Proposed changes
Types of changes
What types of changes does your code introduce?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any ofthem, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.