-
Notifications
You must be signed in to change notification settings - Fork 79
a new exporter without a location returns an error about setting default location #164
Comments
I just noticed this too. I am using the Agent to export to Stackdriver and, when I saw the error, reconfigured my client to use the Stackdriver exporter directly. Since the agent uses the same code, it's unsurprising that both fail. Curiously, I do have some measurements recorded to Stackdriver so, somehow -- and I don't understand how -- I had this working albeit briefly. |
What's curious is that it's looking for When I deployed the agent to a GCE VM, it incorrectly (because it's using this metadata link) binds to the VM's zone:
So, it's both ignoring my specified
See comment below: the error is confusing but accurate. It is setting the |
Adding sd, err := stackdriver.NewExporter(stackdriver.Options{
ProjectID: "...",
Location: "us-west1-c",
}) But:
|
It is misleading to print that message when it is not running on GCE. @odeke-em , @DazWilkin it should still continue to export the metrics/traces without location. Does it not? Agent does not inject resource labels but it simply forwards those it receives from the client. |
I think so. Confirming now. I think this was a red-herring error for another issue that my client has. |
Yes, measurements are being reported by Stackdriver. |
Given code that used to work in the past
I get back an unexpected error
I believe we should only be trying to find a default location if we are on GCE and in the past we've been able to run this exporter on local computers or even on other clouds.
The text was updated successfully, but these errors were encountered: