2023-10-05 12:43:28 +02:00
|
|
|
---
|
|
|
|
|
sort: 13
|
|
|
|
|
weight: 13
|
|
|
|
|
title: VMStaticScrape
|
|
|
|
|
menu:
|
|
|
|
|
docs:
|
|
|
|
|
parent: "operator-custom-resources"
|
|
|
|
|
weight: 13
|
2023-11-22 12:59:07 +01:00
|
|
|
aliases:
|
|
|
|
|
- /operator/resources/vmstaticscrape.html
|
2023-10-05 12:43:28 +02:00
|
|
|
---
|
|
|
|
|
|
2023-10-02 14:50:08 +02:00
|
|
|
# VMStaticScrape
|
|
|
|
|
|
|
|
|
|
The `VMStaticScrape` CRD provides mechanism for scraping metrics from static targets, configured by CRD targets.
|
|
|
|
|
|
|
|
|
|
`VMStaticScrape` object generates part of [VMAgent](./vmagent.md)
|
|
|
|
|
configuration with [static "service discovery"](https://docs.victoriametrics.com/sd_configs.html#static_configs).
|
|
|
|
|
It has various options for scraping configuration of target (with basic auth,tls access, by specific port name etc.).
|
|
|
|
|
|
|
|
|
|
By specifying configuration at CRD, operator generates config
|
|
|
|
|
for [VMAgent](./vmagent.md) and syncs it.
|
|
|
|
|
It's useful for external targets management, when service-discovery is not available.
|
|
|
|
|
`VMAgent` `staticScrapeSelector` must match `VMStaticScrape` labels.
|
|
|
|
|
|
|
|
|
|
More information about selectors you can find in [this doc](./vmagent.md#scraping).
|
|
|
|
|
|
|
|
|
|
## Specification
|
|
|
|
|
|
|
|
|
|
You can see the full actual specification of the `VMStaticScrape` resource in
|
|
|
|
|
the **[API docs -> VMStaticScrape](../api.md#vmstaticscrape)**.
|
|
|
|
|
|
|
|
|
|
Also, you can check out the [examples](#examples) section.
|
|
|
|
|
|
|
|
|
|
## Examples
|
|
|
|
|
|
|
|
|
|
```yaml
|
|
|
|
|
apiVersion: operator.victoriametrics.com/v1beta1
|
|
|
|
|
kind: VMStaticScrape
|
|
|
|
|
metadata:
|
|
|
|
|
name: vmstaticscrape-sample
|
|
|
|
|
spec:
|
|
|
|
|
jobName: static
|
|
|
|
|
targetEndpoints:
|
|
|
|
|
- targets: ["192.168.0.1:9100", "196.168.0.50:9100"]
|
|
|
|
|
labels:
|
|
|
|
|
env: dev
|
|
|
|
|
project: operator
|
|
|
|
|
```
|
