The [Prometheus] monitoring tool follows a white-box monitoring approach: Applications actively provide metrics about their internal state, and the Prometheus server pulls these metrics from the applications using HTTP.

If you can modify the application’s source code, it is straightforward to instrument an application with Prometheus metrics: Add the Prometheus client library as a dependency, call that library to maintain the metrics, and use the library to expose the metrics via HTTP.

However, DevOps teams do not always have the option to modify the source code of the applications they are running.

At this year’s [JavaZone] conference, Fabian Stäber did a [talk] on how to instrument Java Web Applications with Prometheus metrics without modifying the application’s source code.

weiterlesen...

At this year’s [FOSDEM] conference I did a 30 minutes presentation on [Monitoring Legacy Java Applications with Prometheus]. The talk gives an overview of some of the options you have for monitoring Java applications with [Prometheus] when you cannot modify the application’s source code:

• Logfile monitoring ([grok_exporter]), and how it differs from [Elastic stack]
• Blackbox monitoring ([blackbox_exporter])
• JMX ([jmx_exporter])
• Write your own Java agent ([promagent.io])

The video is available below.

weiterlesen...

The [Prometheus] monitoring tool follows a white-box monitoring approach: Applications actively provide metrics about their internal state to the Prometheus server. In order to instrument an application with Prometheus metrics, you have to add a metrics library and call that library in the application’s source code. However, DevOps teams do not always have the option to modify the source code of the applications they are running.

At this year’s [Devoxx] conference, Fabian Stäber did a [talk] on how to instrument Java Web Applications with Prometheus metrics without modifying the application’s source code.

weiterlesen...

At this year’s [FOSDEM] conference I did a 20 minutes presentation on how to implement tail -f in [Go]. The video is available below.

Abstract: As part of a log file monitoring tool, I implemented a file tailer that keeps reading new lines from log files. This turned out to be much more challenging than I thought, especially because it should run on multiple operating systems and it should be robust against logrotate. In this 20 Minutes talk I will present the lessons learned, the pitfalls and dead-ends I ran into.

weiterlesen...

[Prometheus] is an open source monitoring tool, which is conceptually based on Google’s internal Borgmon monitoring system. Unlike traditional tools like Nagios, Prometheus implements a white-box monitoring approach: Applications actively provide metrics, these metrics are stored in a time-series database, the time-series data is used as a source for generating alerts. Prometheus comes with a powerful query language allowing for statistical evaluation of metrics.

weiterlesen...

Mit seinem Vortrag “Containerized End-2-End-Testing” war Tobi am 31.08. als Redner beim [Herbstcampus] 2016 in Nürnberg.

weiterlesen...

Fabian and Christoph have been invited to speak at [Devoxx Conference] 2016 in Antwerp, Belgium. Watch their talks to learn more about HTTP2 and Citrus Framework.

weiterlesen...

Wem meine Folien zum Thema Netzwerkmonitoring mit check_nwc_health zu trocken sind kann sich meinen Vortrag auch als Video anschauen. Film ab!

Vorgestern habe ich auf der diesjährigen Open-Source-Monitoring-Konferenz in Nürnberg einen Vortrag über check_nwc_health gehalten.
Hier sind die Folien für diejenigen, die das Pech hatten, nicht dabei zu sein (damit meine ich die Konferenz an sich, nicht meinen Vortrag)

Here are the links I mentioned in my Devoxx Tools-in-Action Talk “Jolokia - JMX on Capsaicin”. Most of the pointers can of course be reached by starting at www.jolokia.org

weiterlesen...