All Apps and Add-ons

Why does Splunk show an "update" link for Splunk DB Connect 1 if it's already in the latest version?

hettervi
Builder

Hi folks!

I recently tried to update my Splunk DB Connect v1 app to version 1.2.2. When I tried to do so in Splunk Web, I got an error, both when using the link in the app manager and when first downloading the app to localhost. I then tried updating the app via CLI, but got an error here as well. Assuming the update didn't happen I looked in my Splunk DB Connect v1 app folder (dbx), only to find that there where several version of default.old.<timestamp> from my previous tries of upgrading the app and that the README said it was in version 1.2.2.

Now, when looking at the app in the app manager, it says it's in version 1.2.2, but still there is a "Update to 1.2.2" link right next to it. Why is it so? Is this a bug? Is there any way to surely validate if my app was successfully updated or not?

All help is appreciated. Thanks!

0 Karma
1 Solution

hettervi
Builder

The problem kind of solved itself, the "update to 1.2.2" link is gone, but I don't know how or when. Maybe someone restarted the Splunk instance at some point and this made Splunk "sort things out" regarding app versions and updates?

View solution in original post

0 Karma

hettervi
Builder

The problem kind of solved itself, the "update to 1.2.2" link is gone, but I don't know how or when. Maybe someone restarted the Splunk instance at some point and this made Splunk "sort things out" regarding app versions and updates?

0 Karma

dshpritz
SplunkTrust
SplunkTrust

I believe the update checking is based on the build number in the app.conf of the app. So, if you look at the app.conf for the version you have installed, and look at the number in the downloaded version, are they the same? The DBX 1 that I just downloaded has a build number of 274527.

hettervi
Builder

I just checked, the build number in app.conf is 274527, the same number as you. Though, now the "update to 1.2.2" link is gone, as pointed out in my comment below. Is it possible that this build number was indeed wrong (not 274527), but got updated to the right build number (274527) at some point if e.g. Splunk was restarted? If not, my best guess is that the "update to 1.2.2" link on the Splunk DB Connect v1 app already in version 1.2.2 was a bug.

0 Karma

woodcock
Esteemed Legend

Perhaps because V1 is discontinued and you should move to DB Connect v2?

0 Karma

dshpritz
SplunkTrust
SplunkTrust

v1 is still being developed, that is, bugs are still getting fixed. Also, it appears the prompt is to upgrade to "1.2.2" not "2.x".

martin_mueller
SplunkTrust
SplunkTrust

Yup, you should never see an "upgrade to 2.x" prompt on a local v1 install because the two have different Splunkbase IDs.

0 Karma

Lucas_K
Motivator

db connection v2 is functionally different to v1. They aren't even remotely the same even though they share the same name.

We are actually running both side by side. Hopefully one day v2 will be able to do as much as v1.

The update link is technically a bug as db connect v2 is a totally different app unfortunately they point v1 to v2 so the upgrade link will appear.

woodcock
Esteemed Legend

So this is a correct answer then.

0 Karma

hettervi
Builder

It's still supported for 6.3, and the latest update is from Oct. 6 this year I think.

0 Karma
Get Updates on the Splunk Community!

Happy CX Day to our Community Superheroes!

Happy 10th Birthday CX Day!What is CX Day? It’s a global celebration recognizing innovation and success in the ...

Check out This Month’s Brand new Splunk Lantern Articles

Splunk Lantern is a customer success center providing advice from Splunk experts on valuable data insights, ...

Routing Data to Different Splunk Indexes in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. The OpenTelemetry project is the second largest ...