You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/liquids/designate.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,11 @@ This liquid provides support for the DNS service Designate.
13
13
14
14
## Service-specific configuration
15
15
16
-
None.
16
+
| Field | Type | Description |
17
+
| ----- | ---- | ----------- |
18
+
|`prometheus_config.api`|[`promquery.Config`](https://pkg.go.dev/github.com/sapcc/go-bits/promquery#Config)| Configuration for the Prometheus connection from which usage data is queried by the liquid. |
19
+
|`prometheus_config.queries.zones`|[`text/template`](https://pkg.go.dev/text/template) compatible string | Prometheus query for scraping the number of zones per project. The template should contain a filter string `{{.ProjectUUID}}` to be filled with the UUID of the project to be queried for usages. |
20
+
|`prometheus_config.queries.recordsets_per_zone`|[`text/template`](https://pkg.go.dev/text/template) compatible string | Prometheus query for scraping the maximum number of recordsets across all zones of this project. The template should contain a filter string `{{.ProjectUUID}}` to be filled with the UUID of the project to be queried for usages. |
17
21
18
22
## Resources
19
23
@@ -25,3 +29,9 @@ None.
25
29
When the `recordsets_per_zone` quota is set, the backend quota for records per zone is set to 20 times that value, to
26
30
fit into the `records_per_recordset` quota (which is set to 20 by default in Designate). The quota for records per zone
27
31
cannot be managed explicitly in this liquid.
32
+
33
+
### Considerations for cloud operators
34
+
35
+
Because querying usage for the zones and especially recordsets resources is very inefficient using the Designate API, this liquid will instead collect usage data from Prometheus metrics.
36
+
Your Designate operator will have to provide suitable metrics that report the count of all zones per project, as well as the number of recordsets in those zones.
37
+
Be aware that when exporting these figures from the designate database, you have to take into account that deleted zones are soft deleted at first and have to be filtered from the result (`status != "DELETED"`).
0 commit comments