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
1. Click {{< ui >}}Preview{{< /ui >}} to view the form as it appears to respondents.
79
78
1. Click {{< ui >}}Share{{< /ui >}} to copy the form link or configure sharing options.
80
79
80
+
## Customize start and end pages
81
+
82
+
Forms can include a start page shown before the first question, and an end page shown after a respondent submits the form. Customize the title and message on both pages. By default, forms don't include a start page, and the end page shows a generic completion message.
83
+
84
+
To add or customize a start or end page:
85
+
1. From the [Forms][2] page, click a form to open it in the editor.
86
+
1. In the {{< ui >}}Pages{{< /ui >}} panel, click {{< ui >}}Start Page{{< /ui >}} or {{< ui >}}End Page{{< /ui >}}. If no start page exists, click the plus **+** icon to add one.
87
+
1. Edit the title and message.
88
+
1. Click {{< ui >}}Publish{{< /ui >}} or {{< ui >}}Publish Changes{{< /ui >}} to apply your changes.
89
+
81
90
## Form settings
82
91
83
92
From the [Forms][2] page, click a form to open it in the editor. In the editor header, click the gear <iclass="icon-cog-2"></i> icon to access the following settings:
@@ -102,7 +111,9 @@ To configure sharing for a form:
102
111
The following sharing options are available:
103
112
104
113
{{% collapse-content title="Share within Datadog" level="h3" expanded=false %}}
105
-
Share the form with users in your Datadog organization.
114
+
Share the form with users or teams in your Datadog organization.
115
+
116
+
Add individual users or teams as recipients. Enable {{< ui >}}Notify added teammates{{< /ui >}} to send a notification, and optionally add a custom message. Teams are notified in their configured Slack channel or by email; individual users are notified by email.
106
117
107
118
Under {{< ui >}}Add to Dashboard{{< /ui >}}, use the dropdown to add the form to an existing dashboard or create a dashboard.
108
119
@@ -116,7 +127,7 @@ The following options are available:
116
127
117
128
-**Specific individuals**: Add recipients by individual email address. For example, `alice@example.com` and `bob@example.com`.
118
129
-**Company domain**: Share with anyone in a specific email domain. For example, `*@yourcompany.com`.
119
-
-**Shareable link**: Generate a link that anyone can use to access the form without a Datadog account.
130
+
-**Anyone with a link**: Generate a link that anyone can use to access the form after verifying their email address.
120
131
{{% /collapse-content %}}
121
132
122
133
To pause or remove external sharing, click {{< ui >}}Share{{< /ui >}}, then click {{< ui >}}Edit{{< /ui >}} and select {{< ui >}}Pause Sharing{{< /ui >}} or {{< ui >}}Delete Sharing{{< /ui >}}.
Copy file name to clipboardExpand all lines: hugo/content/en/byoc-logs/introduction/network.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,6 +37,8 @@ If your environment uses an HTTP proxy, BYOC Logs supports standard proxy config
37
37
38
38
Only **searcher** pods establish the reverse connection. Indexers, the control plane, the metastore, and the janitor do not initiate any connection to Datadog.
39
39
40
+
<divclass="alert alert-warning">Keep at least one searcher pod running when using the reverse connection. If all searcher pods are unavailable or scaled to <code>0</code>, Datadog cannot route queries or index management requests through the reverse connection until a searcher pod starts and reconnects.</div>
41
+
40
42
## Public ingress (optional)
41
43
42
44
It is also possible to configure BYOC Logs to deploy a public ingress so Datadog can establish the connection in the other direction.
The `datadog/cloudprem` Helm chart creates Horizontal Pod Autoscalers (HPAs) for BYOC (Bring Your Own Cloud) Logs indexers and standalone compactors when you enable them. HPAs are disabled by default, and each component is configured independently.
21
+
22
+
## Before you begin
23
+
24
+
Before you enable autoscaling, you need:
25
+
26
+
- A BYOC Logs deployment installed with the `datadog/cloudprem` Helm chart.
27
+
- Chart version `0.4.6` or later for standalone compactor autoscaling.
28
+
- Kubernetes Metrics Server, or another metrics API implementation, installed in the cluster.
29
+
- Enough node capacity for the maximum number of indexer and compactor pods.
30
+
- CPU requests configured for autoscaled workloads.
31
+
32
+
CPU-based HPA calculations use the pod CPU request. Indexers get CPU requests from `indexer.podSize` or `indexer.resources.requests.cpu`. For standalone compactors, configure `compactor.resources.requests.cpu`.
33
+
34
+
## Enable indexer autoscaling
35
+
36
+
To enable the indexer HPA, set `indexer.autoscaling.enabled` to `true`:
37
+
38
+
```yaml
39
+
indexer:
40
+
autoscaling:
41
+
enabled: true
42
+
```
43
+
44
+
When you enable indexer autoscaling, the HPA controls the number of indexer pods and ignores `indexer.replicaCount`.
45
+
46
+
Default indexer HPA settings:
47
+
48
+
| Setting | Default | Description |
49
+
|---|---:|---|
50
+
| `indexer.autoscaling.minReplicas` | `2` | Minimum number of indexer pods |
51
+
| `indexer.autoscaling.maxReplicas` | `10` | Maximum number of indexer pods |
52
+
| CPU target | `70%` | Average CPU utilization target across indexer pods |
53
+
54
+
## Enable compactor autoscaling
55
+
56
+
To enable the compactor HPA, enable standalone compactors and set `compactor.autoscaling.enabled` to `true`:
57
+
58
+
```yaml
59
+
enableStandaloneCompactors: true
60
+
61
+
compactor:
62
+
autoscaling:
63
+
enabled: true
64
+
```
65
+
66
+
The chart creates the compactor HPA only when you set both `enableStandaloneCompactors` and `compactor.autoscaling.enabled` to `true`. When you enable compactor autoscaling, the HPA controls the number of compactor pods and ignores `compactor.replicaCount`.
67
+
68
+
Default compactor HPA settings:
69
+
70
+
| Setting | Default | Description |
71
+
|---|---:|---|
72
+
| `compactor.autoscaling.minReplicas` | `1` | Minimum number of compactor pods |
73
+
| `compactor.autoscaling.maxReplicas` | `10` | Maximum number of compactor pods |
74
+
| CPU target | `80%` | Average CPU utilization target across compactor pods |
75
+
76
+
## Override the defaults
77
+
78
+
Set `minReplicas` and `maxReplicas` alongside `enabled` to size the scaling range for your workload. Use the [Cluster Sizing][1] guide to pick a maximum that your node capacity supports:
79
+
80
+
```yaml
81
+
indexer:
82
+
autoscaling:
83
+
enabled: true
84
+
minReplicas: 4
85
+
maxReplicas: 20
86
+
```
87
+
88
+
## Apply the configuration
89
+
90
+
Add the autoscaling values to your BYOC Logs values file, then upgrade your release:
91
+
92
+
```shell
93
+
helm upgrade <RELEASE_NAME> datadog/cloudprem \
94
+
--namespace <NAMESPACE_NAME> \
95
+
--values datadog-values.yaml
96
+
```
97
+
98
+
## Verify the HPAs
99
+
100
+
List HPAs in the BYOC Logs namespace:
101
+
102
+
```shell
103
+
kubectl get hpa -n <NAMESPACE_NAME>
104
+
```
105
+
106
+
Describe an HPA to check metrics and recent scaling events:
`<RELEASE_NAME>-indexer`and `<RELEASE_NAME>-compactor` are the default HPA names created by the chart. If you set `nameOverride` or `fullnameOverride`, use the resulting names instead.
114
+
115
+
If `kubectl get hpa` shows `<unknown>` in the `TARGETS` column, the HPA cannot read CPU metrics. Check that the metrics API is running and that the target pods have CPU requests.
0 commit comments