...
Agent install Setup Scenario | Steps | ||||
---|---|---|---|---|---|
Kloudfuse stack & target both in same VPC and in same K8S cluster (Default) | This is the default scenario. Just use the provided values file for the agent and install. | ||||
Kloudfuse stack & target both in same VPC, but in different K8S cluster | Search for
| ||||
Kloudfuse stack hosted in a different VPC (hosted at “customer.kloudfuse.io”) | Search for
|
Required Datadog configurations
The yaml files described above already contains the required Datadog configurations for Kloudfuse to ingest the data properly. These required changes are listed below:
Code Block |
---|
datadog:
logsEnabled: true
logs:
enabled: true
containerCollectAll: true
containerCollectUsingFiles: true
autoMultiLineDetection: true
kubeStateMetricsEnabled: false
kubeStateMetricsCore:
enabled: true
ignoreLegacyKSMCheck: true
orchestratorExplorer:
enabled: true
processAgent:
enabled: true
prometheusScrape:
enabled: true
version: 1
additionalConfigs:
- configurations:
- send_monotonic_counter: false
send_distribution_counts_as_monotonic: false
send_distribution_sums_as_monotonic: false
send_histograms_buckets: true
max_returned_metrics: 999999
min_collection_interval: 15
clusterAgent:
enabled: true
datadog_cluster_yaml:
process_config:
container_collection:
enabled: false
orchestrator_explorer:
manifest_collection:
enabled: false
use_v2_api:
events: true
series: true
service_checks: true
admissionController:
enabled: false
agents:
image:
tagSuffix: jmx
useConfigMap: true
customAgentConfig:
skip_ssl_validation: false
enable_stream_payload_serialization: false
process_config:
container_collection:
enabled: false
orchestrator_explorer:
manifest_collection:
enabled: false
use_v2_api:
events: true
series: true
service_checks: true
logs_config:
use_http: true
logs_no_ssl: true
auto_multi_line_detection: true
use_v2_api: false
apm_config:
enabled: true
apm_non_local_traffic: true
metadata_providers:
- name: host
interval: 300 |
Collect high cardinality tags
...