jojotong

@chenshunliang API: `GET /v1/observability/cluster/{cluster}/namespaces/{namespace}/monitor/status?service={exporter_name}` resp is like: ```json { "Message": "ok", "Data": { "discoveredLabels": { "__address__": "192.168.30.18:9187", "__meta_kubernetes_endpoint_address_target_kind": "Pod", "__meta_kubernetes_endpoint_address_target_name": "harbor-postgre-exporter-55588bd898-hvvts", "__meta_kubernetes_endpoint_node_name": "kubegems-develop", "__metrics_path__": "/metrics", "__scheme__": "http", "__scrape_interval__": "30s", "__scrape_timeout__":...

Should copy receiver from `kubegems-default-logging-alert-rule` to exporter's alertmanagerconfig

What do you see when exec: ``` kubectl get plugins.plugins.kubegems.io -n kubegems-logging loki -oyaml ```

We should use image: `docker.io/resmoio/kubernetes-event-exporter:v1.0` And add config: ```yaml kubeQPS: 60 kubeBurst: 60 ```

Because of problem: `starting container process caused "chdir to cwd (\"/home/nonroot\") set in config.json failed: permission denied": unknown` I revert commit: https://github.com/opsgenie/kubernetes-event-exporter/pull/187/commits/f0dc4143c75d049ae1670199e4d48a8d321ed4bc . Then build a new image to resolve,...

60 qps still seems small, maybe scale to 300.

https://github.com/kubernetes/ingress-nginx/blob/f0490cbfbf29a7a05caaac29998dde56173ac2bb/internal/ingress/metric/collectors/nginx_status.go#L83-L104 Maybe we can add a new const label here ?

> httpConfig: {} # we need a new HTTPConfig type, it should be a 1:1 copy of v1alpha1.HTTPConfig For the httpConfig, can I move it's defination to `monitoringv1` package, which...

> I would keep a clear separation between the v1 and v1alpha1 packages for now That's also ok, > I don't have a strong opinion. Drifting from the original Alertmanager...

> Is there any workaround with which we can use custom templates with the new version? We needed the global config but as soon as we upgraded all our alerts...