prometheus

Bug description

netdatacli has limit for output size of 4096

Expected behavior

do we just increase this limit or make it transfer arbitrary message sizes?

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

We should provide multi-architecture Docker images of skywalking-eyes, just like other SkyWalking sub-projects.

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• [

Currently promtail supports reading logs from a Kafka topic, and write out to a Loki installation.
The feature request is for promtail to have the ability to write logs to a Kafka cluster, the reason explained below.

Describe the solution you'd like
Kafka can be found in many organisations, and is often times used as a way to have a central place for information to flow through. This so

Is your proposal related to a problem?

Right now Thanos repo supports using Gitpod as a remote development environment. Similar to that, Github codespace is also a remote development environment that integrates be

Replace this parsers in node exporter with this ones from procfs.

It is not possible to define SecurityContext for Containers of Alermanager (only PodSecurityContext is available). Because of the missing Container SecurityContext it's not possible to setup important sec

Spent the morning debugging what I thought was a goroutine leak, but turned out to be just a huge number of goroutines being created in a short period of time. However, it seems a lot of the unit tests do leak goroutines. Most of these might just be issues with tests not cleaning up properly, but it makes testing/debugging real leaks quite difficult. Or in my case, the leaks were a red herring - t

README.md is still pointing to addons/strip-limits.libsonnet addon as a way to strip containers from set resource limits. However since release-0.8 resource requests are first-level settings and users should use

What happened:
I created a pod with a "com.acme/fooBar" label.
The l

What did you expect to see?

I'm expecting to be able to filter out the requests from blackbox exporter in my access logs.
So, please, add a user agent header that container the "blackbox exporter" string somewhere.

What did you see instead?

I see User-Agent: Go-http-client/1.1
Not easy to filter in the access logs...

• Success and failures
• Reasons
• How much does it take to finish a round?
• How much does it take to store the symbolized locations?