Comments (4)
From containerd/containerd#6639:
Example policies that a custom log plugin might enforce include:
Log data is pre-processed to remove potentially sensitive information (e.g. via https://github.com/stripe/unilog)
Pre-processed log data is not allowed to be written to persistent disk.
Log lines may be persisted to remote storage at different sampling levels depending on content.
learned a little bit more about how binary loggers should work: they are expected to be called, and piping I/O in to the custom logger. An example the logger is in containerd/containerd#3085
from runwasi.
What's the main benefits of supporting Binary logging?
from runwasi.
the main benefit of binary logging is that you can do highly structured snapshots and various other customized things to not only compress but treat the log as a kind of database. So, for example, systemd and mysql (in fact, almost every db or db service) uses binary logging. Size is not the main concern, but "structured responsiveness".
outside of that, you can just compress the text log if size is your only concern (though ongoing size is typically smaller with binary).
In this case, we have a Windows customer who needs this to make runwasi a "drop-in" replacement for the current shim.
from runwasi.
Yeah sounds good. Perhaps this issue belongs to rust-extensions repo, though?
from runwasi.
Related Issues (20)
- compile-error HOT 3
- Missmatch docs and build HOT 2
- Adding containerd config options for the shim HOT 7
- "no unpack platforms defined: invalid argument" happens when `make load` HOT 2
- update youki to v0.3.3 to pick up the changes that remove `chdir`
- Consider making the Tracing support optional in the shims
- All bench tests are "Ignored"
- add comparison to the normal containers
- add empty wasm module to test the start up time for each shim
- try running hunderds of containers at once to see how "dense" containers on a node would perform
- look into grafana and prometheous for monitoring the CPU, memory, disk, etc. usage of runwasi
- Where do we define the Wasm "container" boundry HOT 8
- Support benchmarking charts on GitHub Pages
- Consider ways to optimize the benchmakring performance
- CI: Consider adding GitHub Artifact Attestations to the release CI
- Enable benchmarking for WasmEdge
- ctr: failed to create shim task, wasmtime can't handle spec? HOT 2
- Problem when trying to use Runwasi + WasmEdge over Kind and Docker Image HOT 5
- instability in e2e tests
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from runwasi.