Skip to content

Commit 2b98b97

Browse files
committed
simpler setup
1 parent dec351b commit 2b98b97

File tree

1 file changed

+7
-66
lines changed
  • content/en/feature_flags/setup/server

1 file changed

+7
-66
lines changed

content/en/feature_flags/setup/server/_index.md

Lines changed: 7 additions & 66 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ further_reading:
55
- link: "/feature_flags/setup/"
66
tag: "Documentation"
77
text: "Feature Flags Setup"
8-
- link: "/agent/"
8+
- link: "/remote_configuration/"
99
tag: "Documentation"
10-
text: "Datadog Agent"
10+
text: "Remote Configuration"
1111
---
1212

1313
{{< callout url="http://datadoghq.com/product-preview/feature-flags/" >}}
@@ -30,79 +30,20 @@ Before setting up server-side feature flags, ensure you have:
3030

3131
## Agent configuration
3232

33-
Server-side feature flags use Remote Configuration to deliver flag configurations to your application. Enable Remote Configuration in your Datadog Agent.
33+
Server-side feature flags use [Remote Configuration][1] to deliver flag configurations to your application. Enable Remote Configuration in your Datadog Agent by setting `DD_REMOTE_CONFIGURATION_ENABLED=true` or adding `remote_configuration.enabled: true` to your `datadog.yaml`.
3434

35-
### Configuration file
35+
See the [Remote Configuration documentation][1] for detailed setup instructions across different deployment environments.
3636

37-
Add the following to your `datadog.yaml`:
37+
### Polling interval
3838

39-
{{< code-block lang="yaml" filename="datadog.yaml" >}}
40-
# Enable Remote Configuration
41-
remote_configuration:
42-
enabled: true
43-
44-
# Your Datadog API key
45-
api_key: <YOUR_API_KEY>
46-
{{< /code-block >}}
47-
48-
### Environment variables
49-
50-
Alternatively, configure the Agent using environment variables:
39+
The Agent polls Datadog for configuration updates at a configurable interval. This interval determines the average time between making a flag change in the UI and the change becoming available to your application.
5140

5241
{{< code-block lang="bash" >}}
53-
# Enable Remote Configuration
54-
DD_REMOTE_CONFIGURATION_ENABLED=true
55-
56-
# Your Datadog API key
57-
DD_API_KEY=<YOUR_API_KEY>
58-
5942
# Optional: Configure polling interval (default: 60s)
60-
# This determines the average time between making a flag change in the UI
61-
# and the change becoming available to your application.
6243
DD_REMOTE_CONFIGURATION_REFRESH_INTERVAL=10s
6344
{{< /code-block >}}
6445

65-
### Docker
66-
67-
When running the Agent in Docker, pass the environment variables:
68-
69-
{{< code-block lang="bash" >}}
70-
docker run -d \
71-
-e DD_API_KEY=<YOUR_API_KEY> \
72-
-e DD_REMOTE_CONFIGURATION_ENABLED=true \
73-
-v /var/run/docker.sock:/var/run/docker.sock:ro \
74-
-v /proc/:/host/proc/:ro \
75-
-v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro \
76-
gcr.io/datadoghq/agent:latest
77-
{{< /code-block >}}
78-
79-
### Kubernetes
80-
81-
For Kubernetes deployments, add the configuration to your Agent manifest:
82-
83-
{{< code-block lang="yaml" filename="datadog-agent.yaml" >}}
84-
apiVersion: v1
85-
kind: ConfigMap
86-
metadata:
87-
name: datadog-agent-config
88-
data:
89-
datadog.yaml: |
90-
remote_configuration:
91-
enabled: true
92-
{{< /code-block >}}
93-
94-
Or set environment variables in your Agent deployment:
95-
96-
{{< code-block lang="yaml" >}}
97-
env:
98-
- name: DD_REMOTE_CONFIGURATION_ENABLED
99-
value: "true"
100-
- name: DD_API_KEY
101-
valueFrom:
102-
secretKeyRef:
103-
name: datadog-secrets
104-
key: api-key
105-
{{< /code-block >}}
46+
[1]: /remote_configuration
10647

10748
## Application configuration
10849

0 commit comments

Comments
 (0)