Code change:
This is a continuation of the topic from the initial "upgrade datadog-agent to v7" ticket - see for details on that. The is a metrics and log collection agent intended to run on linux systems for use with 's paid service. On other linux distributions, installing the datadog-agent includes the integration/plugin code, there is no separate install for those, or post-install steps to install the plugins (only config to activate/configure them). Configure the in , and add some extra integration, such as the docker integration. and look at the installed, the plugins are not available. You should see logs from the agent about those. When configuring the datadog-agent, the standard integrations/plugins (docker, nginx, apache, postgres, etc, etc) should be installed and available to the agent if the agent is configured to use them. Please run and paste the result.
There's still something wrong with the Python environment.
Most likely we need to use pyproject to build it properly: That results into missing ddtrace package, which needs to be .
Looks like setuptools wasn't building the and modules. and should fix the integrations. Datadog is planning on dropping setuptools, so we should switch over to pyproject. The blocker is that there are a number of missing dependencies that aren't on nixpkgs yet, but I've started working on that. the Docker integration was rewritten in Go and is now built together with the . You can enable it with: I have no idea why they're now called Yeah, we need to rethink how these integrations are enabled. Now that some of them are part of the , it's become quite a pain to set up.
Fixed in
Thanks! Note that, to get this to run for me, nixpkgs needed an overlay specifying that all packages wanting would get . That looks liked: It seems that, while is deprecated and python 3 is "the default", the package maps to , so a lot of packages effectively default to python 2. Thanks to for coming up with that workaround. I haven't yet see the docker integration work, but I've seen the plugins and such install, so that is promising, and it's likely the last bits are in my config to sort out.
are you on an older release of nixpkgs? has been set to for the datadog integrations since .
We determined the evaluation error came from here: Did we mess that up somehow?
There's a good chance that can be removed from there with no impact. We recently did so for the systemd service.
is a vestige of the old agent. It was a python wrapper that launched that jmx java thing. can most definitely be removed check is broken. I imagine we'd need to package

Related discussion:
text: <ins> { lib , buildPythonPackage , fetchPypi , pytestCheckHook , pythonOlder , setuptools }: buildPythonPackage rec { pname = "binary"; version = "1.0.0"; format = "pyproject"; disabled = pythonOlder "3.7"; src = fetchPypi { inherit pname version; hash = "sha256-bsAQ5Y9zMevIvJY42+bGbWNd5g1YGLByO+9N6tDsKKY="; }; nativeBuildInputs = [ setuptools ]; nativeCheckInputs = [ pytestCheckHook ]; pythonImportsCheck = [ "binary" "binary.core" ]; meta = with lib; { description = "Easily convert between binary and SI units (kibibyte, kilobyte, etc.)"; homepage = "https://github.com/ofek/binary"; license = with licenses; [ asl20 mit ]; maintainers = with maintainers; [ ]; }; } </ins>