You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are seeing repeated open telemetry errors in the project logs.
I should say that this may be because of our usage, we don't directly trigger on the object finalised event, instead we have a function that triggers on this and passes the eventarc message to the cloud run instance separately.
Version: v3.1.1
I've not been able to determine if we see the same in v3.2 as we had to roll back
{
"stack": "Error: PeriodicExportingMetricReader: metrics export failed (error Error: Send TimeSeries failed: One or more TimeSeries could not be written: timeSeries[4]: Field timeSeries[4].points[0].value had an invalid value: A point has an unrecognized value type.; timeSeries[3]: Field timeSeries[3].points[0].value had an invalid value: A point has an unrecognized value type.; timeSeries[5]: Field timeSeries[5].points[0].value had an invalid value: A point has an unrecognized value type.)\n at PeriodicExportingMetricReader._doRun (/app/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:83:19)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async PeriodicExportingMetricReader._runOnce (/app/node_modules/@opentelemetry/sdk-metrics/build/src/export/PeriodicExportingMetricReader.js:54:13)",
"message": "PeriodicExportingMetricReader: metrics export failed (error Error: Send TimeSeries failed: One or more TimeSeries could not be written: timeSeries[4]: Field timeSeries[4].points[0].value had an invalid value: A point has an unrecognized value type.; timeSeries[3]: Field timeSeries[3].points[0].value had an invalid value: A point has an unrecognized value type.; timeSeries[5]: Field timeSeries[5].points[0].value had an invalid value: A point has an unrecognized value type.)",
"name": "Error"
}
The text was updated successfully, but these errors were encountered:
We are seeing repeated open telemetry errors in the project logs.
I should say that this may be because of our usage, we don't directly trigger on the object finalised event, instead we have a function that triggers on this and passes the eventarc message to the cloud run instance separately.
Version: v3.1.1
I've not been able to determine if we see the same in
v3.2
as we had to roll backThe text was updated successfully, but these errors were encountered: