The metrics collected by prometheus are not continuous

[vitaaaaa1]

I turned on the configuration of prometheus collection metrics when installing vault with helm

server.standalone.config:
config: |-
      ui = true

      listener "tcp" {
        tls_disable = 1
        address = "[::]:8200"
        cluster_address = "[::]:8201"
        # Enable unauthenticated metrics access (necessary for Prometheus Operator)
        telemetry {
          unauthenticated_metrics_access = "true"
        }
      }
      storage "file" {
        path = "/vault/data"
      }

      # Example configuration for using auto-unseal, using Google Cloud KMS. The
      # GKMS keys must already exist, and the cluster must have a service account
      # that is authorized to access GCP KMS.
      #seal "gcpckms" {
      #   project     = "vault-helm-dev"
      #   region      = "global"
      #   key_ring    = "vault-helm-unseal-kr"
      #   crypto_key  = "vault-helm-unseal-key"
      #}

      # Example configuration for enabling Prometheus metrics in your config.
      telemetry {
        prometheus_retention_time = "30s"
        disable_hostname = true
      }

The serviceMonitor option is set to true

serverTelemetry.serviceMonitor.enabled: ture
serverTelemetry.serviceMonitor.interval: 30s
serverTelemetry.serviceMonitor.scrapeTimeout: 10s

prometheus is now collecting data normally, but the metrics are not continuous, which is strange

The data is not continuous

This causes the Federated Center to collect this prometheus instance without getting data, and I wonder if this is a configuration issue or if the vault exposed metrics are inherently intermittent