ScrapeInterval not set in VMScrapeConfig?

[a-bali]

I have the following ScrapeConfig:

apiVersion: monitoring.coreos.com/v1alpha1
kind: ScrapeConfig
metadata:
  name: foo
spec:
  scrapeInterval: 30m
  staticConfigs:
    - labels:
        job: external-monitoring
      targets:
        - "http://foo/metrics"

And the VMScrapeConfig generated by vm-operator is missing the scrape interval (I suppose it should have spec.interval set from spec.scrapeInterval), why is this?

apiVersion: operator.victoriametrics.com/v1beta1
kind: VMScrapeConfig
metadata:
  annotations:
  creationTimestamp: "2025-11-28T08:29:13Z"
  generation: 1
  name: foo
  namespace: monitoring
  resourceVersion: "12936439"
  uid: 97f97b43-55ca-47a4-85fb-5693dcb75ddc
spec:
  staticConfigs:
  - labels:
      job: external-monitoring
    targets:
    - http://foo/metrics
status:
  conditions:
  - lastTransitionTime: "2025-11-28T08:29:13Z"
    lastUpdateTime: "2025-11-28T08:29:13Z"
    observedGeneration: 1
    reason: ConfigParsedAndApplied
    status: "True"
    type: vm.victoriametrics.vmagent.victoriametrics.com/Applied
  observedGeneration: 1
  updateStatus: operational

[AndrewChubatiuk]

it should be scrape_interval, not scrapeInterval

[a-bali]

It is scrapeInterval according to the CRD.

[AndrewChubatiuk]

your link points to prometheus operator CRDs, VM operator CRDs are here

[a-bali]

But then, I have a valid ScrapeConfig as per the Prometheus CRD. I would expect vm-operator to generate a valid VMScrapeConfig, which it does, but it skips the scrapeInterval source field. And it should create a scrape_interval target field.

[AndrewChubatiuk]

yes, that's a bug, will add a PR with a fix soon

[AndrewChubatiuk]

fix is available in operator v0.66.0 and released in helm chart 0.57.0