Open ntpct1993 opened 2 months ago
Got 502 error code when sending data to the opencensus metrics
Is this still occurring? There was an short outage of monitoring last week, but it does not seem to overlap with your issue.
I have deployed from head in a teat project, and the counters are working correctly.
502 is an internal sever error, which is not a permissions issue, and does imply something going wrong in cloud monitoring backend.
I do have a plan to replace the (deprecated) opencensus metrics library with its replacement - opentelemetry.
yes, it's still occurring.
However, I didnt find any 502 error from logs anymore. But still NO DATA
Hi,
As mentioned from the issue title, there is no data from all custom metrics. The rest (scanning stuff) are working fine for me - thank you for your work.
I added some debug logs in metrics.js to see what happened there and to make sure metrics.js was called. I'm sure that writeScanCleanMetric and writeScanInfectedMetric functions were called
writeScanCleanMetric ====== sourceBucket: phucnguyen-clamav-unscanned - destinationBucket: phucnguyen-clamav-unscanned - fileSize: 4 - scanDuration: 105 - clamVersion: ClamAV 1.0.5/27344/Mon Jul 22 08:26:31 2024
writeScanInfectedMetric ====== sourceBucket: <unscanned-bucket> - destinationBucket: <quarantined-bucket> - fileSize: 69 - scanDuration: 100 - clamVersion: ClamAV 1.0.5/27344/Mon Jul 22 08:26:31 2024
The initialization was OK also
"Starting ClamAV daemon: clamd {"severity":"INFO","level":30,"timestamp":{"seconds":1721708195,"nanos": 437000000},"pid":2612,"hostname":"localhost","serviceContext":{"service":"gcs-malware-scanner","version":"2.6.1"},"logging.googleapis.com/insertId":"..........6mnyAoxPtAB7AQqpV3.lw6","message":"Metrics initialized for malware-scanning/ on project <my_project>}"
However, there was nothing displayed from Metric explorer console page - all metrics are inactive
Please help me with this
FYI, I already granted the Metric Writer role for the cloudrun Service Account (malware-scanner@${PROJECT_ID}.iam.gserviceaccount.com)