Comments (3)
Hi @Ergamon 👋
We actually don't have a nice way to do this currently. Seq's CLI has this concept of extraction patterns that would be a good fit for this. We don't have a Rust implementation of them yet but I think this sounds like a great addition.
from seq-input-gelf.
Thanks for your quick reply. At least I now know that I have not overlooked something ;)
Intitially I had thought about some regex replace mechanism, but what you showed is also fine.
As every container has its own "logging syntax" it cannot be something hard wired in the gelf server.
If I could wish for this new feature, my idea would be to have some label on the container for the extraction pattern.
So server side I would configure the name of the label for the pattern, which is then not send to the seq.
On the container side I would have to add the label and add the label to the logging options for gelf.
from seq-input-gelf.
Coming back to this, the way you could do this today would be through something like fluentbit, which lets you transform and reshape your logs between their producer and the eventual consumer. In the future we might consider some similar data pipelining functionality in Seq itself, but don't have any immediate plans for it.
This would be great to support, but having thought about it I think we should avoid accumulating these sorts of configurable transformations in the GELF input itself.
Thanks again for the suggestion @Ergamon!
from seq-input-gelf.
Related Issues (20)
- Ingestion failed: Invalid URI: The URI scheme is not valid. HOT 3
- Spurious error logs when diagnostics enabled with TLS HOT 2
- control charater found while parsing a string HOT 1
- invalid unicode code point ? HOT 5
- select another timestamp key HOT 2
- Filter out "Empty" information messages HOT 2
- bin/sqelf: No such file or directory HOT 3
- The App Process is Stopped HOT 1
- Connection to Seq using gelf refusing HOT 1
- Add HTTP support HOT 2
- High memory consumption HOT 1
- All events from Docker Imported as Error Level in Seq HOT 6
- Add support for docker secrets HOT 2
- Nothing being received in Seq? (Laravel / Gelf / Seq) HOT 5
- GELF processing failed HOT 8
- sqelf in Docker doesn't listen on 12201/TCP HOT 4
- "GELF processing failed irrecoverably" stops the receiver HOT 7
- ARM64 container for seq-input-gelf HOT 7
- "No template provided" HOT 14
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 seq-input-gelf.