cwielenb/CNCF-Dataset huggingface dataset:
Project: Krkn (Observability and Analysis / Chaos Engineering)
File: contribute.md

Contributions are always appreciated. How to: In order to submit a change or a PR, please fork the project and follow these instructions: ```bash $ git clone http://github.com/<me>/krkn $ cd krkn $ git checkout -b <branch_name> $ <make change> $ git add <changes> $ git commit -a $ <insert good message> $ git push ``` Kraken uses framework to maintain the code linting and python code styling. The CI would run the pre-commit check on each pull request. We encourage our contributors to follow the same pattern while contributing to the code. The pre-commit configuration file is present in the repository `.pre-commit-config.yaml`. It contains the different code styling and linting guides which we use for the application. The following command can be used to run the pre-commit: `pre-commit run --all-files` If pre-commit is not installed in your system, it can be installed with `pip install pre-commit`. If there are multiple commits, please rebase/squash multiple commits before creating the PR by following: ```bash $ git checkout <my-working-branch> $ git rebase -i HEAD~<numofcommitstomerge> -OR- $ git rebase -i <commitidoffirstchange_commit> ``` In the interactive rebase screen, set the first commit to `pick`, and all others to `squash`, or whatever else you may need to do. Push your rebased commits (you may need to force), then issue your PR. ``` $ git push origin <my-working-branch> --force ``` If changes go into the main repository while you're working on your code it is best to rebase your code with the upstream, so you stay up to date with all changes and fix any conflicting code changes. If not already configured, set the upstream url for kraken. ``` git remote add upstream https://github.com/krkn-chaos/krkn.git ``` Rebase to upstream master branch. ``` git fetch upstream git rebase upstream/master git push origin <branch_name> --force ``` If any errors occur, it will list off any files that have merge issues. Edit the files with the code you want to keep. See below for detailed help from Git. Vi <file(s)> Resolving-a-merge-conflict-using-the-command-line git add <all files you edit> git rebase --continue Might need to repeat steps 2 through 4 until rebase complete git status <this will also tell you if you have other files to edit> git push origin <branch_name> --force [push the changes to github remote] Merge Conflicts Example ``` git rebase upstream/kraken vi run_kraken.py [edit at the indicated places, get rid of arrowed lines and dashes, and apply correct changes] git add run_kraken.py git rebase --continue repeat 2-4 until done git status <this will also tell you if you have other files to edit> git push origin <branch_name> --force [push the changes to github remote] ```
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_pod.LogOptions.md

title: "Interface: LogOptions" linkTitle: "LogOptions" slug: "libk8spod.LogOptions" .LogOptions `Optional` follow: `boolean` Whether to follow the log stream _ `Optional` showPrevious: `boolean` Whether to show the logs from previous runs of the container (only for restarted containers) _ `Optional` showTimestamps: `boolean` Whether to show the timestamps in the logs _ `Optional` tailLines: `number` The number of lines to display from the end side of the log `Optional` onReconnectStop(): `void` Callback to be called when the reconnection attempts stop `void`
Project: Netdata (Observability and Analysis / Observability)
File: 10min_dbengine_global_flushing_errors.md

The Database Engine works like a traditional database. It dedicates a certain amount of RAM to data caching and indexing, while the rest of the data resides compressed on disk. Unlike other memory modes, the amount of historical metrics stored is based on the amount of disk space you allocate and the effective compression ratio, not a fixed number of metrics collected. By using both RAM and disk space, the database engine allows for long-term storage of per-second metrics inside of the Netdata Agent itself. Netdata monitors the number of pages deleted due to failure to flush data to disk in the last 10 minutes. In this situation some metric data was dropped to unblock data collection. To remedy this issue, reduce disk load or use faster disks. This alert is triggered in critical state when the number deleted pages is greater than 0.
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_clusterRoleBinding.ClusterRoleBinding.md

title: "Class: ClusterRoleBinding" linkTitle: "ClusterRoleBinding" slug: "libk8sclusterRoleBinding.ClusterRoleBinding" .ClusterRoleBinding `ClusterRoleBinding` new ClusterRoleBinding(`json`) | Name | Type | | : | : | | `json` | | . `Static` apiEndpoint: `Object` | Name | Type | | : | : | | `apiInfo` | { `group`: `string` ; `resource`: `string` ; `version`: `string` }[] | | `delete` | (`name`: `string`, `queryParams?`: , `cluster?`: `string`) => `Promise`<`any`\> | | `get` | (`name`: `string`, `cb`: , `errCb`: , `queryParams?`: , `cluster?`: `string`) => `Promise`<() => `void`\> | | `isNamespaced` | `boolean` | | `list` | (`cb`: , `errCb`: , `queryParams?`: , `cluster?`: `string`) => `Promise`<() => `void`\> | | `patch` | (`body`: `OpPatch`, `cluster?`: `string`) => `Promise`<`any`\> | | `post` | (`body`: , `queryParams?`: , `cluster?`: `string`) => `Promise`<`any`\> | | `put` | (`body`: , `queryParams?`: , `cluster?`: `string`) => `Promise`<`any`\> | . `get` detailsRoute(): `string` `string` _ `get` roleRef(): `any` `any` RoleBinding.roleRef _ `get` subjects(): { `apiGroup`: `string` ; `kind`: `string` ; `name`: `string` ; `namespace`: `string` }[] { `apiGroup`: `string` ; `kind`: `string` ; `name`: `string` ; `namespace`: `string` }[] RoleBinding.subjects _ `Static` `get` className(): `string` `string` RoleBinding.className `Static` apiList(`onList`, `onError?`, `opts?`): `any` | Name | Type | | : | : | | `onList` | (`arg`: `any`[]) => `void` | | `onError?` | (`err`: ) => `void` | | `opts?` | | `any` . _ `Static` `Optional` getAuthorization(`arg`, `resourceAttrs?`): `any` | Name | Type | | : | : | | `arg` | `string` | | `resourceAttrs?` | | `any` . _ `Static` getErrorMessage(`err?`): ``null`` \| `string` | Name | Type | | : | : | | `err?` | ``null`` \| | ``null`` \| `string` . _ `Static` useApiGet(`onGet`, `name`, `namespace?`, `onError?`): `void` | Name | Type | | : | : | | `onGet` | (...`args`: `any`) => `void` | | `name` | `string` | | `namespace?` | `string` | | `onError?` | (`err`: ) => `void` | `void` . _ `Static` useApiList(`onList`, `onError?`, `opts?`): `any` | Name | Type | | : | : | | `onList` | (`arg`: `any`[]) => `void` | | `onError?` | (`err`: ) => `void` | | `opts?` | | `any` . _ `Static` useGet(`name`, `namespace?`): , (`item`: `any`) => `void`, (`err`: ``null`` \| ) => `void`] | Name | Type | | : | : | | `name` | `string` | | `namespace?` | `string` | , (`item`: `any`) => `void`, (`err`: ``null`` \| ) => `void`] . _ `Static` useList(`opts?`): , (`items`: `any`) => `void`] | Name | Type | | : | : | | `opts?` | | , (`items`: `any`) => `void`] .
Project: M3 (Observability and Analysis / Observability)
File: quickstart-prometheus-steps.md

This quickstart uses of the Prometheus node exporter to export metrics to Prometheus that M3 then ingests. To follow the next steps, . With M3 running and ready to receive metrics, change your Prometheus configuration to add M3 as `remoteread` and `remotewrite` URLs, and as a job. With the configuration below, Prometheus scrapes metrics from two local nodes `localhost:8080` and `localhost:8081` in the `production` group, and one local node `localhost:8082` in the `canary` group: {{< codeinclude file="docs/includes/prometheus.yml" language="yaml" >}} Start Prometheus using the new configuration with the command below: ```shell prometheus --config.file=prometheus.yml ``` The three commands below simulate three point of sale (POS) devices reporting an hourly sales total for the POS. The node_exporter textfile collector uses for metrics, and only loads files from a directory, so this requires some extra steps for each node for this example. {{< tabs name="node_exporters" >}} {{< tab name="Node 1" >}} {{% notice tip %}} Below is the text file for the first node, copy and paste it into a new .prom file in a directory named node-1, or into that new folder. {{% /notice %}} {{< codeinclude file="docs/includes/quickstart/node-1/metrics-1.prom" language="text" >}} Run node_exporter from its install location, passing the directory that contains the textfile, and the public facing address, which for this example serves as the identifier of the POS. {{< codeinclude file="docs/includes/quickstart/node-1/node_exporter-1.sh" language="shell" >}} {{< /tab >}} {{< tab name="Node 2" >}} {{% notice tip %}} Below is the text file for the second node, copy and paste it into a new .prom file in a directory named node-2, or into that new folder. {{% /notice %}} {{< codeinclude file="docs/includes/quickstart/node-2/metrics-2.prom" language="text" >}} Run node_exporter from its install location, passing the directory that contains the textfile, and the public facing address, which for this example serves as the identifier of the POS. {{< codeinclude file="docs/includes/quickstart/node-2/node_exporter-2.sh" language="shell" >}} {{< /tab >}} {{< tab name="Node 3" >}} {{% notice tip %}} Below is the text file for the second node, copy and paste it into a new .prom file in a directory named node-3, or into that new folder. {{% /notice %}} {{< codeinclude file="docs/includes/quickstart/node-3/metrics-3.prom" language="text" >}} Run node_exporter from it's install location, passing the directory that contains the textfile, and the public facing address, which for this example serves as the identifier of the POS. {{< codeinclude file="docs/includes/quickstart/node-3/node_exporter-3.sh" language="shell" >}} {{< /tab >}} {{< /tabs >}} {{% notice tip %}} You can now confirm that the nodeexporter exported metrics to Prometheus by searching for `thirdavenue` in the Prometheus dashboard. {{% /notice %}}
Project: Netdata (Observability and Analysis / Observability)
File: btrfs.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/integrations/btrfs.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/metadata.yaml" sidebar_label: "BTRFS" learn_status: "Published" learnrelpath: "Collecting Metrics/Linux Systems/Filesystem/BTRFS" most_popular: False message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" endmeta--> <img src="https://netdata.cloud/img/filesystem.svg" width="150"/> Plugin: proc.plugin Module: /sys/fs/btrfs <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> This integration provides usage and error statistics from the BTRFS filesystem. This collector is supported on all platforms. This collector supports collecting metrics from multiple instances of this integration, including remote instances. This integration doesn't support auto-detection. The default configuration for this integration does not impose any limits on data collection. The default configuration for this integration is not expected to impose a significant performance impact on the system. Metrics grouped by scope. The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels. Labels: | Label | Description | |:--|:-| | filesystem_uuid | TBD | | filesystem_label | TBD | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | btrfs.disk | unallocated, datafree, dataused, metafree, metaused, sysfree, sysused | MiB | | btrfs.data | free, used | MiB | | btrfs.metadata | free, used, reserved | MiB | | btrfs.system | free, used | MiB | | btrfs.commits | commits | commits | | btrfs.commitsperctime | commits | percentage | | btrfs.commit_timings | last, max | ms | Labels: | Label | Description | |:--|:-| | device_id | TBD | | filesystem_uuid | TBD | | filesystem_label | TBD | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | btrfs.deviceerrors | writeerrs, readerrs, flusherrs, corruptionerrs, generationerrs | errors | The following alerts are available: | Alert name | On metric | Description | |:|:-|:| | | btrfs.disk | percentage of allocated BTRFS physical disk space | | | btrfs.data | utilization of BTRFS data space | | | btrfs.metadata | utilization of BTRFS metadata space | | | btrfs.system | utilization of BTRFS system space | | | btrfs.device_errors | number of encountered BTRFS read errors | | | btrfs.device_errors | number of encountered BTRFS write errors | | | btrfs.device_errors | number of encountered BTRFS flush errors | | | btrfs.device_errors | number of encountered BTRFS corruption errors | | | btrfs.device_errors | number of encountered BTRFS generation errors | No action required. There is no configuration file. There are no configuration options. There are no configuration examples.
Project: Vector (Observability and Analysis / Observability)
File: 2021-04-21-0-13-upgrade-guide.md

date: "2020-04-21" title: "0.13 Upgrade Guide" description: "An upgrade guide that addresses breaking changes in 0.13.0" authors: ["jszwedko"] pr_numbers: [] release: "0.13.0" hideonrelease_notes: false badges: type: breaking change 0.13 includes one minor breaking change: We cover each below to help you upgrade quickly: Previously, when the function was used, it would return both named capture groups as well as numeric capture groups. For example: ```text parse_regex!("hello 123 world", r'hello (?P<number>\d+) world') ``` Would return: ```json { "0": "hello 123 world", "1": "123", "number": "123" } ``` With `0` matching the whole regex, and `1` matching the first capture group, in addition to `number`. We heard from users that they did not expect the numeric groups by default so we decided to leave them out by default now. Using our previous example: ```text parse_regex!("hello 123 world", r'hello (?P<number>\d+) world') ``` It now returns: ```json { "number": "123" } ``` A new `numeric_groups` parameter that can be used to have the numeric capture groups returned like before. Again using the same example, but with the new parameter: ```text parseregex!("hello 123 world", r'hello (?P<number>\d+) world', numericgroups: true) ``` This returns the old value of: ```json { "0": "hello 123 world", "1": "123", "number": "123" } ```
Project: Vector (Observability and Analysis / Observability)
File: 2020-07-06-add-compression-option-for-aws-sinks.md

date: "2020-07-14" title: "New compression options for some sinks" description: "Stuff more data down a smaller hose in less time for cheaper." authors: ["hoverbear"] hideonrelease_notes: false pr_numbers: [2953, 2637, 2679, 2682] release: "0.10.0" badges: type: "new feature" sinks: ["awskinesisfirehose", "awskinesisstreams", "awss3", "humiologs"] Several sinks, including most AWS sinks as well as and have had compression options added. Compression is opt-in. Make the following changes in your `vector.toml` file: ```diff title="vector.toml" [sinks.little-pipe] type = "awscloudwatchmetrics" # required inputs = ["big-firehose"] # required healthcheck = true # optional, default namespace = "service" # required region = "us-east-1" # required, required when endpoint = "" compression = "gzip" # optional, default none ```
Project: Checkmk (Observability and Analysis / Observability)
File: 16359.md

key | value | date | 2024-01-16T11:18:30+00:00 version | 2.3.0b1 class | feature edition | cre component | checks level | 1 compatible | no In previous versions some windows agent plugins were included in `share/check_mk/agents/windows/plugins/deprecated`. As the name already suggested these were deprecated for a long time and are now removed. If you still require them you can use the plugins from former versions.
Project: HertzBeat (Observability and Analysis / Observability)
File: 2022-10-08-hertzbeat-v1.2.0.md

title: HertzBeat v1.2.0 Released! Easy-to-use and friendly open source real-time monitoring tool author: tom author_title: tom author_url: https://github.com/tomsun28 authorimageurl: https://avatars.githubusercontent.com/u/24788200?s=400&v=4 tags: [opensource] Home: hertzbeat.com | tancloud.cn Hi guys! HertzBeat v1.2.0 is coming. This version supports more powerful metrics collect jsonpath, upgrade springboot version to 2.7.4, support This version supports more powerful metrics collect jsonpath, upgrade springboot version to 2.7.4, support metrics unit convert display, and more. Fixed several bugs and improved the overall stable usability. Only one docker command is needed to install and experience heartbeat: `docker run -d -p 1157:1157 --name hertzbeat apache/hertzbeat` Thanks to the contributors! @Ceilzcx @Privauto @VampireAchao @DreamGirl524 @CharlieXCL @emrys-he @SxLiuYu @tomsun28 We urgently need contributors to test cases, new application monitoring, documentation, etc., and very welcome you to join. Come on! HertzBeat is so easy! Features. 1. [[home,manager]] contribute by @DreamGirl524 contributed by @VampireAchao contributed by @Ceilzcx contributed by @Privauto contributed by @Ceilzcx contributed by @Privauto contributed by @Privauto contributed by @Ceilzcx Bugfixes. contributed by @CharlieXCL contributed by @Privauto contributed by @emrys-he contributed by @SxLiuYu Online https://console.tancloud.cn. Have Fun! Need Convert `application.yml`. ``` spring. resources: static-locations. static-locations. classpath:/dist/ classpath:... /dist/ ``` To `` spring. web. resources: static-locations. static-locations. classpath:/dist/ classpath:... /dist/ ```
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_vpa.VPA.md

title: "Class: VPA" linkTitle: "VPA" slug: "libk8svpa.VPA" .VPA `any` `VPA` new VPA(`json`) | Name | Type | | : | : | | `json` | | makeKubeObject<KubeVPA\>('verticalPodAutoscaler').constructor `Static` apiEndpoint: `Object` | Name | Type | | : | : | | `scale?` | { `get`: (`namespace`: `string`, `name`: `string`, `clusterName?`: `string`) => `Promise`<`any`\> ; `put`: (`body`: { `metadata`: ; `spec`: { `replicas`: `number` } }, `clusterName?`: `string`) => `Promise`<`any`\> } | | `scale.get` | (`namespace`: `string`, `name`: `string`, `clusterName?`: `string`) => `Promise`<`any`\> | | `scale.put` | (`body`: { `metadata`: ; `spec`: { `replicas`: `number` } }, `clusterName?`: `string`) => `Promise`<`any`\> | _ `Static` className: `string` makeKubeObject<KubeVPA\>('verticalPodAutoscaler').className `get` referenceObject(): `any` `any` _ `get` spec(): `VpaSpec` `VpaSpec` _ `get` status(): `VpaStatus` `VpaStatus` _ `get` targetRecommendations(): `undefined` \| ``null`` \| `RecommendationValue` `undefined` \| ``null`` \| `RecommendationValue` `Static` apiList(`onList`, `onError?`, `opts?`): `any` | Name | Type | | : | : | | `onList` | (`arg`: `any`[]) => `void` | | `onError?` | (`err`: ) => `void` | | `opts?` | | `any` makeKubeObject<KubeVPA\>('verticalPodAutoscaler').apiList _ `Static` `Optional` getAuthorization(`arg`, `resourceAttrs?`): `any` | Name | Type | | : | : | | `arg` | `string` | | `resourceAttrs?` | | `any` makeKubeObject<KubeVPA\>('verticalPodAutoscaler').getAuthorization _ `Static` getErrorMessage(`err?`): ``null`` \| `string` | Name | Type | | : | : | | `err?` | ``null`` \| | ``null`` \| `string` makeKubeObject<KubeVPA\>('verticalPodAutoscaler').getErrorMessage _ `Static` isEnabled(): `Promise`<`boolean`\> `Promise`<`boolean`\> _ `Static` useApiGet(`onGet`, `name`, `namespace?`, `onError?`): `void` | Name | Type | | : | : | | `onGet` | (...`args`: `any`) => `void` | | `name` | `string` | | `namespace?` | `string` | | `onError?` | (`err`: ) => `void` | `void` makeKubeObject<KubeVPA\>('verticalPodAutoscaler').useApiGet _ `Static` useApiList(`onList`, `onError?`, `opts?`): `any` | Name | Type | | : | : | | `onList` | (`arg`: `any`[]) => `void` | | `onError?` | (`err`: ) => `void` | | `opts?` | | `any` makeKubeObject<KubeVPA\>('verticalPodAutoscaler').useApiList _ `Static` useGet(`name`, `namespace?`): , (`item`: `any`) => `void`, (`err`: ``null`` \| ) => `void`] | Name | Type | | : | : | | `name` | `string` | | `namespace?` | `string` | , (`item`: `any`) => `void`, (`err`: ``null`` \| ) => `void`] makeKubeObject<KubeVPA\>('verticalPodAutoscaler').useGet _ `Static` useList(`opts?`): , (`items`: `any`) => `void`] | Name | Type | | : | : | | `opts?` | | , (`items`: `any`) => `void`] makeKubeObject<KubeVPA\>('verticalPodAutoscaler').useList
Project: Graylog (Observability and Analysis / Observability)
File: bug_report.md

name: Bug report / change request about: Create a report to help us improve. This includes bugs but also changing the behavior of the product. title: '' labels: bug assignees: '' <! Provide a general summary of the issue in the Title above --> <! If you're describing a bug, tell us what should happen --> <! If you're suggesting a change/improvement, tell us how it should work --> <! If describing a bug, tell us what happens instead of the expected behavior --> <! If suggesting a change/improvement, explain the difference from current behavior --> <! Not obligatory, but suggest a fix/reason for the bug, --> <! or ideas how to implement the addition or change --> <! Provide a link to a live example, or an unambiguous set of steps to --> <! reproduce this bug. Include code to reproduce, if relevant --> <! How has this issue affected you? What are you trying to accomplish? --> <! Providing context helps us come up with a solution that is most useful in the real world --> <! Include as many relevant details about the environment you experienced the bug in --> Graylog Version: Java Version: OpenSearch Version: MongoDB Version: Operating System: Browser version: