profile
viewpoint
Matthias Rampke matthiasr SoundCloud Berlin, Germany http://rampke.de/

erlehmann/fickileaks 14

Whistleblowjobplattform

matthiasr/logformat 5

converts zweipktfkts IRC plaintext logs to HTML5

matthiasr/kubernetes-config 4

Various configuration, Dockerfiles, and RC/service definitions for Kubernetes

matthiasr/melt 4

mkhybrid+cdrecord frontend for BeOS R5. needs fixing to run on Haiku. Original coding by Lukas F. Hartmann

matthiasr/irclogs 3

Parse and beautify IRC/irssi logs

matthiasr/de-DE-multi 2

Old and new german dictionary for Firefox/Thunderbird etc. spellchecker

matthiasr/7XX-rfc 1

An RFC for a new series of HTTP status codes covering developer fouls.

matthiasr/abiword-macports 1

updated Portfile for AbiWord 2.8.x on Mac

matthiasr/audiofile 1

Audio File Library

matthiasr/autoscaler 1

Autoscaling components for Kubernetes

startednascheme/durus

started time in 12 hours

starteditsFrank/MinecraftHDL

started time in 20 hours

startedmatthiasr/autoscaler

started time in a day

startedFEX-Emu/FEX

started time in 4 days

issue openedprometheus/statsd_exporter

Any configuration option to turn off aggregations on statsd timers ?

I'm trying to hook statsite as an upstream service from which the exporter receives statsistics. For now, I want to relay the metrics as is to prometheus without aggregating the timers in statsd format. Is it possible to do this ?

created time in 5 days

PR opened prometheus/statsd_exporter

Pass around custom registry for registering exporter metrics

Importers of pkg/exporter may not want for series to be imported into the default registry. This PR makes it possible to provide a custom registry for metrics registration.

Signed-off-by: Robert Fratto robertfratto@gmail.com

+81 -65

0 comment

8 changed files

pr created time in 5 days

issue openedprometheus/influxdb_exporter

How should I set the address of the influxDB for listening

This Exporter is used to collect monitoring data points for influxDB. I have searched for a lot of documents but I haven't found out how to set up the address for influxDB. Could you please tell me how I can set up?

created time in 5 days

created repositoryregular/tre-cli-about

created time in 6 days

startedt-oster/VisiCut

started time in 7 days

issue commentprometheus/statsd_exporter

Allow specification of histogram buckets from client

Sorry, we kind of fell off on this. Our use case is as follows:

We're using this exporter because PHP doesn't have a great solution for exporters due to it's lack of a central thread. We're working with a fairly legacy monolith, so there's a wide variety of metrics we are trying to export. Our PHP application is handling a variety of process models, from web requests to long running data pipelines to medium length cron-like tasks, which speaks to the variety of metrics and timeframes we are handling. The current workflow for deciding on buckets relies on having intricate knowledge of the metric pipeline. Our workflow for histograms is... A) Write your code that ships statsd metrics out from the PHP application B) Create the statsd exporter bucket definitions in the statsd exporter

All in all, not the worst, but it does mean that every engineer who wants to ship timing data needs to have decently in depth knowledge about the configuration of the statsd exporter application, which can get painful when you have hundreds of engineers who need to at some point do this.

Meanwhile, we have a growing collection of services that are based in languages that more natively support prometheus exporters and allow all of the definition of exported metrics to be done in the application itself. These applications have a much lower barrier to entry for adding metrics, and engineers are much happier to engage with exporting metrics.

We would like to bring our PHP metric exporting to be as similar to the models of the more strongly supported languages (aka golang) as we can manage, which led us to this idea: Specifying histogram buckets from the requester instead of the server.

SpencerMalone

comment created time in 8 days

startedspatie/data-transfer-object

started time in 9 days

startedspatie/phpunit-snapshot-assertions

started time in 9 days

startedphpstan/phpstan-strict-rules

started time in 12 days

startedthenexxuz/cups-epilog

started time in 12 days

PR opened prometheus/promu

Explicitly specify promu binary name and path config

This commit makes it so the make build target will not rely on the default behaviour for guessing promu's binary name and path when building promu with promu.

This is useful when the repo dir name is not promu (e.g. in a fork). Without this change the binary that is built would be named after the repo root directory's name, which may be unexpected. With this change the built binary will always be names promu.

+3 -0

0 comment

1 changed file

pr created time in 12 days

issue commentprometheus/statsd_exporter

statsd_exporter OOM (out of memory)

It looks like you are creating lots of new metrics since the label key is random. Since each metric is the combination of metric name and label keys/values, lots of summary objects are created, which consume all the space. This is expected, and should be fixed by removing cardinality from the labels.

Can you confirm if there is unbounded cardinality in the labels of your production instance?

You can view the pprof with the following command:

go tool pprof -web pprof.statsd_exporter.alloc_objects.alloc_space.inuse_objects.inuse_space.009.pb
Vytiss

comment created time in 14 days

issue closedprometheus/graphite_exporter

Unable to report to Graphite java.net.SocketException: Broken pipe

My application offers monitoring on http://localhost:80/1.0/metrics. Unfortunately it does not include prometheus. So in oder to be able to store monitoring data into prometheus I'm using graphite_exporter. Enable my application metrics to sink to Graphite: catalina.properties:

metrics.graphite=true
metrics.graphite.host=graphite_host
metrics.graphite.port=9108

However, the application is assigned the host and port correctly and I'm able to telnet on port 9108. The issue unable to send metrics to graphite-exporter:

2020-11-10T13:57:33,354+0000 lvl='WARN', log='GraphiteReporter', th='metrics-graphite-reporter-1-thread-1', xff='', rId='', tok='', aRId='', tRId='', Unable to report to Graphite
java.net.SocketException: Broken pipe (Write failed)
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
	at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
	at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)
	at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125)
	at java.io.OutputStreamWriter.write(OutputStreamWriter.java:207)
	at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:129)
	at java.io.BufferedWriter.write(BufferedWriter.java:230)
	at java.io.Writer.write(Writer.java:157)
	at com.codahale.metrics.graphite.Graphite.send(Graphite.java:138)
	at com.codahale.metrics.graphite.GraphiteReporter.sendIfEnabled(GraphiteReporter.java:328)
	at com.codahale.metrics.graphite.GraphiteReporter.reportTimer(GraphiteReporter.java:292)
	at com.codahale.metrics.graphite.GraphiteReporter.report(GraphiteReporter.java:259)
	at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:251)
	at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReporter.java:174)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

What is the problem?

closed time in 14 days

Bashayr29

issue openedprometheus/graphite_exporter

Unable to report to Graphite java.net.SocketException: Broken pipe

My application offers monitoring on http://localhost:80/1.0/metrics. Unfortunately it does not include prometheus. So in oder to be able to store monitoring data into prometheus I'm using graphite_exporter. Enable my application metrics to sink to Graphite: catalina.properties:

metrics.graphite=true
metrics.graphite.host=graphite_host
metrics.graphite.port=9108

However, the application is assigned the host and port correctly and I'm able to telnet on port 9108. The issue unable to send metrics to graphite-exporter:

2020-11-10T13:57:33,354+0000 lvl='WARN', log='GraphiteReporter', th='metrics-graphite-reporter-1-thread-1', xff='', rId='', tok='', aRId='', tRId='', Unable to report to Graphite
java.net.SocketException: Broken pipe (Write failed)
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
	at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
	at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)
	at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125)
	at java.io.OutputStreamWriter.write(OutputStreamWriter.java:207)
	at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:129)
	at java.io.BufferedWriter.write(BufferedWriter.java:230)
	at java.io.Writer.write(Writer.java:157)
	at com.codahale.metrics.graphite.Graphite.send(Graphite.java:138)
	at com.codahale.metrics.graphite.GraphiteReporter.sendIfEnabled(GraphiteReporter.java:328)
	at com.codahale.metrics.graphite.GraphiteReporter.reportTimer(GraphiteReporter.java:292)
	at com.codahale.metrics.graphite.GraphiteReporter.report(GraphiteReporter.java:259)
	at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:251)
	at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReporter.java:174)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

What is the problem?

created time in 15 days

startedreitermarkus/automerge

started time in 16 days

startedYqnn/svg-path-editor

started time in 16 days

issue closedprometheus/graphite_exporter

the exporter does not support the Centos6.10?

I use the node_exporter-1.0.1.linux-amd64 on the Centos6.10. When I run the exporter on this service,it work and the logs is normal.But it can't be get by the prometheus,which whow the node's value is 0. eg: prometheus up{instance="10.0.0.1:9100",job="db"} | 0

closed time in 16 days

liheng0507

issue openedprometheus/graphite_exporter

the exporter does not support the Centos6.10?

I use the node_exporter-1.0.1.linux-amd64 on the Centos6.10. When I run the exporter on this service,it work and the logs is normal.But it can't be get by the prometheus,which whow the node's value is 0. eg: prometheus up{instance="10.0.0.1:9100",job="db"} | 0

created time in 16 days

pull request commentprometheus/statsd_exporter

Create SECURITY.md

Thanks for your PR. This is covered for the entire project at https://prometheus.io/docs/operating/security/

sergk-mambu

comment created time in 19 days

PR opened prometheus/statsd_exporter

Create SECURITY.md

Hi,

my current employer is going to use statsd_exporter in production environments. One of the requirements to an open source project to comply to strict security rules is to have a security policy adopted. Therefore I would like to propose this security policy for statsd_exporter which is based on a generic security policy recommended by GitHub.

+42 -0

0 comment

1 changed file

pr created time in 19 days

issue commentprometheus/influxdb_exporter

Error messages should have JSON format

Many thanks for the very quick solution. It is working fine.

AndiKu

comment created time in 20 days

create barnchprometheus/statsd_exporter

branch : repo_sync

created branch time in 21 days

PR opened prometheus/statsd_exporter

Synchronize common files from prometheus/prometheus

Propagating changes from prometheus/prometheus default branch.

+1 -1

0 comment

1 changed file

pr created time in 21 days

create barnchprometheus/influxdb_exporter

branch : repo_sync

created branch time in 21 days

PR opened prometheus/influxdb_exporter

Synchronize common files from prometheus/prometheus

Propagating changes from prometheus/prometheus default branch.

+1 -1

0 comment

1 changed file

pr created time in 21 days

more