Tracking issue for PD own service self-protection

[CabinfeverB]

Enhancement

This issue is tracking PD's own service self-protection mechanism.

The self-protection mechanism (refer to #4373) consists of two parts the standard use of etcd and the own service of PD itself. PD provides services for other components in two ways: HTTP API and gRPC. But now PD provides gRPC service by embedding etcd which is lack of a method to use gRPC interceptor, so we will support HTTP self-protection firstly.

We will develop two features to implement the self-protection mechanism. Such as k8s, hold a handler chain to process middleware. So PD will hold the rate limit handler and auditing handler. To gather some information used by the above handlers, it will also hold an information-gathering handler.

Subtasks

• Implementing the information-gathering handler
  • Add HTTP Component Signature #4490
  • Support to Get real HTTP Client IP #4494
  • Support Gather http.Request info  #4538
  • Get All defined Service labels  #4681
• Support HTTP QPS rate limit
  • Add HTTP rate limit middleware #4666
  • Implement QPS rate limiter #4500
• Support HTTP audit
  • Implement Audit Middleware #4601
  • Support local log for Audit #4602
  • Support HTTP audit using prometheus histogram metrics #4608
• Config
  • Persistent Audit switch config #4761
  • config, api: Add Service Config #4869
• Let other components add component header
• Edit docs

TODO

• support gRPC self-protection

[CabinfeverB]

/assign

[lhy1024]

@CabinfeverB Can we close it?

[CabinfeverB]

Closed since most tasks has been finished.