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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is currently a draft PR to make the PowerHog data upload usable again.
It was deactivated as we were seeing regular errors.
It has now been deactivated with some learnings. More are to come in this PR.
Learnings
PowerHog is posting often frames larger than 1 MB
NGINX POST body size was increased to 3 MB. Not too large to block the server, but a bit of headroom
For reasons unknown many requests where issued to GET /v1/hog/add. Since we monitor 404s this was clogging up our logs. I have deactivated the route for now ... but why is this happening?
🌳 CO2 Data:
City: Chicago, Lat: 41.8874, Lon: -87.6318
IP: 172.183.76.129
CO₂ from energy is: 0.585173780 g
CO₂ from manufacturing (embodied carbon) is: 0.118975858 g Carbon Intensity for this location: 361 gCO₂eq/kWh SCI: 0.704150 gCO₂eq / pipeline run emitted
ArneTR
linked an issue
Sep 16, 2024
that may be
closed
by this pull request
Large uploads:
We limit the upload to 10 rows [0] which I found to be under 1MB. This could have increased over time the more apps are running. Setting the upload to 3MB seems like a good solution
Access to GET /v1/hog/add.
I can not explain why this is happening. The upload is with POST [1]. Do you see some correlation in the log files? What IPs are the GET requests coming from?
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is currently a draft PR to make the PowerHog data upload usable again.
It was deactivated as we were seeing regular errors.
It has now been deactivated with some learnings. More are to come in this PR.
Learnings
GET /v1/hog/add. Since we monitor 404s this was clogging up our logs. I have deactivated the route for now ... but why is this happening?