Are you a member of the Splunk Community?
- Find Answers
- :
- Apps & Add-ons
- :
- All Apps and Add-ons
- :
- Re: How can we migrate inputs from DB Connect 3.7 ...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Splunk Enterprise 9.0.1.
We upgrade DB Connect from 3.7.0. to 3.11.1 and we started to notice that some inputs were not working.
Also on _internal we found an event that lists inputs that require migration.
INFO c.s.d.s.m.s.DbInputToModularInputInstanceMigrator - DB Inputs requiring migration: [...]
The actual documentation doesnt say anything about this migration.
https://docs.splunk.com/Documentation/DBX/3.11.1/DeployDBX/MigratefromDBConnectv1
Is there any other documentation on how to migrate to the latest version?
UPDATE:
We found that the cron expression validation changed between versions:
'1/10 * * * *' was a valid expression in 3.7, now its no longer valid. We have to do '1-59/10 * * * *'.
Also we have to disable and then enable the input for it to start working again, changing the cron is not enough.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We got lots of inputs, we can try to remake them, but its going to take time. This is the last thing we are trying.
We found that the cron expression validation changed between versions:
'1/10 * * * *' was a valid expression in 3.7, now its no longer valid. We have to do '1-59/10 * * * *'.
Also we have to disable and then enable the input for it to start working again, changing the cron is not enough.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Very nice to hear you solved and thank you for the information.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If not too many inputs seem to be migrated, you can copy the query and setting to create new inputs. It maybe a faster solution.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We got lots of inputs, we can try to remake them, but its going to take time. This is the last thing we are trying.
We found that the cron expression validation changed between versions:
'1/10 * * * *' was a valid expression in 3.7, now its no longer valid. We have to do '1-59/10 * * * *'.
Also we have to disable and then enable the input for it to start working again, changing the cron is not enough.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @joshiro,
You can try below migration script.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We already saw that documentation, and we didnt try to migrate that way because it doesnt match our context. We are already on 3.7 and that document is for an upgrade from 2.x to 3.
And we were using DB Connect 3 for a long time without problems, this just happened recently when updating to the latest version, from 3.7.0.
Might check what the upgrade scripts do, and see if they help us in any way.
Thanks.
Splunk Observability Cloud's AI Assistant in Action Series: Auditing Compliance and ...
Splunk Community Badges!
What You Read The Most: Splunk Lantern’s Most Popular Articles!
