Add me to the list of people who is frustrated by not being able to clearly explain to clients why Pantheon is reporting a magnitude greater level of traffic than anywhere else – and wants to bump them to the next plan level, which can be a whopping 70%-100% increase in price. When I asked support for help in figuring out why Pantheon’s metrics show a huge spike in Dec and Jan (even though GA does not), it took 28 days and multiple requests for them to get back to me – with an analysis of just one day in Feb.
If that one day is indicative, then maybe the problem is that bots are continually trying to access different URLs with “wp-login.php” in them – even though it’s a Drupal site. Isn’t there a simple rule that Pantheon can put in place to block these sorts of requests on Drupal sites?
It’s embarrassing because the client wants to know what’s going on and is concerned about a 70% increase in hosting costs they didn’t budget for, and all I can tell them is I’m going to have to spend billable hours playing whack-a-mole with bots using an incomplete set of logs.
One of the original benefits of Pantheon – which I touted to clients when convincing them to migrate over from other hosting options – was being able to focus on building a great Drupal site rather than spending hours on low-level sysadmin tasks like this.
I already had one client switch to a Pantheon competitor after the new traffic rules, and now this client is asking the same question. In both cases, I brought these clients to Pantheon years ago.
I really hope you can take a hard look at whether this is the right way to bill for hosting, whether the price jumps are justified, whether your support staff has the tools they need to help when questions about traffic come up, and whether you’re providing developers with tools to make their jobs easier, not harder.