Git Product home page Git Product logo

Comments (7)

brancz avatar brancz commented on July 28, 2024

My personal opinion is that your environment should take care of this. There are infinite amounts of solutions that could be supported, but all of them can be used with little to no extra tooling around Prometheus.

from common.

brian-brazil avatar brian-brazil commented on July 28, 2024

I agree with @brancz.

from common.

grobie avatar grobie commented on July 28, 2024

@mdlayher @cagedmantis I believe DigitalOcean relies heavily on syslog in the logging infrastructure. How do you deal with applications which only log to stdout? Anything which would make it impossible to use a wrapper to write the log stream to syslog instead?

@carlpett You added the EventLog back then for the wmi_exporter. I assume the wmi_exporter could just use implement its own logger for that? Do you run Prometheus on Windows as well? Do you see any issues writing to stdout only?

from common.

mdlayher avatar mdlayher commented on July 28, 2024

Pinging @taotetek about the logging question. I imagine we are able to just capture stdout but our internal structured logger has syslog support too, though I'd also rather have an external process be responsible for that.

from common.

carlpett avatar carlpett commented on July 28, 2024

@grobie We could implement it ourselves, yes.
We're not running the Prometheus server on Windows in my organisation, but I've heard that there are people elsewhere who do. Since there is no Windows Service support built in to Prometheus (there is an API that needs to be implemented in order to run as a service), anyone who does will need to have implemented some form of wrapper, and that wrapper should be able to handle output redirection. So I do not think that case is a problem.

from common.

fabxc avatar fabxc commented on July 28, 2024

From what I could see, our syslog sink was best-effort at best. It comes with its own various config parameters and we made some effort to map log levels etc. to those – but I don't think that was necessarily the only sane way to do it.

from common.

grobie avatar grobie commented on July 28, 2024

Alright, let's not do this for now.

If someone comes up with critical reason why any of these sinks can only be sanely implemented here and not as a wrapper, please open this issue again and we can discuss.

from common.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.