Feature release - initial version of metrics #574
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
Initial implementation for transaction handling. Verified and extended the original concept of using JFR for metrics.
Initial implementation for transaction handling. Verified and extended the original concept of using JFR for metrics.
Initial implementation for transaction handling. Verified and extended the original concept of using JFR for metrics.
Observability is better wording for this part fo documentation.
Added basis of storage events. Made ReadOnlyHandle closeable and trying to consistently close it.
Observability is better wording for this part fo documentation.
Added monitoring of non-flushed data in OffsetIndexes.
Implemented transactional and storage metrics.
# Conflicts: # evita_external_api/evita_external_api_observability/src/main/java/io/evitadb/externalApi/observability/metric/provider/CustomEventProvider.java # evita_functional_tests/src/test/java/io/evitadb/utils/FileUtilsTest.java # evita_functional_tests/src/test/java/io/evitadb/utils/ReflectionLookupTest.java
Finalized query metrics.
Finalized session metrics.
Finalized session metrics.
Finalized background tasks and evitaDB start
Cache metrics done.
gRPC metrics done.
feat(#18): metrics
Corrected metrics name and initialization process.
Handle NULL labels safely.
Metrics finalization.
NPE fixes.
Also corrected the memory calculation.
Also defined better default bucket count for Histograms.
Also upgraded Undertow and XNIO to latest version to avoid security problems.
…hing-with-exception fix(#572): NullPointerException in transactional stage
…o EvitaStart event
…o EvitaStart event
Unfortunately, Prometheus doesn't propagate native histograms in text format - see prometheus/prometheus#11265, only in Protobuff format, and this is not easily scrapeable.
It seems that the re-scheduling initiated an invocation storm (according to metrics). Tests added, logic tested and introduced minimal gap to avoid those storms.
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.
No description provided.