After following the migration process to migrate from DB Connect 1 to DB Connect 2 located here
Fails silently with no exceptions or outputs.
Answering my own question here, to save folks time and agony in finding a solution.
Our existing database names contain hyphens and underscores (ex. database-things_are-in-dev) which the migration script fails on, to fix edit the following line in
/opt/splunk/etc/apps/splunk_app_db_connect/bin/dbx2/migration/migrations/input/001_migrate_from_dbx1.py
Change this:
name_pattern = r'dbmon-(?P<type>\w+)://(?P<database>\w+)/(?P<unique_name>\w+)'
to this:
name_pattern = r'dbmon-(?P<type>\w+)://(?P<database>\S+)/(?P<unique_name>\S+)'
Rerun script.
Another note you'll need to manually check your migrated inputs, if you used either:
instead of a cron, those will import, but continue to fail until you manually edit them (similar to how you manually edit the lookups).
Answering my own question here, to save folks time and agony in finding a solution.
Our existing database names contain hyphens and underscores (ex. database-things_are-in-dev) which the migration script fails on, to fix edit the following line in
/opt/splunk/etc/apps/splunk_app_db_connect/bin/dbx2/migration/migrations/input/001_migrate_from_dbx1.py
Change this:
name_pattern = r'dbmon-(?P<type>\w+)://(?P<database>\w+)/(?P<unique_name>\w+)'
to this:
name_pattern = r'dbmon-(?P<type>\w+)://(?P<database>\S+)/(?P<unique_name>\S+)'
Rerun script.
Another note you'll need to manually check your migrated inputs, if you used either:
instead of a cron, those will import, but continue to fail until you manually edit them (similar to how you manually edit the lookups).