Skip to content

Feat: dynamic canaries#2686

Open
alvarocabanas wants to merge 2 commits into
mainfrom
feat/dynamic_canaries
Open

Feat: dynamic canaries#2686
alvarocabanas wants to merge 2 commits into
mainfrom
feat/dynamic_canaries

Conversation

@alvarocabanas

Copy link
Copy Markdown
Contributor
  • Changes fleet_deployment.sh to use the Fleet API in newrelic-cli instead of using Graphql directly.
  • Adds a scheduled GitHub Action (every 6h) that rotates the canary fleets through an ordered set of agent config versions, advancing one step per run and wrapping around. Each run fans out over a matrix of environment (staging/production) and platform (linux/windows), deploying via the newrelic-CLI-based fleet_deployment.sh.

@alvarocabanas alvarocabanas requested a review from a team as a code owner July 10, 2026 16:24
@alvarocabanas alvarocabanas force-pushed the feat/dynamic_canaries branch from c423970 to ac98283 Compare July 10, 2026 16:26
Comment thread test/onhost-canaries/scripts/fleet_deployment.sh
Comment thread .github/workflows/scheduled_onhost_canary_config_rotation.yml
Comment thread .github/workflows/scheduled_onhost_canary_config_rotation.yml Outdated
…ur canaries and refactors fleet_deployment.sh to use the fleet API in newrelic-cli
@alvarocabanas alvarocabanas force-pushed the feat/dynamic_canaries branch from ac98283 to 7bcc953 Compare July 13, 2026 12:37
# Second -> NRDOT 1.19.0 (canaries-nrdot)
AGENT_SPECS_LINUX_STAGING: >-
NRInfra:1.77.1:MTIyMTMwNjh8TkdFUHxBR0VOVF9DT05GSUdVUkFUSU9OX1ZFUlNJT058MDE5ZjViZTItYjdkYy03YmM5LTg0OTUtYTIyMmI5NTYyZDAy
NRDOT:1.19.0:MTIyMTMwNjh8TkdFUHxBR0VOVF9DT05GSUdVUkFUSU9OX1ZFUlNJT058MDE5ZjViZTMtNmU3YS03NzA0LWI0NjgtOTAwMDY1NjgyMWJj

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be MTIyMTMwNjh8TkdFUHxBR0VOVF9DT05GSUdVUkFUSU9OX1ZFUlNJT058MDE5ZjViZTQtMWFmNC03YmM4LTlmZDgtZmQ3YzIzMWNlNzMx I think.

The one here points to canaries-infra-config-windows. It's a copy paste from the one below.

Comment on lines +39 to +43
AGENT_SPECS_LINUX_PRODUCTION: >-
NRInfra:1.77.1:NjQyNTg2NXxOR0VQfEFHRU5UX0NPTkZJR1VSQVRJT05fVkVSU0lPTnwwMTlmNGM3Yi1lYjAyLTc1MmQtOGViOC0zNDYyMWM2ZDRkMzQ
NRDOT:1.19.0:NjQyNTg2NXxOR0VQfEFHRU5UX0NPTkZJR1VSQVRJT05fVkVSU0lPTnwwMTlmNGM3Yy05M2Y3LTcyMjctODJmZS01OGYwMjcyMDViMDI
# First -> NRInfra 1.77.1 (canaries-infra-config-windows)
# Second -> NRDOT 1.19.0 (canaries-nrdot-windows)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are any of the existing alerts affected by switching between the infrastructure agent and nr-dot?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, good point, I didn't control it, and they will for sure fail, we are working on the samples, so the only way to make this work is making the alerts be compatible with both infra-agent and NRDOT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants