Comments (5)
Hey Bruno,
A µ/log publisher for Prometheus.
Is this a typo?
Also it is easy enough to write InfluxDB data points without the java library. In my travels I have written a spec and a mapping function to produce InfluxDB line protocol:
https://gitlab.com/misterzirillo/plant-parenthood/-/blob/master/src/pp/device/metrics.cljs
Would some version of that code be a suitable implementation for this project?
from mulog.
Hi @misterzirillo,
thanks for spotting the typo, probably a copy/paste issue.
Thanks also for pointing out the line protocol, it is easy enough
that we don't need a Java wrapper for it. So definitely your approach
could be suitable.
The only issue is that InfluxDB is designed to store
measurements/metrics (not events), therefore it will be required to
turn the events intro metrics before publishing them.
We have done something similar for Prometheus:
However, the InfluxDB model is closer to μ/log model, so it should be easier.
Probably, only we have to do is separate numerical pairs from string pairs
and turn the numerical into fields and the string pairs into tags.
For example an event such as:
{:mulog/event-name :db/store-records
:mulog/timestamp 1587504242983,
:mulog/trace-id #mulog/flake "4VTF9QBbnef57vxVy-b4uKzh7dG7r7y4",
:mulog/root-trace #mulog/flake "4VTF9QBbnef57vxVy-b4uKzh7dG7r7y4",
:mulog/duration 254402837,
:mulog/namespace "your-ns",
:mulog/outcome :ok,
:app-name "mulog-demo",
:env "local",
:version "0.1.0"
:num-items 123}
could be stored as follow:
:mulog/event-name -> measurementName
:mulog/timestamp -> timestamp
:mulog/duration -> field
:num-items 123 -> field
:mulog/namespace -> label
:mulog/outcome -> label
:app-name -> label
:env -> label
:version -> label
I'm not sure whether there is any value on storing the trace-id
into
InfluxDB (what's your thoughts on this?) but it could be added as an
extra label.
from mulog.
Probably, only we have to do is separate numerical pairs from string pairs
and turn the numerical into fields and the string pairs into tags.
This is my intuition as well. I think with that basic rule we a pretty solid out-of-the-box behavior for the InfluxDB publisher.
I'm not sure whether there is any value on storing the trace-id into
InfluxDB (what's your thoughts on this?) but it could be added as an
extra label.
It depends on how strict μ/log is about recording the whole event. There are performance reasons that an InfuxDB user might want to store a subset of the event data or change which data are stored as tags/fields. How much control do you think the publisher should allow the user over the transformation?
from mulog.
It depends on how strict μ/log is about recording the whole event. There are performance reasons that an InfuxDB user might want to store a subset of the event data or change which data are stored as tags/fields. How much control do you think the publisher should allow the user over the transformation?
On second thought, the trace-id
could be useful to avoid duplicates in case of publisher failures.
In regards to the control, the users have the ability to manipulate events at will before the publishing,
so I would say that the users have full control on the shape of the data published.
from mulog.
This issue seems stale and not sure anyone requires InfluxDB.
So closing issue.
from mulog.
Related Issues (20)
- Character code for `µ` HOT 2
- Does mulog publisher for zipkin support Annotations? HOT 1
- Extract file/line info from callsites?
- µ/log publisher for OpenTelemetry HOT 6
- Logging maps HOT 7
- Merge map keys into µ/log statement HOT 2
- Add payload length to the zipkin publisher HOT 1
- AWS Cloudwatch logs are not generally "discoverable" HOT 2
- Publish errors with Cloudwatch Logs HOT 8
- Slack Publisher Documentation implies support for Block Kit messages HOT 1
- Errors serializing to JSON are unreasonably difficult to debug HOT 2
- Publishers continually retrying HOT 3
- Silent failure with trace and :capture HOT 1
- Trace stopped publishing to zipkin HOT 13
- µ/log and µ/trace should accept a logger HOT 2
- duplicate log entries HOT 6
- Trace with interceptors? HOT 5
- CloudWatch Publisher: error when transform function returns no events HOT 2
- Programatically obtain current `:mulog/trace-id` HOT 2
- Put event name in options map HOT 1
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 mulog.