Datadog Technical Support Engineer 2 interview questions

Question 1 - Integration Not Working I’m not seeing the metric system.disk.directory.file.bytes in my Datadog account. I’m trying to monitor our application directory and I have installed a Windows Datadog Agent onto our environment. This is what we have so far for the integration: init_config: instances: - directory: "C:\Users\projects\prod-application" I know I saved the configuration, directly after saving it I then checked the platform, and I’m still not receiving the metric. I tried uninstalling the Agent and setting up the integration again, but it tells me: 2021-07-19 08:06:22 UTC | CORE | INFO | (pkg/metadata/host/host.go:169 in getPublicIPv4) | No public IPv4 address found 2021-07-19 09:12:05 UTC | CORE | ERROR | (pkg/util/azure/diagnosis.go:21 in diagnose) | Azure HostAliases: unable to query metadata endpoint: status code 404 trying to GET http://111.254.167.255/metadata/instance/compute/vmId?api-version=201 7-04-02 2021-07-19 09:12:05 UTC | CORE | ERROR | (pkg/util/azure/diagnosis.go:21 in diagnose) | Azure HostAliases: unable to query metadata endpoint: status code 404 trying to GET http://169.254.169.254/metadata/instance/compute/vmId?api-version=201 7-04-02 2021-07-19 09:12:17 UTC | CORE | WARN | (pkg/autodiscovery/providers/file.go:192 in collectEntry) | C:\ProgramData\Datadog\conf.d\directory.d\conf.yaml is not a valid config file: yaml: line 3: found unknown escape character 2021-07-19 09:12:20 UTC | CORE | INFO | (pkg/serializer/serializer.go:374 in sendMetadata) | Sent metadata payload, size (raw/compressed): 1331/379 bytes. Can you let me know what I’m doing wrong so I can get this integration up and running?