prometheus

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

Hi @apache/skywalking-committers and contributors

SkyWalking INFRA e2e subproject is almost ready to release because this is for testing scope only, we could adopt it in the main repo based on commit IDs.

We are welcome everyone to join this and replace the existing Java Maven based e2e tests. The latest one should be much more friendly and m

https://github.com/heptiolabs/healthcheck

This will give us metric on healtcheck and more granularity on checks we want to have.

/cc @slim-bean @joe-elliott

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

Is your proposal related to a problem?

Replication is currently slow.

Describe the solution you'd like

tools bucket replicate could upload a few objects at a time instead of one by one

Describe alternatives you've considered

Copying the objects with some other tool but tools bucket replicate is way too convenient because you can use two completely different object st

Host operating system: output of uname -a

Linux sarbian 5.13.5-arch1-1 #1 SMP PREEMPT Sun, 25 Jul 2021 18:02:58 +0000 x86_64 GNU/Linux

node_exporter version: output of node_exporter --version

node_exporter, version 1.2.0 (branch: tarball, revision: 1.2.0)
build user: someone@builder
build date:
go version: go1.16.5
platform: linux/amd64

n

po-lint was useful when there was no tools like kubeconform (which we use in kube-prometheus project). And support for CRDs in kubernetes was at earlier stage. Right now po-lint seems like a largely unused code.

We would need to change docs at https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/user-guides/linting.md

Bug description

There seem to be more space between 'Application Metrics' and 'External Calls' compared to the space between 'External Calls' and 'Database Calls' on Macbook Air 13 inch model.

Expected behavior

The tabs should be evenly spac

In this document, following sentence has a typo,

# Register the intrumentation handlers (/metrics etc).

intrumentation -> instrumentation

# Register the instrumentation handlers (/metrics etc).

What happened?
I wanted to configure my kubeadm-like cluster to get monitored by prometheus-operator. I started using the following file:

apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
api:
  advertiseAddress: 192.168.1.173 (I changed the IP from here)
  bindPort: 6443
authorizationModes:
- Node
- RBAC
certificatesDir: /etc/kubernetes/pki
cloudProvider:

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...