Skip to content

ScrapeInterval not set in VMScrapeConfig? #1645

@a-bali

Description

@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 

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions