cwielenb/CNCF-Dataset huggingface dataset:
Project: Netdata (Observability and Analysis / Observability)
File: load_average_1.md

This alarm calculates the system `load average` (`CPU` and `I/O` demand) over the period of one minute. If you receive this alarm, it means that your system is `overloaded`. The term `system load average` on a Linux machine, measures the number of threads that are currently working and those waiting to work (CPU, disk, uninterruptible locks). So simply stated: System load average measures the number of threads that aren't idle. Let's look at a single core CPU system and think of its core count as car lanes on a bridge. A car represents a process in this example: On a 0.5 load average, the traffic on the bridge is fine, it is at 50% of its capacity. If the load average is at 1, then the bridge is full, and it is utilized 100%. If the load average gets to 2 (remember we are on a single core machine), it means that there is one car lane that is passing the bridge. However, there is another full car lane that waits to pass the bridge. So this is how you can imagine CPU load, but keep in mind that `load average` counts also I/O demand, so there is an analogous example there. Determine if the problem is CPU load or I/O load To get a report about your system statistics, use `vmstat` (or `vmstat 1`, to set a delay between updates in seconds): The `procs` column, shows: r: The number of runnable processes (running or waiting for run time). b: The number of processes blocked waiting for I/O to complete. Check per-process CPU/disk usage to find the top consumers To see the processes that are the main CPU consumers, use the task manager program `top` like this: ``` top -o +%CPU -i ``` Use `iotop`: `iotop` is a useful tool, similar to `top`, used to monitor Disk I/O usage, if you don't have it, then ``` sudo iotop ``` Minimize the load by closing any unnecessary main consumer processes. We strongly advise you to double-check if the process you want to close is necessary.
Project: Elastic APM (Observability and Analysis / Observability)
File: bug.md

name: Bug about: "Report a confirmed bug. For unconfirmed bugs please visit https://discuss.elastic.co/c/apm" labels: "bug" <!-- GitHub is reserved for bug reports and feature requests; it is not the place for general questions. If you have a question or an unconfirmed bug, please visit the . For security vulnerabilities please only send reports to security@elastic.co. See https://www.elastic.co/community/security for more information. Please fill in the following details to help us reproduce the bug: --> APM Server version (`apm-server version`): Description of the problem including expected versus actual behavior: Steps to reproduce: Please include a minimal but complete recreation of the problem, including server configuration, agent(s) used, etc. The easier you make it for us to reproduce it, the more likely that somebody will take the time to look at it. 2. Provide logs (if relevant):
Project: Checkmk (Observability and Analysis / Observability)
File: 16655.md

key | value | date | 2024-03-25T07:55:46+00:00 version | 2.4.0b1 class | fix edition | cre component | wato level | 1 compatible | yes When bulk renaming hosts the "Add Prefix" and "Add Suffix" options only allowed valid hostnames. This requirement was now changed, so that only the resulting hostname is validated.
Project: Inspektor Gadget (Observability and Analysis / Observability)
File: block-io.md

title: 'Using top block-io' weight: 20 description: > Periodically report block device I/O activity. The top block-io gadget is used to visualize the containers generating the most block device input/output. First, we need to create one pod for us to play with: ```bash $ kubectl run test-pod --image busybox:latest sleep inf ``` You can now use the gadget, but output will be empty: ```bash $ kubectl gadget top block-io K8S.NODE K8S.NAMESPACE K8S.POD K8S.CONTAINER PID COMM R/W MAJOR MINOR BYTES TIME(s) IOs ``` Indeed, it is waiting for I/O to occur. So, open another terminal and keep and eye on the first one, `exec` the container and use `dd`: ```bash $ kubectl exec -ti test-pod -- dd if=/dev/zero of=/tmp/foo count=16384 ``` On the first terminal, you should see: ``` K8S.NODE K8S.NAMESPACE K8S.POD K8S.CONTAINER PID COMM R/W MAJOR MINOR BYTES TIME(s) IOs minikube default test-pod test-pod 7767 dd W 0 0 1564672 3046 4 ``` This line correspond to the block device I/O initiated by `dd`. Congratulations! You reached the end of this guide! You can now delete the pod you created: ```bash $ kubectl delete pod test-pod pod "test-pod" deleted ``` Start a container that performs some IO activity: ```bash $ docker run --rm --name test-top-block-io busybox /bin/sh -c'while true; do dd if=/dev/zero of=/tmp/foo count=4096; sync; done' ``` Start the gadget on another terminal and you'll see the activity produced by the `test-top-block-io` container. ```bash $ sudo ig top block-io -c test-top-block-io RUNTIME.CONTAINERNAME PID COMM R/W MAJOR MINOR BYTES TIME OPS test-top-block-io 63666 sync W 253 0 24576 428 5 test-top-block-io 63715 dd W 253 0 2097152 4816 5 ... ```
Project: Checkmk (Observability and Analysis / Observability)
File: 16807.md

key | value | date | 2024-04-24T12:25:30+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes If users had disabled checks that have since been removed or are temporarily unavailable (due to disabled MKPs for instance), they would be prompted with a message like ``` WARNING: Invalid rule configuration detected (Ruleset: ignored_checks, Title: Disabled checks, Folder: , -| Rule nr: 1, Exception: ifoperstatus is not an allowed value) ``` These invalid values are ignored now. They do no harm and they are dropped upon editing the rule.
Project: Grafana Loki (Observability and Analysis / Observability)
File: authentication.md

title: Authentication menuTitle: description: Describes Loki's authentication. weight: Grafana Loki does not come with any included authentication layer. Operators are expected to run an authenticating reverse proxy in front of your services. The simple scalable requires a reverse proxy to be deployed in front of Loki, to direct client API requests to either the read or write nodes. The Loki Helm chart includes a default reverse proxy configuration, using Nginx. A list of open-source reverse proxies you can use: , which has a using their {{% admonition type="note" %}} When using Loki in multi-tenant mode, Loki requires the HTTP header `X-Scope-OrgID` to be set to a string identifying the tenant; the responsibility of populating this value should be handled by the authenticating reverse proxy. For more information, read the documentation.{{% /admonition %}} For information on authenticating Promtail, see the documentation for [how to configure Promtail]({{< relref "../send-data/promtail/configuration" >}}).
Project: Flagsmith (Observability and Analysis / Feature Flagging)
File: pull_request_template.md

Thanks for submitting a PR! Please check the boxes below: to check linting [ ] I have added information to `docs/` if required so people know about the feature! [ ] I have filled in the "Changes" section below? [ ] I have filled in the "How did you test this code" section below? title for this Pull Request Please describe. <!-- If the answer is manually, please include a quick step-by-step on how to test this PR. --> Please describe.
Project: Checkmk (Observability and Analysis / Observability)
File: 16495.md

key | value | date | 2024-03-04T13:04:06+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes When selecting to check multiple mailboxes, the software always checked only the last specified mailbox. This werk fixes this behaviour.
Project: Botkube (Observability and Analysis / Observability)
File: botkube_install.md

title: botkube install install or upgrade Botkube in k8s cluster Use this command to install or upgrade the Botkube agent. ``` botkube install [OPTIONS] [flags] ``` ``` botkube install botkube install --version 0.1.0 botkube install --repo @local ``` ``` --atomic If set, process rolls back changes made in case of failed install/upgrade. The --wait flag will be set automatically if --atomic is used -y, --auto-approve Skips interactive approval when upgrade is required. --chart-name string Botkube Helm chart name. (default "botkube") --dependency-update Update dependencies if they are missing before installing the chart --description string add a custom description --disable-openapi-validation If set, it will not validate rendered templates against the Kubernetes OpenAPI Schema --dry-run Simulate an installation --force Force resource updates through a replacement strategy -h, --help help for install --kubeconfig string Paths to a kubeconfig. Only required if out-of-cluster. --namespace string Botkube installation namespace. (default "botkube") --no-hooks Disable pre/post install/upgrade hooks --release-name string Botkube Helm chart release name. (default "botkube") --render-subchart-notes If set, render subchart notes along with the parent --repo string Botkube Helm chart repository location. It can be relative path to current working directory or URL. Use @stable tag to select repository which holds the stable Helm chart versions. (default "https://charts.botkube.io/") --reset-values When upgrading, reset the values to the ones built into the chart --reuse-values When upgrading, reuse the last release's values and merge in any overrides from the command line via --set and -f. If '--reset-values' is specified, this is ignored --set stringArray Set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2) --set-file stringArray Set values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2) --set-json stringArray Set JSON values on the command line (can specify multiple or separate values with commas: key1=jsonval1,key2=jsonval2) --set-literal stringArray Set a literal STRING value on the command line --set-string stringArray Set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2) --skip-crds If set, no CRDs will be installed. --timeout duration Maximum time during which the Botkube installation is being watched, where "0" means "infinite". Valid time units are "ns", "us" (or "s"), "ms", "s", "m", "h". (default 10m0s) -f, --values strings Specify values in a YAML file or a URL (can specify multiple) --version string Botkube version. Possible values @latest, 1.2.0, ... (default "@latest") -w, --watch --timeout Watches the status of the Botkube installation until it finish or the defined --timeout occurs. (default true) ``` ``` -v, --verbose int/string[=simple] Prints more verbose output. Allowed values: 0 - disable, 1 - simple, 2 - trace (default 0 - disable) ``` - Botkube CLI
Project: Checkmk (Observability and Analysis / Observability)
File: 16584.md

key | value | date | 2024-03-20T12:51:32+00:00 version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes Some httpie examples had a backslash at the end of the last line causing these examples to fail when executed. This Werk fixes the way REST API examples are generated to prevent backslashes at the end of the last line.
Project: Grafana Pyroscope (Observability and Analysis / Observability)
File: v1-5.md

title: Version 1.5 release notes menuTitle: V1.5 description: Release notes for Grafana Pyroscope 1.5 weight: 650 We are excited to present Grafana Pyroscope 1.5. This release focuses on improving stability and interoperability to make Pyroscope more reliable and easier to use. Notable changes are listed below. For more details, check out the Full 1.5.0 Changelog: https://github.com/grafana/pyroscope/compare/v1.4.0...v1.5.0. Version 1.5 includes the following improvements and updates: Repair Go stack traces () eBPF: Aggregate python stacks in kernel space instead of user space () eBPF: Propagate PID namespace to kernel space () eBPF: Run tests on many kernels () eBPF: Add support for more Python versions () Improve trace span propagation in streaming requests () Drop type params from Go function names () Disable vt proto pools () Allow running multiple rideshare examples in the same network namespace () Version 1.5 includes the following fixes: Wait for ongoing queries to finish at close () Fix data duplication in the read path (#3100, ) Fix merging of empty pprof samples () Correctly format makefile help rule () Version 1.5 includes the following documentation updates: Reorganize examples folder to match documentation structure () Update Configure the client and span profiles doc () Improve intro and span profiles docs (, )
Project: Checkmk (Observability and Analysis / Observability)
File: 16615.md

key | value | date | 2024-03-11T11:09:48+00:00 version | 2.4.0b1 class | security edition | cre component | checks level | 1 compatible | yes With this Werk the `websphere_mq` plugin is removed for security reasons. In this plugin the output of `ps` is used to determine an argument for `runmqsc`. This meant that anybody who can launch processes with an arbitrary command line could manipulate one argument to `runmqsc`. The plugin was already superseded by the agent plugin `ibm_mq` and deprecated with Werk and version 2.0.0. Since this plugin is already deprecated and it was not configurable via the agent bakery we assumed that this plugin is not frequently used. Therefore we decided to not fix the issue but to push the removal. We found this vulnerability internally. Affected versions: 2.3.0 2.2.0 2.1.0 2.0.0 Mitigations: Migrate to the `ibm_mq` plugin. Vulnerability Management: We have rated the issue with a CVSS Score of 6.5 (Medium) with the following CVSS vector: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`. We assigned CVE-2024-3367 to this vulnerability. Changes: The plugin was removed.
Project: Grafana Loki (Observability and Analysis / Observability)
File: fuzzy_mode_convert_table.md

| json type \ dest type | bool | int | uint | float |string| | | | | |--|--| | number | positive => true <br/> negative => true <br/> zero => false| 23.2 => 23 <br/> -32.1 => -32| 12.1 => 12 <br/> -12.1 => 0|as normal|same as origin| | string | empty string => false <br/> string "0" => false <br/> other strings => true | "123.32" => 123 <br/> "-123.4" => -123 <br/> "123.23xxxw" => 123 <br/> "abcde12" => 0 <br/> "-32.1" => -32| 13.2 => 13 <br/> -1.1 => 0 |12.1 => 12.1 <br/> -12.3 => -12.3<br/> 12.4xxa => 12.4 <br/> +1.1e2 =>110 |same as origin| | bool | true => true <br/> false => false| true => 1 <br/> false => 0 | true => 1 <br/> false => 0 |true => 1 <br/>false => 0|true => "true" <br/> false => "false"| | object | true | 0 | 0 |0|originnal json| | array | empty array => false <br/> nonempty array => true| [] => 0 <br/> [1,2] => 1 | [] => 0 <br/> [1,2] => 1 |[] => 0<br/>[1,2] => 1|original json|
Project: VictoriaMetrics (Observability and Analysis / Observability)
File: vmscrapeconfig.md

sort: 11 weight: 11 title: VMScrapeConfig menu: docs: parent: "operator-custom-resources" weight: 11 aliases: /operator/resources/vmscrapeconfig.html The `VMScrapeConfig` CRD allows to define a scrape config using . `VMScrapeConfig` object generates part of configuration with Prometheus-compatible scrape targets. You can see the full actual specification of the `VMScrapeConfig` resource in the . Also, you can check out the section. The `VMScrapeConfig` CRD from VictoriaMetrics Operator is a drop-in replacement for the Prometheus `ScrapeConfig` from prometheus-operator. More details about migration from prometheus-operator you can read in . ```yaml apiVersion: operator.victoriametrics.com/v1beta1 kind: VMScrapeConfig metadata: name: mongodb spec: consulSDConfigs: server: https://consul-dns:8500 services: mongodb relabelConfigs: action: replace sourceLabels: metaconsulservice targetLabel: job ```
Project: PowerfulSeal (Observability and Analysis / Chaos Engineering)
File: CONTRIBUTING.md

If you'd like to help us improve and extend this project, then we welcome your contributions! Below you will find some basic steps required to be able to contribute to the project. If you have any questions about this process or any other aspect of contributing to a Bloomberg open source project, feel free to send an email to opensource@bloomberg.net and we'll get your questions answered as quickly as we can. Pull Requests are always welcome, however they will only be accepted if they provide a reasonably test coverage. Since `PowerfulSeal` is distributed under the terms of the , contributions that you make are licensed under the same terms. In order for us to be able to accept your contributions, we will need explicit confirmation from you that you are able and willing to provide them under these terms, and the mechanism we use to do this is called a Developer's Certificate of Origin . This is very similar to the process used by the Linux(R) kernel, Samba, and many other major open source projects. To participate under these terms, all that you must do is include a line like the following as the last line of the commit message for each commit in your contribution: Signed-Off-By: Random J. Developer <random@developer.example.org> The simplest way to accomplish this is to add `-s` or `--signoff` to your `git commit` command. You must use your real name (sorry, no pseudonyms, and no anonymous contributions).
Project: Grafana (Observability and Analysis / Observability)
File: README.md

Modowners is a way to ensure that each Go dependency has at least one team responsible for maintaining and upgrading it. The `validate-modfile` drone step checks `go.mod` and will pass if every dependency has an owner. When adding a new dependency, add the responsible team in a line comment. Currently `validate-modfile` is non-blocking, but will eventually become a blocking step. All newly added dependencies will require an assigned owner. `cloud.google.com/go/storage v1.30.1 // @grafana/grafana-backend-group` Validate `go.mod` and exit with an error if a dependency does not have an owner. Example CLI command: `go run scripts/modowners/modowners.go check go.mod` If `go.mod` is valid, there will be no output. List owners of given dependency. Example CLI command to get a list of all owners with a count of the number of dependencies they own: `go run scripts/modowners/modowners.go owners -a -c go.mod` Example output: ``` @grafana/grafana-release-guild 5 @grafana/grafana-bi-squad 2 @grafana/grafana-app-platform-squad 13 @grafana/observability-metrics 4 @grafana/observability-traces-and-profiling 6 @grafana/aws-datasources 2 @grafana/alerting-squad-backend 22 @grafana/plugins-platform-backend 7 @grafana/grafana-operator-experience-squad 3 @grafana/dataviz-squad 1 @grafana/grafana-backend-group 75 @grafana/grafana-as-code 11 @grafana/identity-access-team 6 @grafana/partner-datasources 4 ``` Example CLI command to get the owner for a specific dependency (you must use `dependency@version`, not `dependency version`): `go run scripts/modowners/modowners.go owners -d cloud.google.com/go/storage@v1.30.1 go.mod` Example output: ``` @grafana/grafana-backend-group ``` List all dependencies of given owner(s). Example CLI command to list all direct dependencies owned by Delivery and Authnz: `go run scripts/modowners/modowners.go modules -o @grafana/grafana-release-guild,@grafana/identity-access-team go.mod` Example output: ``` github.com/BurntSushi/toml@v1.2.1 github.com/go-ldap/ldap/v3@v3.4.4 github.com/magefile/mage@v1.14.0 golang.org/x/oauth2@v0.8.0 github.com/drone/drone-cli@v1.6.1 github.com/google/go-github/v45@v45.2.0 github.com/Masterminds/semver/v3@v3.1.1 gopkg.in/square/go-jose.v2@v2.6.0 filippo.io/age@v1.1.1 github.com/docker/docker@v23.0.4+incompatible ``` For existing dependencies, please review and update ownership of your teams dependencies in `go.mod`. If any assignments are incorrect, you can replace your team name with the correct team in `go.mod`. If you dont know who the correct team is, you can reassign the dependency back to backend platform. Afterwards, open a PR and assign backend platform as reviewers.
Project: Checkmk (Observability and Analysis / Observability)
File: 16755.md

key | value | date | 2024-04-19T12:34:59+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes The value previously displayed as 'Commit Charge' did not match its description. Therefore, this value has been accurately renamed to 'Virtual Memory,' while maintaining the original calculation method. Correspondingly, the titles of related graphs have been adjusted to reflect this change. In versions prior to 2.3, the service summary included a metric labeled 'Pagefile installed.' This has now been correctly renamed to 'Total Virtual Memory,' as it never accurately represented the 'Pagefile installed.'
Project: Netdata (Observability and Analysis / Observability)
File: k8s_cgroup_10min_cpu_usage.md

This alert calculates the average `cgroup CPU utilization` over the past 10 minutes in a Kubernetes cluster. If you receive this alert at the warning or critical levels, it means that your cgroup is heavily utilizing the available CPU resources. In Kubernetes, `cgroups` are a Linux kernel feature that helps to limit and isolate the resource usage (CPU, memory, disk I/O, etc.) of a collection of processes. The `cgroup CPU utilization` measures the percentage of available CPU resources consumed by the processes within a cgroup. Identify the over-utilizing cgroup Check the alert message for the specific cgroup that is causing high CPU utilization. Determine the processes utilizing the most CPU resources in the cgroup To find the processes within the cgroup with high CPU usage, you can use `systemd-cgtop` on the Kubernetes nodes: ``` systemd-cgtop -m -1 -p -n10 ``` Analyze the Kubernetes resource usage Use `kubectl top` to get an overview of the resource usage in your Kubernetes cluster: ``` kubectl top nodes kubectl top pods ``` Investigate the Kubernetes events and logs Examine the events and logs of the Kubernetes cluster and the specific resources that are causing the high CPU utilization. ``` kubectl get events --sort-by='.metadata.creationTimestamp' kubectl logs <pod-name> -n <namespace> --timestamps -f ``` Optimize the resource usage of the cluster You may need to scale your cluster by adding more resources, adjusting the resource limits, or optimizing the application code to minimize CPU usage.