Closed cirocosta closed 4 years ago
Hey,
Since the upgrade to 1.15 (see https://github.com/concourse/hush-house/issues/95), we end up with no metrics coming to the (web|worker) errors dashboards:
(web|worker) errors
It turns out that when moving from Kubernetes 1.14.x to 1.15.x (GKE), we end up losing support for what's now called Legacy stackdriver (which is what collects our logs and turns them into web/worker errors in our dashboards).
(from https://cloud.google.com/monitoring/kubernetes-engine/)
It seems like to get the new Stackdriver we need to first disable legacy, and then enable the new one:
That's something we might / might not be able to do right from Terraform
https://github.com/concourse/hush-house/blob/a3f7662a65cc32ea0de47e31851e577564455a4a/terraform/cluster/main.tf#L17-L19
although I'm not completely sure.
Thanks!
aaand .. it's active!
as we can't get the legacy even if we wanted to, there's no need to have that in terraform.
Hey,
Since the upgrade to 1.15 (see https://github.com/concourse/hush-house/issues/95), we end up with no metrics coming to the
(web|worker) errors
dashboards:It turns out that when moving from Kubernetes 1.14.x to 1.15.x (GKE), we end up losing support for what's now called Legacy stackdriver (which is what collects our logs and turns them into web/worker errors in our dashboards).
(from https://cloud.google.com/monitoring/kubernetes-engine/)
It seems like to get the new Stackdriver we need to first disable legacy, and then enable the new one:
That's something we might / might not be able to do right from Terraform
https://github.com/concourse/hush-house/blob/a3f7662a65cc32ea0de47e31851e577564455a4a/terraform/cluster/main.tf#L17-L19
although I'm not completely sure.
Thanks!