[pull] master from DataDog:master#547
Merged
Merged
Conversation
* Run n8n queue-mode test environment on Postgres * Add changelog entry for n8n compose Postgres switch * Drop the unneeded changelog entry for the tests-only change * Set a fixed N8N_ENCRYPTION_KEY for both n8n containers The worker no longer mounts the shared /home/node/.n8n volume, so it can't read the auto-generated key written there by main on first boot. n8n refuses to start the worker without an encryption key, which cascades into webhook-registration timeouts on main after restart. Pin the key in the compose env so neither container depends on the shared volume for it.
…y errors (#23661) * [mongo] fall back to configured host when serverStatus hostname lookup fails Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> * [mongo] add changelog entry for PR #23661 Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> * [mongo] shorten changelog entry for PR #23661 Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> * [mongo] raise on serverStatus failure to surface auth/connectivity errors Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> * [mongo] simplify changelog entry for PR #23661 Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
…levant metrics (#21294) * added system_metrics generator and generated queries * updated default hatch env matrix, added keeper repo * update docker compose files, switched from zookeeper to clickhouse-keeper * updated base conftest for new docker compose * added generator for system events * updated generator, added tests template * added generated data * updated metadata.csv * updated tests * added async metrics parsing * added support of plain and json logs by default * fixed linters * exported new dashboard * added 25.8 and removed 25.5 versions metrics * fixed max desc length for metadata file * added metrics based on system.errors * added metrics stat counter * added system errors check to the agent and fixed e2e * explicit query match mapping * added explicit agent check before the next assert * switch system.errors metrics type to monotonic_gauge and extended metadata.csv descriptions with that info * added changelog entry * updated conf.yaml.example file * increased conditions waiting time on the env startup * split compose files for mounted logs testing and the regular run * fixed metrics_metadata * fixed UNKNOWN_IDENTIFIER metrics name * updated conf.example with new ddev * fixed license-headers * small fixes on dashboard panels * update tests with brand new CH client * linter fix in conftest * removed unfinished test * template typo fixes + renamed metrics prefixes and the package name * removed 25.6 and 25.7 versions * simplified docker setup to 1 CH and 1 Keeper nodes * updated docker setup for legacy CH versions * renamed hatch generator script * rolled back old metrics + added version specific ones * fix format * CI sync * added changelog file * fixed license-headers validator * renamed changelog file * renamed metrics on the dashboard * fixed some leftovers after merge * updated flush_interval_milliseconds for newer CH versions for DBM integration tests * fixed DBM tests on supported CH versions * fixed formatter * updated license-headers * returned previous manifest metric-check name * removed all quantiles * removed `ddsource` assertion from the tests * return ddsource back to fqt_events as it was before * added cache for query manager * added TLS setting after merge conflicts * fixed dbm_integration tests after the merge * added 23.2 and 23.8 to the legacy versions * onboarded new config settings * fixed LogTrace event metric * introduced generic errors.raised metric for all the errors * set version gating for system errors to 21.3 to have remote column * added test for system errors query, fixed dbm query check * fixed linter
* Add --explicit-package-bases to default mypy_args Always prepend --explicit-package-bases to the mypy command built by the datadog-checks Hatch environment collector. The flag is structurally required by every integration's datadog_checks/<name>/ namespace package layout, so integrations that enable check-types = true no longer need to repeat it in their own hatch.toml. It is also a no-op on the few integrations that ship a datadog_checks/__init__.py. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Add changelog --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* [SEC-27721]: Add SIEM category to integrations * [SEC-27721]: Add SIEM category to additional integrations
* Validate matrix targets for dependency resolution * Update dependency resolution * Update dependency resolution --------- Co-authored-by: dd-agent-integrations-bot[bot] <dd-agent-integrations-bot[bot]@users.noreply.github.com>
…um_lsf hatch.toml (#23743)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )