#440 make click-to-launch-in-EC2 button something that we can log
Closed: Fixed Opened by mattdm.

Right now, we don't have very good statistics about whether the deploy-to-cloud button is being used. As I understand it, the current implementation just presents a bare link which we can't easily log. I don't want invasive tracking or anything, just a count of how many launches there have been (analogous to counting downloads). Could we make the button link to a redirect which we can then count?


still would be nice to have. thanks!

We need to work on this together with the Infra team. I guess the ticket for this is already open, adding it here for all the others:

https://fedorahosted.org/fedora-infrastructure/ticket/3893

If we were allowed to use a server-side language I'm sure we could make something for it quickly

I think server-side processing is probably overkill -- it really just needs to be a redirect.

PS: this'd be awesome to see for F22 web redesign, if possible.

The basic thing is that we need to URLs that are clicked to be Fedora URLs, which then redirect to the real target URLs.

Well, that makes sense, but how are you going to store the statistics? We either have to use a third party or write our own server-side script.

I think we can use a redirect rule on our varnish proxy such that anything like http://theoreticalredirectserver.fedoraproject.org/redirect/console.aws.amazon.com/ec2/v2/home?region=us-east-1#LaunchInstanceWizard:ami=ami-21362b48 would be redirected to https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#LaunchInstanceWizard:ami=ami-21362b48

The clicks on that first link would be logged with our normal web logs and could be analyzed.

OK, the redirect is ready:

{{{
$ curl -I https://redirect.fedoraproject.org/console.aws.amazon.com/ec2/v2/home\?region\=us-east-1#LaunchInstanceWizard:ami\=ami-21362b48
HTTP/1.1 302 Found
Date: Thu, 06 Nov 2014 16:39:01 GMT
Server: Apache/2.2.15 (Red Hat)
Location: https://console.aws.amazon.com/ec2/v2/home?region=us-east-1
Content-Type: text/html; charset=iso-8859-1
}}}

Thanks Ralph!

Oop, although I see now the fragment identifier is not taken along for the ride yet. :(

Replying to [comment:10 ralph]:

Oop, although I see now the fragment identifier is not taken along for the ride yet. :(

Nevermind this - browsers seem to handle it correctly.

Okay so didn't make the release web site (ah well). Websites team, do you think we can do this as an update?

Yes we can! Let's see if we get this working :)

Websites updated, all EC2 links now go through the redirect alias. See ref. e8b3c55.

Metadata