Discussions related to using object storage as a backup target.
Post Reply
MatzeB
Veeam Vanguard
Posts: 41
Liked: 10 times
Joined: Jan 04, 2021 7:51 am
Full Name: Matthias Beller
Contact:

Object Storage User Agent Version

Post by MatzeB »

Hi Team,

we offer an S3 object storage as an provider for our customers.
For different reasons we make queries which client is connecting with which software product and version.
We need this for analysies as well as "value add" for example to give customer hints to upgrade etc.

All software products we seen are sending the exact version number/build of their product - but not Veeam.
For example
Veeam 12.0 / 12.1 / 12.2 etc are all sending 12.0
Veeam M365 7.X is sending 7.0

I would really like to see the same behaviour than any other software - send the current version number.
Would be nice to get feedback why you do it like this and if you plan to change this.

Image


Regards
Matze
veremin
Product Manager
Posts: 20677
Liked: 2382 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Object Storage User Agent Version

Post by veremin »

We added support for the user agent string quite some time ago and decided then to update it with each major version of the product. The exact reasons for this decision are hard to recall now, given how long ago it was made.

However, thank you for your feedback; we will consider the possibility of including the exact product version in the user agent string, not just the major part, in the future.
MatzeB
Veeam Vanguard
Posts: 41
Liked: 10 times
Joined: Jan 04, 2021 7:51 am
Full Name: Matthias Beller
Contact:

Re: Object Storage User Agent Version

Post by MatzeB »

Thanks for your feedback, looks like a historic decision ;)

I think differently, the other way around, why would it be bad to always give the exact build number here.
I think that could be an added value for one or the other and if not, it doesn't hurt.

Practice example:
I think with the release of 12.2 it was announced that there were some optimizations regarding object storage, especially fewer API calls, we tried to track this for customers who have already updated, it would be helpfull for analysis.

Matze
Gostev
Chief Product Officer
Posts: 32239
Liked: 7603 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Object Storage User Agent Version

Post by Gostev » 1 person likes this post

veremin wrote: Feb 14, 2025 3:52 pmThe exact reasons for this decision are hard to recall now, given how long ago it was made.
I remember the reason: changing user agent would mess up consumption reporting we get from the Azure side for months. And since we're releasing new minor releases every few months, we would end up with no reliable reporting... permanently :)

I don't know how important is this reporting these days, but it was extremely important for the company in the early days of object storage adoption.
Post Reply

Who is online

Users browsing this forum: Baidu [Spider] and 11 guests