Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to migrate synthetics using the migratesynthetics script #46

Open
jamesL92 opened this issue Sep 10, 2024 · 0 comments
Open

Unable to migrate synthetics using the migratesynthetics script #46

jamesL92 opened this issue Sep 10, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jamesL92
Copy link

Description

We are unable to use the migratesynthetics script to migrate most types of synthetics. This appears to be due to the fact that the script uses the synthetics REST API endpoint defined here. According to this documentation only supports synthetic creation using legacy synthetic agent versions.

Affected synthetic types we've come across are:

  • Scripted API
  • Scripted Browser
  • Simple Browser
  • Step Monitor

Ping synthetics appear to be unaffected

Steps to Reproduce

  1. Create two separate NR accounts (A and B)
  2. In account A, create one of the above synthetic types
  3. Run the fetchmonitors script to fetch all monitors from account A - this will succeed
  4. Run the migratemonitors script to migrate from account A to B (doesn't matter if you specify useLocal or not)
  5. The migration fails

Expected Behavior

The monitor migrates successfully

Relevant Logs / Console output

We get the following log in logs/migration.log:

monitorsclient.py - ERROR - Error creating monitor <<monitor-name>>:{'status': 400, 'error': '{"errors":[{"error":"Monitor creation using legacy runtimes is not allowed as of August 26, 2024. Please refer to https://docs.newrelic.com/whats-new/2024/06/whats-new-06-26-eol-synthetics-runtime-cpm/"}],"count":1}'}

Your Environment

Not relevant to the issue.

Additional context

Per documentation, this issue would have started happening as of the 26th August. The monitors should now be created via the NerdGraph API instead.

@jamesL92 jamesL92 added the bug Something isn't working label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant