k8s部署prometheus+grafana+alertmanager

最新推荐文章于 2023-11-05 15:41:24 发布
最新推荐文章于 2023-11-05 15:41:24 发布
阅读量173 收藏
点赞数 1
文章标签： kubernetes prometheus grafana
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_42324368/article/details/132831981
版权

1、创建名称空间

kubectl create ns monitoring

2、创建rbca角色认证

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: prometheus
rules:
- apiGroups: [""]
  resources:
  - nodes
  - nodes/proxy
  - services
  - endpoints
  - pods
  verbs: ["get", "list", "watch"]
- apiGroups:
  - extensions
  resources:
  - ingresses
  verbs: ["get", "list", "watch"]
- nonResourceURLs: ["/metrics"]
  verbs: ["get"]
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: prometheus
  namespace: monitoring
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: prometheus
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: prometheus
subjects:
- kind: ServiceAccount
  name: prometheus
  namespace: monitoring

3、部署prometheus无状态服务，生产环境建议创建为有状态服务

###这里开头编辑了简单的cpu,内存，磁盘告警规则
kind: ConfigMap
apiVersion: v1
metadata:
  name: alert-rules
  namespace: monitoring
data:
  alert-linux.yaml: |-                              
    groups:
    - name: instances
      rules:
      - alert: InstanceDown                  
        expr: up == 0                        
        for: 1m                                                                                                                                                    
        annotations:
          title: 'Instance down'
          description: Instance has been down for more than 1 minute.'
        labels:
          severity: 'critical'
    - name: cpu_alert
      rules:
      - alert: cpu_alert
        expr: 100 -avg(irate(node_cpu_seconds_total{mode="idle"}[1m])) by (instance)* 100 > 80
        for: 5m
        labels:
          level: warning
        annotations:
          description: "instance: {{ $labels.instance }} ,cpu usage is too high ! value: {{$value}}"
          summary:  "cpu usage is too high"
    - name: mem_alert
      rules:
      - alert: mem_alert
        expr: ((node_memory_MemTotal_bytes{instance="$node",job="$job"} - node_memory_MemFree_bytes{instance="$node",job="$job"}) / (node_memory_MemTotal_bytes{instance="$node",job="$job"} )) * 100 > 90
        for: 5m
        labels:
          level: warning
        annotations:
          description: "instance: {{ $labels.instance }} ,memory usage is too high ! value: {{$value}}"
          summary:  "memory usage is too high"
    - name: disk_alert
      rules:
      - alert: disk_alert
        expr: 100 - ((node_filesystem_avail_bytes{instance="$node",job="$job",mountpoint="/",fstype!="rootfs"} * 100) / node_filesystem_size_bytes{instance="$node",job="$job",mountpoint="/",fstype!="rootfs"}) > 85
        for: 5m
        labels:
          level: warning
        annotations:
          description: "instance: {{ $labels.instance }} ,disk usage is too high ! value: {{$value}}"
          summary:  "disk usage is too high"
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: prometheus-config
  namespace: monitoring
data:
  prometheus.yml: |
    global:
      scrape_interval:     15s
      evaluation_interval: 15s
    scrape_configs:
    - job_name: 'kubernetes-cadvisor'
      kubernetes_sd_configs:
      - role: node
      scheme: https
      tls_config:
        ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
      bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
      relabel_configs:
      - action: labelmap
        regex: __meta_kubernetes_node_label_(.+)
      - target_label: __address__
        replacement: kubernetes.default.svc:443
      - source_labels: [__meta_kubernetes_node_name]
        regex: (.+)
        target_label: __metrics_path__
        replacement: /api/v1/nodes/${1}/proxy/metrics/cadvisor
    - job_name: kube-state-metrics
      kubernetes_sd_configs:
      - role: endpoints
        namespaces:
          names:
          - monitoring
      relabel_configs:
      - source_labels: [__meta_kubernetes_service_label_app_kubernetes_io_name]
        regex: kube-state-metrics
        replacement: $1
        action: keep
      - action: labelmap
        regex: __meta_kubernetes_service_label_(.+)
      - source_labels: [__meta_kubernetes_namespace]
        action: replace
        target_label: k8s_namespace
      - source_labels: [__meta_kubernetes_service_name]
        action: replace
        target_label: k8s_sname
    - job_name: node-exporter
      static_configs:
      - targets: ['node-exporter.monitoring.svc.cluster.local:9100']
    alerting:
      alertmanagers:
      - static_configs:
        - targets: ["alertmanager.monitoring.svc.cluster.local:9093"]
    rule_files:
      - /opt/prometheus/*.yaml
---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    name: prometheus
  name: prometheus
  namespace: monitoring
spec:
  replicas: 1
  selector:
    matchLabels:
      app: prometheus
  template:
    metadata:
      labels:
        app: prometheus
    spec:
      containers:
      - image: prom/prometheus:v2.7.1
        name: prometheus
        command:
        - "/bin/prometheus"
        args:
        - "--config.file=/etc/prometheus/prometheus.yml"
        - "--storage.tsdb.path=/prometheus"
        - "--storage.tsdb.retention=24h"
        ports:
        - containerPort: 9090
          protocol: TCP
        volumeMounts:
        - mountPath: "/prometheus"
          name: data
        - mountPath: "/etc/prometheus"
          name: config-volume
        - mountPath: "/opt/prometheus/alert-linux.yaml"
          subPath: alert-linux.yaml
          name: alert
        resources:
          requests:
            cpu: 100m
            memory: 512Mi
          limits:
            cpu: 500m
            memory: 1560Mi
      serviceAccountName: prometheus    
      volumes:
      - name: data
        emptyDir: {}
      - name: config-volume
        configMap:
          name: prometheus-config
      - name: alert
        configMap: 
          name: alert-rules
          items:
          - key: alert-linux.yaml
            path: alert-linux.yaml
---
kind: Service
apiVersion: v1
metadata:
  labels:
    app: prometheus
  name: prometheus
  namespace: monitoring
spec:
  #type: NodePort
  type: ClusterIP
  ports:
  - port: 9090
    targetPort: 9090
    protocol: TCP
    #nodePort: 30003
  selector:
    app: prometheus
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/proxy-body-size: 50m
    nginx.org/client-max-body-size: 100m
    prometheus.io/http-probe: "true"
    prometheus.io/scrape: "true"
  name: prometheus-web
  namespace: monitoring
spec:
  ingressClassName: nginx
  rules:
  - host: prometheus-test.xxx.com
    http:
      paths:
      - backend:
          service:
            name: prometheus
            port:
              number: 9090
        path: /
        pathType: Prefix

4、部署grafana

apiVersion: v1
kind: ConfigMap
metadata:
  name: grafana-cm
  namespace: monitoring
data:
  grafana.ini: |
    [smtp]
    enabled = true
    host = smtp.qq.com:25
    user = xxxx@qq.com
    password = xxxxxx
    skip_verify = true
    from_address = xxxxx@qq.com
    [alerting]
    enabled = true
    execute_alerts = true
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: grafana
  namespace: monitoring
spec:
  replicas: 1
  selector:
    matchLabels:
      app: grafana
  template:
    metadata:
      labels:
        app: grafana
    spec:
      containers:
      - image: grafana/grafana
        imagePullPolicy: IfNotPresent
        securityContext:
          allowPrivilegeEscalation: false
          runAsUser: 0
        name: grafana
        ports:
        - containerPort: 3000
          protocol: TCP
        volumeMounts:
        - mountPath: "/var/lib/grafana"
          name: data
        - mountPath: "/etc/grafana"
          name: grafana-cm
        resources:
          requests:
            cpu: 100m
            memory: 512Mi
          limits:
            cpu: 500m
            memory: 1560Mi
      volumes:
      - name: data
        emptyDir: {}
      - name: grafana-cm
        configMap:
          name: grafana-cm
---
apiVersion: v1
kind: Service
metadata:
  name: grafana
  namespace: monitoring
spec:
  ports:
  - port: 3000
    targetPort: 3000
    protocol: TCP
    #nodePort: 30006
  selector:
    app: grafana
  #type: NodePort
  type: ClusterIP
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/proxy-body-size: 50m
    nginx.org/client-max-body-size: 100m
    prometheus.io/http-probe: "true"
    prometheus.io/scrape: "true"
  name: grafana-web
  namespace: monitoring
spec:
  ingressClassName: nginx
  rules:
  - host: grafana-test.xxx.com
    http:
      paths:
      - backend:
          service:
            name: grafana
            port:
              number: 3000
        path: /
        pathType: Prefix

5、部署alertmanager

kind: ConfigMap
apiVersion: v1
metadata:
  name: alertmanager
  namespace: monitoring
data:
  alertmanager.yml: |-                              
    global:                            
      resolve_timeout: 5m                            
      smtp_smarthost: 'smtp.qq.com:25'              
      smtp_from: 'xxx'              
      smtp_auth_username: 'xxx'              
      smtp_auth_password: 'xxx'        
      smtp_require_tls: false
    route:                                         
      group_by: [alertname]                         
      group_wait: 30s                                
      group_interval: 5m                            
      repeat_interval: 3m                           
      receiver: web.hook
    receivers:
    - name: 'email'                     
      email_configs:                                 
      - to: 'xxx'                    
        send_resolved: true
    - name: 'dingtalk'
      webhook_configs:
      - url: 'https://oapi.dingtalk.com/robot/send?access_token=xxxxxxx'
        send_resolved: true
    receivers:
    - name: 'web.hook'
      webhook_configs:
      ##这里的地址是后面的转发服务的服务地址
      - url: 'http://czhwebhook.monitoring.svc.cluster.local:1994/webhook/sendmsgtowx&key=czj'
    inhibit_rules:
    - source_match:
        severity: 'critical'
      target_match:
        severity: 'warning'
      equal: ['alertname', 'node', 'instance']
---
apiVersion: v1
kind: Service
metadata:
  labels:
    name: altermanager
    kubernetes.io/cluster-service: 'true'
  name: alertmanager
  namespace: monitoring
spec:
  ports:
  - name: alertmanager
    #nodePort: 30007
    port: 9093
    protocol: TCP
    targetPort: 9093
  selector:
    app: altermanager
  sessionAffinity: None
  #type: NodePort
  type: ClusterIP
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/proxy-body-size: 50m
    nginx.org/client-max-body-size: 100m
    prometheus.io/http-probe: "true"
    prometheus.io/scrape: "true"
  name: alertmanager-web
  namespace: monitoring
spec:
  ingressClassName: nginx
  rules:
  - host: alertmanager-test.xxx.com
    http:
      paths:
      - backend:
          service:
            name: altermanager
            port:
              number: 9093
        path: /
        pathType: Prefix

6、我这里是将告警数据发到企业微信机器人，所以写了一个简单的转发告警消息的服务，在

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: czhwebhook
  name: czhwebhook
  namespace: monitoring
spec:
  minReadySeconds: 60
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 5
  selector:
    matchLabels:
      app: czhwebhook
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      labels:
        app: czhwebhook
    spec:
      containers:
      - env:
        - name: wxurl
          value: https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=xxxxxxx
        image: czhwebhook:1.0
        imagePullPolicy: IfNotPresent
        name: czhwebhook
        ports:
        - containerPort: 1994
          name: tcp-1994
          protocol: TCP
        resources:
          limits:
            memory: 256Mi
            cpu: 100m
---
apiVersion: v1
kind: Service
metadata:
  annotations:
    prometheus.io/http-probe: "true"
    prometheus.io/scrape: "true"
  labels:
    app: czhwebhook
  name: czhwebhook
  namespace: monitoring
spec:
  ports:
  - name: tcp-1994
    port: 1994
    protocol: TCP
    targetPort: 1994
  selector:
    app: czhwebhook
  sessionAffinity: None
  type: ClusterIP

查看部署的服务

kubectl get pod,svc,ingress -o wide -n monitoring

NAME                                   READY   STATUS    RESTARTS   AGE   IP                NODE   NOMINATED NODE   READINESS GATES
pod/altermanager-57d56db644-2cdcp      1/1     Running   0          33m   192.168.219.21    k8s3   <none>           <none>
pod/czhwebhook-f9c6df698-2md46         1/1     Running   0          36m   192.168.166.239   k8s1   <none>           <none>
pod/grafana-5f66f54c99-d78r6           1/1     Running   0          23h   192.168.166.235   k8s1   <none>           <none>
pod/kube-state-metrics-cc9968b-5j8zb   1/1     Running   0          23h   192.168.219.19    k8s3   <none>           <none>
pod/node-exporter-4m4q6                1/1     Running   0          23h   192.168.166.237   k8s1   <none>           <none>
pod/node-exporter-ltkpg                1/1     Running   0          23h   192.168.219.20    k8s3   <none>           <none>
pod/node-exporter-vkrp9                1/1     Running   0          23h   192.168.109.106   k8s2   <none>           <none>
pod/prometheus-676f97cd9d-27k8l        1/1     Running   0          23h   192.168.166.238   k8s1   <none>           <none>

NAME                         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE   SELECTOR
service/alertmanager         ClusterIP   10.108.164.2     <none>        9093/TCP            33m   app=altermanager
service/czhwebhook           ClusterIP   10.97.63.161     <none>        1994/TCP            36m   app=czhwebhook
service/grafana              ClusterIP   10.102.252.251   <none>        3000/TCP            23h   app=grafana
service/kube-state-metrics   ClusterIP   None             <none>        8080/TCP,8081/TCP   23h   app.kubernetes.io/name=kube-state-metrics
service/node-exporter        ClusterIP   10.105.96.244    <none>        9100/TCP            23h   k8s-app=node-exporter
service/prometheus           ClusterIP   10.100.196.114   <none>        9090/TCP            23h   app=prometheus

NAME                                         CLASS   HOSTS                           ADDRESS   PORTS   AGE
ingress.networking.k8s.io/alertmanager-web   nginx   alertmanager-test.xxx.com             80      33m
ingress.networking.k8s.io/grafana-web        nginx   grafana-test.xxx.com                  80      23h
ingress.networking.k8s.io/prometheus-web     nginx   prometheus-test.xxx.com               80      23h

部署完成，后续还将配置告警规则及添加节点监控，中间件监控等等

曹david
关注
  • 1
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
k8s部署prometheus+grafana
weixin_40548182的博客
04-28 344
kubelet --version Kubernetes v1.20.2 docker --version Docker version 20.10.2, build 2291f61 cat altermanager-deploy.yaml apiVersion: apps/v1 kind: Deployment metadata: name: alertmanager namespace: kube-system labels: k8s-app: alertmanager
k8s安装prometheus（包含镜像文件、yaml文件、部署方案）
02-27
kubernetes安装prometheus 下载后，解压压缩包，阅读readme.md文件（部署方案）， 上传prometheus-operator.zip至服务器， 根据readme.md方案进行部署， 执行脚本导入prometheus相关镜像， 运行yaml文件，创建prometheus、grafana、node-exporter等相关资源， 修改prometheus、grafana、alertmanager的svc类型为NodePort，并声明暴露的端口 浏览器访问k8s-master的IP:端口， 白屏配置grafana的监控项。 完成部署。
Prometheus，Grafana，exporter，Alertmanager等k8s告警系统一键部署
最新发布
04-11
安装前需保证有正常的k8s环境，适配centos，ubt等，内含readme说明
prometheus监控配置文件.rar
02-19
这是一套K8S方式部署的prometheus监控的配置文件，在K8S+istio的基础上可以直接执行kubectl apply 进行安装，配置文件包含了 prometheus+grafana+alertmanager+钉钉报警的配套配置文件，安装完后可兼容大部分的grafana官方模版，钉钉机器人添加的时候选择安全方式时要选择第二种方式加密。该配置文件需要对k8s有一定了解，需要根据环境修改少量的配置文件，对小白不太友好。
prometheus + alertmanager + grafana +钉钉告警 动部署包
06-29
prometheus + alertmanager + grafana +钉钉告警 动部署包 ，自己写的yaml。创建ns，然后apply拉起来就好了。
Prometheus+Grafana（Kubernetes）企业级监控
06-19
本套课程由浅入深地对Prometheus进行了全方位的介绍，内容通俗易懂，理论与实践相结合。首先从监控体系讲起，介绍了关于监控的各种经典理论和方法。然后循序渐进地介绍了Prometheus的各个功能组件和配置方法，包括监控主机和容器、服务发现、警报管理，以及Kubernetes和运行其上的应用程序的监控。后面讲解了kube-prometheus的详细用法。 主要讲解prometheus、alertmanager的以下几个方面： ?1. Prometheus服务器部署及PromQL的查询及使用案例 ?2. Alertmanager的使用详解 ?3. 常见的日志告警，如邮件、钉钉、微信等 ?4. 在kubernetes中监控的手工部署、应用监控。 ?5. kube-prometheus在Kubernetes的应用，对k8s的各个组件的监控、告警、和对部署在k8s中应用的监控。 注意：本课程学习需要具有一定的Linux基础，网络基础，至少需要您了解网络七层协议，路由等基础知识，并掌握Docker和k8s相关知识点。
k8s集群监控及报警（Prometheus+AlertManager+Grafana+prometheusAlert+Dingding）
weixin_45720992的博客
08-14 2355
k8s集群部署后，急需可靠稳定低延时的集群监控报警系统，报警k8s集群正常有序运行，经过不断调研和测试，最终选择Prometheus+AlertManager+Grafana+prometheusAlert的部署方案，故障信息报警至钉钉群和邮件，如需要额外监控可部署pushgateway主动推送数据到Prometheus进行数据采集。：指定了报警规则所在的位置，prometheus 可以根据这个配置加载规则，用于生成新的时间序列数据或者报警信息，当前我们没有配置任何报警规则。
采用Prometheus+Grafana+Altermanager搭建部署K8S集群节点可视化监控告警平台
宝耶需努力的技术分享博客
06-25 4131
采用 "Prometheus+Grafana"的开源监控系统，安装部署K8S集群监控平台。并使用Altermanager告警插件，配合使用企业微信，实现系统集群监控报警机制。
K8s部署Prometheus+grafana+alertmanager报警监控系统(持续更新)
勇敢的打工人.的博客
01-13 4180
K8s部署Prometheus+grafana+alertmanager报警监控系统
Prometheus接入AlterManager配置邮件告警(基于K8S环境部署)
秦子腾
10-21 1319
2、由于在prometheus中新增了etcd，所以生成一个etcd-certs，这个在部署prometheus需要。1、创建新的Prometheus ConfigMap资源清单，添加监控K8S集群告警规则。1、创建AlterManager ConfigMap资源清单。2、创建AlterManager SVC资源。1、创建deployment资源。2、配置文件核心配置说明。文章之上做本次实验。
K8S监控（Prometheus+Grafana+alertmanager+钉钉机器人告警）部署方案
boy3363900的博客
10-17 916
架构就不细讲，网上一大堆都大同小异，但是自己在部署的过程中发现踩了很多坑，记录一下整个部署过程，开干！一、部署K8S集群资源数据采集组件：kube-state-metrics需要注意的是镜像k8s.gcr.io/kube-state-metrics/kube-state-metrics:v2.3.0这个国内无法下载，需要通过国内源下载，然后tag打包push到自己的私有仓库docker tag 更换仓库地址docker push 镜像。
基于prometheus+alertmanager+grafana的kubernetes监控告警方案
zhangper的博客
09-14 929
基于prometheus+alertmanager+grafana的kubernetes监控告警方案
进阶之路：从零到一在k8s上部署高可用prometheus —— alertmanager
ary的博客
08-03 888
目录导航前言相关yaml文件权限相关alertmanager-serviceAccount.yaml配置相关alertmanager-secret.yaml服务相关alertmanager-service.yamlprometheus.yaml部署验证 导航 进阶之路：从零到一在k8s上部署高可用prometheus —— 总览 前言 在上一章部署完监控基础组件prometheus后，我们应该已经可以采集到node_exporter暴露出的监控数据了。但是仅仅有数据是不够的，我们需要将数据转化为可以利用的资
Prometheus K8S中部署Alertmanager
weixin_30876945的博客
08-30 711
Prometheus K8S中部署Alertmanager 设置告警和通知的主要步骤如下：一、部署Alertmanager二、配置Prometheus与Alertmanager通信三、配置告警　　1. prometheus指定rules目录　　2. configmap存储告警规则　　3. configmap挂载到容器rules目录 一、部署Alertmanager 配置文件 ...
Prometheus接入AlterManager配置企业微信告警(基于K8S环境部署)
秦子腾
11-05 2315
如上图可以看到，Prometheus的告警信息已经发到AlterManager了，AlertManager收到报警数据后，会将警报信息进行分组，然后根据AlertManager配置的。2、由于在prometheus中新增了etcd，所以生成一个etcd-certs，这个在部署prometheus需要。1、创建新的Prometheus ConfigMap资源清单，添加监控K8S集群告警规则。1、创建AlterManager ConfigMap资源清单。如上图，告警信息已经成功发往企业微信了！
k8s全栈-笔记6-Prometheus+Alertmanager构建监控系统
llllyh812的博客
10-03 2275
k8s全栈-笔记6-Prometheus+Alertmanager构建监控系统
外独立部署Prometheus+Grafana+Alertmanager监控K8S
听海归雪的博客
12-06 7117
集群外独立Prometheus+Grafana+Alertmanager服务监控k8s资源
alertmanager 告警写入kafka 及 k8s 部署prometheus alertmanager
qq_15138049的博客
01-11 873
prometheus alertmanager
【k8s】基于Prometheus监控Kubernetes集群安装部署
2302_77582029的博客
08-16 3400
【k8s】基于Prometheus监控Kubernetes集群安装部署
k8s部署prometheus + grafana+alert
06-03
这是一个比较复杂的问题，需要详细说明。我会尽可能地给您提供一些指导。 首先，您需要了解一些基础知识，如 Kubernetes 和 Prometheus。Kubernetes 是一个容器编排平台，可以帮助您自动管理多个容器应用程序的部署、扩展和故障恢复。Prometheus 是一个开源的监控系统，可以收集和存储应用程序的指标，并支持告警和可视化。 以下是大致的步骤： 1. 部署 Kubernetes 集群，并准备好部署 Prometheus 和 Grafana 的节点。您可以使用各种 Kubernetes 发行版，如 kops、kubeadm 等。 2. 安装和配置 Prometheus。您可以使用 Prometheus 的 Helm Chart 进行部署，并通过 Prometheus Operator 进行管理。在部署 Prometheus 时，您需要配置它来收集应用程序的指标，并将其存储在 Prometheus 存储中。 3. 部署 Grafana。您可以使用 Grafana 的 Helm Chart 进行部署，并配置它来连接到 Prometheus 存储。在 Grafana 中，您可以创建仪表板并可视化 Prometheus 存储中的指标数据。 4. 配置告警。您可以使用 Prometheus 的 Alertmanager 进行告警，并将告警发送到 Slack、Email 等渠道。在配置告警时，您需要定义告警规则，并配置 Alertmanager 来发送告警。 以上是部署 Prometheus、Grafana 和告警的大致步骤。由于每个环境的部署和配置都有所不同，所以具体的细节可能会有所不同。我建议您查阅官方文档，并根据您的需求进行调整。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值