kandi background
Explore Kits

paascloud-master | spring cloud | Microservice library

 by   paascloud Java Version: Current License: Apache-2.0

 by   paascloud Java Version: Current License: Apache-2.0

Download this library from

kandi X-RAY | paascloud-master Summary

paascloud-master is a Java library typically used in Architecture, Microservice, Vue, Spring Boot applications. paascloud-master 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.
spring cloud + vue + oAuth2.0全家桶实战,前后端分离模拟商城,完整的购物流程、后端运营平台,可以实现快速搭建企业级微服务项目。支持微信登录等三方登录。
Support
Support
Quality
Quality
Security
Security
License
License
Reuse
Reuse

kandi-support Support

  • paascloud-master has a medium active ecosystem.
  • It has 9259 star(s) with 4288 fork(s). There are 516 watchers for this library.
  • It had no major release in the last 12 months.
  • There are 81 open issues and 42 have been closed. On average issues are closed in 68 days. There are 11 open pull requests and 0 closed requests.
  • It has a neutral sentiment in the developer community.
  • The latest version of paascloud-master is current.
paascloud-master Support
Best in #Microservice
Average in #Microservice
paascloud-master Support
Best in #Microservice
Average in #Microservice

quality kandi Quality

  • paascloud-master has 0 bugs and 0 code smells.
paascloud-master Quality
Best in #Microservice
Average in #Microservice
paascloud-master Quality
Best in #Microservice
Average in #Microservice

securitySecurity

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

license License

  • paascloud-master 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.
paascloud-master License
Best in #Microservice
Average in #Microservice
paascloud-master License
Best in #Microservice
Average in #Microservice

buildReuse

  • paascloud-master releases are not available. You will need to build from source code and install.
  • Build file is available. You can build the component from source.
  • Installation instructions are not available. Examples and code snippets are available.
paascloud-master Reuse
Best in #Microservice
Average in #Microservice
paascloud-master Reuse
Best in #Microservice
Average in #Microservice
Top functions reviewed by kandi - BETA

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

  • Parses order details
  • update uac group status
  • bindUserRoles
  • Process job data .
  • Get cartVo
  • bind user to role
  • Handle log .
  • Assemble product detailVo .
  • Check bot message .
  • Handle a child event .

paascloud-master Key Features

spring cloud + vue + oAuth2.0全家桶实战,前后端分离模拟商城,完整的购物流程、后端运营平台,可以实现快速搭建企业级微服务项目。支持微信登录等三方登录。

项目介绍

copy iconCopydownload iconDownload
功能点:
    模拟商城,完整的购物流程、后端运营平台对前端业务的支撑,和对项目的运维,有各项的监控指标和运维指标。
技术点:
       核心技术为springcloud+vue两个全家桶实现,采取了取自开源用于开源的目标,所以能用开源绝不用收费框架,整体技术栈只有
    阿里云短信服务是收费的,都是目前java前瞻性的框架,可以为中小企业解决微服务架构难题,可以帮助企业快速建站。由于服务
    器成本较高,尽量降低开发成本的原则,本项目由10个后端项目和3个前端项目共同组成。真正实现了基于RBAC、jwt和oauth2的
    无状态统一权限认证的解决方案,实现了异常和日志的统一管理,实现了MQ落地保证100%到达的解决方案。
	
	核心框架:springcloud Edgware全家桶
	安全框架:Spring Security Spring Cloud Oauth2
	分布式任务调度:elastic-job
	持久层框架:MyBatis、通用Mapper4、Mybatis_PageHelper
	数据库连接池:Alibaba Druid
	日志管理:Logback	前端框架:Vue全家桶以及相关组件
	三方服务: 邮件服务、阿里云短信服务、七牛云文件服务、钉钉机器人服务、高德地图API

平台目录结构说明

copy iconCopydownload iconDownload
├─paascloud-master----------------------------父项目,公共依赖
│  │
│  ├─paascloud-eureka--------------------------微服务注册中心
│  │
│  ├─paascloud-discovery-----------------------微服务配置中心
│  │
│  ├─paascloud-monitor-------------------------微服务监控中心
│  │
│  ├─paascloud-zipkin--------------------------微服务日志采集中心
│  │
│  ├─paascloud-gateway--------------------------微服务网关中心
│  │
│  ├─paascloud-provider
│  │  │
│  │  ├─paascloud-provider-mdc------------------数据服务中心
│  │  │
│  │  ├─paascloud-provider-omc------------------订单服务中心
│  │  │
│  │  ├─paascloud-provider-opc------------------对接服务中心
│  │  │
│  │  ├─paascloud-provider-tpc------------------任务服务中心
│  │  │
│  │  └─paascloud-provider-uac------------------用户服务中心
│  │
│  ├─paascloud-provider-api
│  │  │
│  │  ├─paascloud-provider-mdc-api------------------数据服务中心API
│  │  │
│  │  ├─paascloud-provider-omc-api------------------订单服务中心API
│  │  │
│  │  ├─paascloud-provider-opc-api------------------对接服务中心API
│  │  │
│  │  ├─paascloud-provider-tpc-api------------------任务服务中心API
│  │  │
│  │  ├─paascloud-provider-sdk-api------------------可靠消息服务API
│  │  │
│  │  └─paascloud-provider-uac-api------------------用户服务中心API
│  │
│  ├─paascloud-common
│  │  │
│  │  ├─paascloud-common-base------------------公共POJO基础包
│  │  │
│  │  ├─paascloud-common-config------------------公共配置包
│  │  │
│  │  ├─paascloud-common-core------------------微服务核心依赖包
│  │  │
│  │  ├─paascloud-common-util------------------公共工具包
│  │  │
│  │  ├─paascloud-common-zk------------------zookeeper配置
│  │  │
│  │  ├─paascloud-security-app------------------公共无状态安全认证
│  │  │
│  │  ├─paascloud-security-core------------------安全服务核心包
│  │  │
│  │  └─paascloud-security-feign------------------基于auth2的feign配置
│  │
│  ├─paascloud-generator
│  │  │
│  │  ├─paascloud-generator-mdc------------------数据服务中心Mybatis Generator
│  │  │
│  │  ├─paascloud-generator-omc------------------数据服务中心Mybatis Generator
│  │  │
│  │  ├─paascloud-generator-opc------------------数据服务中心Mybatis Generator
│  │  │
│  │  ├─paascloud-generator-tpc------------------数据服务中心Mybatis Generator
│  │  │
│  │  └─paascloud-generator-uac------------------数据服务中心Mybatis Generator




特殊说明

copy iconCopydownload iconDownload
这里做一个解释由于微服务的拆分受制于服务器,这里我做了微服务的合并,比如OAuth2的认证服务中心和用户中心合并,
统一的one service服务中心和用户认证中心合并,支付中心和订单中心合并,其实这也是不得已而为之,
只是做了业务微服务中心的合并,并没有将架构中的 注册中心 监控中心 服务发现中心进行合并。

作者介绍

copy iconCopydownload iconDownload
Spring Cloud 爱好者,现就任于鲜易供应链平台研发部.

配套项目

copy iconCopydownload iconDownload
后端项目:https://github.com/paascloud/paascloud-master 
         https://gitee.com/paascloud/paascloud-master
登录入口:https://github.com/paascloud/paascloud-login-web
         https://gitee.com/paascloud/paascloud-login-web
后端入口:https://github.com/paascloud/paascloud-admin-web
         https://gitee.com/paascloud/paascloud-admin-web
前端入口:https://github.com/paascloud/paascloud-mall-web
         https://gitee.com/paascloud/paascloud-mall-web

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 paascloud-master

You can download it from GitHub.
You can use paascloud-master 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 paascloud-master 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

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

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
Try Top Libraries by paascloud
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.