So this ingestion got stopped or crashed, at some point.
Probably around the db outage from last week (which emptied the rabbitmq queue).
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 27 2021
Replicating the comment from T3500:
Postfix alert installed so next time, we should be able to be made aware ;)
Closing now.
There, some illegitimate alerts about smart error on vms were raised.
That's really nice, but I still prefer the minimalist first iframe :-)
s/Mb/MB/
(elsewhere: giverny is still on stretch, so the package needs to be made to exist there)
(elsewhere: giverny is still on stretch, so the package needs to be made to exist there)
This is not needed.
The issue lies elsewhere.
nit: 5MB, not 5Mb
And I triggered re-cooking bundles that were requested in the last month.
Add comment
thanks. I will test that once the monitoring is updated to use the statsd statistics instead of the object_count table content.
Build is green
rebase + squash + add tests
Build is green
rebase
Got deployed. Some more alerts are raised now. Some legitimate, some others are errors
in the deployment.
Yeah SWHIDs are long so they eat a lot of horizontal space.
Build is green
Looks better with the first implementation with "Go to the archive" :-)
With the badge, it seems right and left side aren't balanced.
apply comments
Build is green
Build is green
Build is green
Landed through ad85a394 (forgot to update the diff apparently).
Build is green
Use --only-enabled and --only-disabled as mentioned yesterday
- Rebase on top of latest master
- Adapt according to remarks
rebase + fix typos
Rebase
couple of typos inline.
the lz4 compression was already activated by default. Changing the algo to zstd on the table snapshot was not really significant (initially with lz4: 7Go, zstd: 12Go, go back to lz4: 9Go :) )
The one thing that is missing is the current SWHID I’m viewing.
Maybe use a SWHID (or a badge) instead of the path in the center of the panel… or as a footer like a reference…
Not sure about this, but we need to know what artifact is identified in the iframe.