datadog-agent | present repository contains the source code | Monitoring library
kandi X-RAY | datadog-agent Summary
kandi X-RAY | datadog-agent Summary
The present repository contains the source code of the Datadog Agent version 7 and version 6. Please refer to the Agent user documentation for information about differences between Agent v5, Agent v6 and Agent v7. Additionally, we provide a list of prepackaged binaries for an easy install process here. Note: the source code of Datadog Agent v5 is located in the dd-agent repository.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of datadog-agent
datadog-agent Key Features
datadog-agent Examples and Code Snippets
Community Discussions
Trending Discussions on datadog-agent
QUESTION
I am attempting to use the CDK to deploy an EC2 TaskDefinition for a DataDog agent which uses 3 bind mount volumes. The DD example task definition looks pretty simple.
The fragment of a Cloudformation template below has been generated by the AWS CDK. Deploying this raises the Unknown volume: 'null' error with all three volumes as is. It deploys successfully if no volumes are set.
I have tried using changesets through the cloudformation UI to add volumes one at a time. Adding the first volume by itself works normally, but adding two or three fails with the Unknown volume: 'null' error, regardless of doing it in stages or in one lump.
Editing the task definition manually through the ECS console does add a second volume successfully.
There doesn't appear to be any documentation on this particular error, and I can't understand how the ECS service is getting a null in the volumes array. I suspect I'm missing something obvious somewhere, so hoping someone has some insight into what's going on.
...ANSWER
Answered 2021-Nov-01 at 08:42Turns out I was misreading the CDK addMountPoints function.
When I was having success adding the volumes, I was also not adding any mount points, but I kept adding mount points while also adding new things, so masked the actual error. This is the relevant javascript from my original code.
QUESTION
i am trying to send kafka consumer metrics to datadog but its not showing in monitoring when I select the node. The server is giving below check in status
...ANSWER
Answered 2021-Mar-24 at 15:02Nothing is wrong there. DataDog conceals that the Kafka integration uses Dogstatsd under the hood. When use_dogstatsd: 'true within /etc/datadog-agent/datadog.yaml is set, metrics do appear in DataDog webUI. If that option is not set the default Broker data is available via JMXFetch using sudo -u dd-agent datadog-agent status as also via sudo -u dd-agent datadog-agent check kafka but not in the webUI.
QUESTION
I have a secret stored as an env variable in GitLab : TF_VAR_DD_API_KEY
In my main.tf I am doing something like this:
ANSWER
Answered 2020-Oct-28 at 13:46You need to add a module input variable like this:
QUESTION
I try to setup a postgres check using DD Agent and i'm getting an error thrown by postgres.py script. As you can see in the screenshot, i'm using this simple query to get the number of active connections to a db. I've put it inside the /etc/datadog-agent/conf.d/postgres.d/conf.yaml like this :
...ANSWER
Answered 2020-Oct-17 at 22:24In these kinds of checks, the response order matters, since the columns returned from the DB are going to be mapped back to the names specified in the YAML.
Reading the error message:
Error: postgres:953578488181a512 | (postgres.py:398) | non-numeric value
cldtxfor metric columnactive_connectionsof metric_prefixpostgresql
We can see that the value of cldtx is being returned for the active_connections column, which in the YAML is declared as a gauge, and this is a string.
The fix should be straightforward, by reordering the YAML, like so:
QUESTION
I set up datadog trace client in my kubernetes cluster to monitor my deployed application. It was working fine with the kubernetes version 1.15x but as soon as I upgraded the version to 1.16x, the service itself is not showing in the Datadog Dashboard.
Currently using:
Kubernetes 1.16.9
Datadog 0.52.0
When checked for agent status. It is giving following exception :
...ANSWER
Answered 2020-Jul-01 at 15:20This was a issue with deployed DataDog daemonset for me:
What I did to resolve:
Check daemonset if it exists or not:
QUESTION
I've using ansible k8s module with a dynamic definition where I call it with
...ANSWER
Answered 2020-May-05 at 20:19You can not put {{ }} inside {{ }} so try remove extra block:
QUESTION
I have a chef_resource that looks like this
...ANSWER
Answered 2020-Feb-04 at 08:21You can try to create an execute resource with command equal to your bash not_if guard.
QUESTION
My task definition:
...ANSWER
Answered 2020-Jan-10 at 10:04You need to set the aws_ecs_task_definition's network_mode to awsvpc if you are defining the network_configuration of the service that uses that task definition.
This is mentioned in the documentation for the network_configuration parameter of the aws_ecs_service resource:
network_configuration- (Optional) The network configuration for the service. This parameter is required for task definitions that use theawsvpcnetwork mode to receive their own Elastic Network Interface, and it is not supported for other network modes.
In your case you've added the network_mode parameter to the container definition instead of the task definition (a task is a collection of n containers and are grouped together to share some resources). The container definition schema doesn't allow for a network_mode parameter.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install datadog-agent
Go 1.17 or later. You'll also need to set your $GOPATH and have $GOPATH/bin in your path.
Python 3.7+ along with development libraries for tooling. You will also need Python 2.7 if you are building the Agent with Python 2 support.
Python dependencies. You may install these with pip install -r requirements.txt This will also pull in Invoke if not yet installed.
CMake version 3.12 or later and a C++ compiler
Checkout the repo: git clone https://github.com/DataDog/datadog-agent.git $GOPATH/src/github.com/DataDog/datadog-agent.
cd into the project folder: cd $GOPATH/src/github.com/DataDog/datadog-agent.
Install go tools: invoke install-tools.
Install go dependencies: invoke deps. Make sure that $GOPATH/bin is in your $PATH otherwise this step might fail.
Create a development datadog.yaml configuration file in dev/dist/datadog.yaml, containing a valid API key: api_key: <API_KEY>
Build the agent with invoke agent.build --build-exclude=systemd. By default, the Agent will be built to use Python 3 but you can select which Python version you want to use: invoke agent.build --python-runtimes 2 for Python2 only invoke agent.build --python-runtimes 3 for Python3 only invoke agent.build --python-runtimes 2,3 for both Python2 and Python3 You can specify a custom Python location for the agent (useful when using virtualenvs): invoke agent.build \ --python-runtimes 2,3 \ --python-home-2=$GOPATH/src/github.com/DataDog/datadog-agent/venv2 \ --python-home-3=$GOPATH/src/github.com/DataDog/datadog-agent/venv3 . Running invoke agent.build: Discards any changes done in bin/agent/dist. Builds the Agent and writes the binary to bin/agent/agent. Copies files from dev/dist to bin/agent/dist. See https://github.com/DataDog/datadog-agent/blob/main/dev/dist/README.md for more information. If you built an older version of the agent, you may have the error make: *** No targets specified and no makefile found. Stop.. To solve the issue, you should remove CMakeCache.txt from rtloader folder with rm rtloader/CMakeCache.txt.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
