kandi background
Explore Kits

hmily | Distributed transaction solutions | Microservice library

 by   dromara Java Version: Current License: Apache-2.0

 by   dromara Java Version: Current License: Apache-2.0

Download this library from

kandi X-RAY | hmily Summary

hmily is a Java library typically used in Architecture, Microservice, Spring Boot, Spring applications. hmily has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has medium support. You can download it from GitHub, Maven.
high reliability :supports abnormal transaction rollback in distributed scenarios, and abnormal recovery over time to prevent transaction suspension. usability :provide zero-invasive Spring-Boot, Spring-Namespace to quickly integrate with business systems. high performance :decentralized design, fully integrated with business systems, naturally supporting cluster deployment. observability :metrics performance monitoring of multiple indicators, and admin management background UI display. various RPC : support Dubbo, SpringCloud, Motan, Sofa-rpc, brpc, tars and other well-known RPC frameworks. log storage : support mysql, oracle, mongodb, redis, zookeeper etc. complex scene : support RPC nested call transaction.
Support
Support
Quality
Quality
Security
Security
License
License
Reuse
Reuse

kandi-support Support

  • hmily has a medium active ecosystem.
  • It has 3696 star(s) with 1344 fork(s). There are 258 watchers for this library.
  • It had no major release in the last 12 months.
  • There are 18 open issues and 133 have been closed. On average issues are closed in 13 days. There are no pull requests.
  • It has a neutral sentiment in the developer community.
  • The latest version of hmily is current.
hmily Support
Best in #Microservice
Average in #Microservice
hmily Support
Best in #Microservice
Average in #Microservice

quality kandi Quality

  • hmily has 0 bugs and 0 code smells.
hmily Quality
Best in #Microservice
Average in #Microservice
hmily Quality
Best in #Microservice
Average in #Microservice

securitySecurity

  • hmily has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
  • hmily code analysis shows 0 unresolved vulnerabilities.
  • There are 0 security hotspots that need review.
hmily Security
Best in #Microservice
Average in #Microservice
hmily Security
Best in #Microservice
Average in #Microservice

license License

  • hmily is licensed under the Apache-2.0 License. This license is Permissive.
  • Permissive licenses have the least restrictions, and you can use them in most projects.
hmily License
Best in #Microservice
Average in #Microservice
hmily License
Best in #Microservice
Average in #Microservice

buildReuse

  • hmily releases are not available. You will need to build from source code and install.
  • Deployable package is available in Maven.
  • Build file is available. You can build the component from source.
hmily Reuse
Best in #Microservice
Average in #Microservice
hmily Reuse
Best in #Microservice
Average in #Microservice
Top functions reviewed by kandi - BETA

kandi has reviewed hmily and discovered the below as its top functions. This is intended to give you an instant insight into hmily implemented functionality, and help decide if they suit your requirements.

  • Prepare prepare .
  • Intercept a method call .
  • Checks if method is annotated in Hars .
  • Gets version info from the given class .
  • Build connection pool .
  • Intercept the method invocation .
  • Get the invoker .
  • Initialize curator factory .
  • Dispatches event .
  • Performs a method invocation .

hmily Key Features

high reliability :supports abnormal transaction rollback in distributed scenarios, and abnormal recovery over time to prevent transaction suspension

usability :provide zero-invasive Spring-Boot, Spring-Namespace to quickly integrate with business systems

high performance :decentralized design, fully integrated with business systems, naturally supporting cluster deployment

observability :metrics performance monitoring of multiple indicators, and admin management background UI display

various RPC : support Dubbo, SpringCloud, Motan, Sofa-rpc, brpc, tars and other well-known RPC frameworks

log storage : support mysql, oracle, mongodb, redis, zookeeper etc.

complex scene : support RPC nested call transaction

Community Discussions

Trending Discussions on Microservice
  • Exclude Logs from Datadog Ingestion
  • Custom Serilog sink with injection?
  • How to manage Google Cloud credentials for local development
  • using webclient to call the grapql mutation API in spring boot
  • Jdeps Module java.annotation not found
  • How to make a Spring Boot application quit on tomcat failure
  • Deadlock on insert/select
  • Rewrite host and port for outgoing request of a pod in an Istio Mesh
  • Checking list of conditions on API data
  • Traefik v2 reverse proxy without Docker
Trending Discussions on Microservice

QUESTION

Exclude Logs from Datadog Ingestion

Asked 2022-Mar-19 at 22:38

I have a kubernetes cluster that's running datadog and some microservices. Each microservice makes healthchecks every 5 seconds to make sure the service is up and running. I want to exclude these healthcheck logs from being ingested into Datadog.

I think I need to use log_processing_rules and I've tried that but the healthcheck logs are still making it into the logs section of Datadog. My current Deployment looks like this:

apiVersion: apps/v1
kind: Deployment
[ ... SNIP ... ]
spec:
  replicas: 2
  selector:
    matchLabels:
      app: my-service
  template:
    metadata:
      labels:
        app: my-service
        version: "fac8fb13"
      annotations:
        rollme: "IO2ad"
        tags.datadoghq.com/env: development
        tags.datadoghq.com/version: "fac8fb13"
        tags.datadoghq.com/service: my-service
        tags.datadoghq.com/my-service.logs: |
          [{
            "source": my-service,
            "service": my-service,
            "log_processing_rules": [
              {
                "type": "exclude_at_match",
                "name": "exclude_healthcheck_logs",
                "pattern": "\"RequestPath\": \"\/health\""
              }
            ]
          }]

and the logs coming out of the kubernetes pod:

$ kubectl logs my-service-pod

{
  "@t": "2022-01-07T19:13:05.3134483Z",
  "@m": "Request finished HTTP/1.1 GET http://10.64.0.80:5000/health - - - 200 - text/plain 7.5992ms",
  "@i": "REDACTED",
  "ElapsedMilliseconds": 7.5992,
  "StatusCode": 200,
  "ContentType": "text/plain",
  "ContentLength": null,
  "Protocol": "HTTP/1.1",
  "Method": "GET",
  "Scheme": "http",
  "Host": "10.64.0.80:5000",
  "PathBase": "",
  "Path": "/health",
  "QueryString": "",
  "HostingRequestFinishedLog": "Request finished HTTP/1.1 GET http://10.64.0.80:5000/health - - - 200 - text/plain 7.5992ms",
  "EventId": {
    "Id": 2,
    "Name": "RequestFinished"
  },
  "SourceContext": "Microsoft.AspNetCore.Hosting.Diagnostics",
  "RequestId": "REDACTED",
  "RequestPath": "/health",
  "ConnectionId": "REDACTED",
  "dd_service": "my-service",
  "dd_version": "54aae2b5",
  "dd_env": "development",
  "dd_trace_id": "REDACTED",
  "dd_span_id": "REDACTED"
}

EDIT: Removed 2nd element of the log_processing_rules array above as I've tried with 1 and 2 elements in the rules array.

EDIT2: I've also tried changing log_processing_rules type to INCLUDE at match in an attempt to figure this out:

"log_processing_rules": [
  {
    "type": "include_at_match",
    "name": "testing_include_at_match",
    "pattern": "somepath"
  }
]

and I'm still getting the health logs in Datadog (in theory I should not as /health is not part of the matching pattern)

ANSWER

Answered 2022-Jan-12 at 20:28

I think the problem is that you're defining multiple patterns; the docs state, If you want to match one or more patterns you must define them in a single expression.

Try somtething like this and see what happens:

"log_processing_rules": [
  {
    "type": "exclude_at_match",
    "name": "exclude_healthcheck_logs",
    "pattern": "\/health|\"RequestPath\": \"\/health\""
  }

Source https://stackoverflow.com/questions/70687054

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install hmily

You can download it from GitHub, Maven.
You can use hmily like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the hmily component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

If you want to use it, you can refer to Quick Start.

DOWNLOAD this Library from

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 430 million Knowledge Items
Find more libraries
Reuse Solution Kits and Libraries Curated by Popular Use Cases

Save this library and start creating your kit

Share this Page

share link
Consider Popular Microservice Libraries
Compare Microservice Libraries with Highest Support
Compare Microservice Libraries with Highest Security
Compare Microservice Libraries with Permissive License
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 430 million Knowledge Items
Find more libraries
Reuse Solution Kits and Libraries Curated by Popular Use Cases

Save this library and start creating your kit

  • © 2022 Open Weaver Inc.