Being excited about the new value to text available in tables I just pulled release 5.1 for windows.
wget https://s3-us-west-2.amazonaws.com/grafana-releases/release/grafana-5.1.0.windows-x64.zip
Alas, it appears the actual package is version 5.0.0.
The configuration page shows 5.0.0 (I was on 5.0.4 previously). See attached screenshot.
I was hoping perhaps maybe just the version text was wrong, but no value to text options in my tables either.
Hi,
That’s weird. Could you give us some more information? Like grafana server log output. Have you for example tried if the new value to text mapping is included - in that case we have some problem with the versioning for the windows build. Thanks
Marcus
Update:
So it is actually the correct version, despite the wrong display value.
And to get to value to text you need to change the type to “String” instead of number. I found this a little counter intuitive given my value is a numeric value, but otherwise works nicely. This had initially made me think the new feature wasn’t available because I had my column as a “Number” type.
Here is a log output on server startup:
t=2018-04-26T13:53:10-0600 lvl=info msg=“Starting Grafana” logger=server version=5.0.0 commit=NA compiled=2018-04-26T13:53:10-0600
t=2018-04-26T13:53:10-0600 lvl=info msg=“Config loaded from” logger=settings file=C:\grafana-5.1.0/conf/defaults.ini
t=2018-04-26T13:53:10-0600 lvl=info msg=“Path Home” logger=settings path=C:\grafana-5.1.0
t=2018-04-26T13:53:10-0600 lvl=info msg=“Path Data” logger=settings path=C:\grafana-5.1.0\data
t=2018-04-26T13:53:10-0600 lvl=info msg=“Path Logs” logger=settings path=C:\grafana-5.1.0\data\log
t=2018-04-26T13:53:10-0600 lvl=info msg=“Path Plugins” logger=settings path=C:\grafana-5.1.0\data\plugins
t=2018-04-26T13:53:10-0600 lvl=info msg=“Path Provisioning” logger=settings path=C:\grafana-5.1.0\conf\provisioning
t=2018-04-26T13:53:10-0600 lvl=info msg=“App mode production” logger=settings
t=2018-04-26T13:53:10-0600 lvl=info msg=“Initializing DB” logger=sqlstore dbtype=sqlite3
t=2018-04-26T13:53:10-0600 lvl=info msg=“Starting DB migration” logger=migrator
t=2018-04-26T13:53:10-0600 lvl=info msg=“Executing migration” logger=migrator id=“copy data account to org”
t=2018-04-26T13:53:10-0600 lvl=info msg=“Skipping migration condition not fulfilled” logger=migrator id=“copy data account to org”
t=2018-04-26T13:53:10-0600 lvl=info msg=“Executing migration” logger=migrator id=“copy data account_user to org_user”
t=2018-04-26T13:53:10-0600 lvl=info msg=“Skipping migration condition not fulfilled” logger=migrator id=“copy data account_user to org_user”
t=2018-04-26T13:53:10-0600 lvl=info msg=“Starting plugin search” logger=plugins
t=2018-04-26T13:53:10-0600 lvl=info msg=“Initializing Alerting” logger=alerting.engine
t=2018-04-26T13:53:10-0600 lvl=info msg=“Initializing CleanUpService” logger=cleanup
t=2018-04-26T13:53:10-0600 lvl=info msg=“Initializing Stream Manager”
t=2018-04-26T13:53:10-0600 lvl=info msg=“Initializing HTTP Server” logger=http.server address=0.0.0.0:3000 protocol=http subUrl= socket=
Notice the incorrect version of 5.0.0 there as well.
Thanks for confirming. Will put out a fix for this tomorrow.
Marcus
Has this been fixed yet? I’ve just compiled version 5.3.0 and it’s still showing 5.0.0:
t=2018-10-10T13:55:32+0000 lvl=info msg=“Starting Grafana” logger=server version=5.0.0 commit=NA compiled=2018-10-10T13:55:32+0000
Was fixed in v5.1.1 for appveyor, see changelog.
Make sure you’re using a correct GO path, i.e. try using a capital drive letter in GO path like we did to fix above initial problem.
Interesting. I’m building it inside a vagrant box using fpm cookery on CentOS 7.
So you’re not building on Windows? Are you using go version 1.11?
No, it’s using golang version 1.10.3. I believe it was an issue for us since Grafana 5.0.0 came out.
EDIT: Scratch that, yes it’s using 1.11.1.
EDIT 2: Think there might be an issue with our build process somewhere as it does show the version on the built one, but once packaged and installed elsewhere it… doesn’t? Anyway, think the problem is on our side. My apologies for completely missing the “Windows” bit in this subject too!
Okay 
No worries, just create a new topic if there should be any other problem not already reported in other topic.