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

key | value | compatible | yes version | 2.4.0b1 date | 2024-01-17T08:20:43+00:00 level | 3 class | security component | checks edition | cre The agent plugins mkoracle, mkoracle.ps1 and mkoraclecrs were vulnerable to privilege escalation to root by the oracle user. A malicious oracle user could replace a binary (e.g. sqlplus) with another script and put it in the corresponding directory. The script would be executed by the root user. All binaries, which are called by the plugins, are now checked if they need to be executed as a non-root (non-administrator under Windows) user, preventing the privilege escalation. Affected binaries are: sqlplus, tnsping, crsctl. <h3>Affected Versions</h3> 2.3.0 (beta) 2.2.0 2.1.0 2.0.0 (EOL) and older <h3>Mitigations</h3> If updating is not possible, disable the mk_oracle plugin. <h3>Vulnerability Management</h3> We have rated the issue with a CVSS score of 8.2 (High) with the following CVSS vector: <code>CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H</code> We have assigned <code>CVE-2024-0638</code>. <h3>Changes</h3> All called binaries are now executed in a safe way.
Project: OpenFeature (Observability and Analysis / Feature Flagging)
File: appendix-b-gherkin-suites.md

id: appendix-b title: "Appendix B: Gherkin Suites" description: A Set of End-to-End Tests for Validating OpenFeature Implementations sidebar_position: 5 This section contains a set of language-agnostic end-to-end tests (defined in gherkin). These tests can be used to validate the behavior of an OpenFeature implementation. "Features" (test suites) can be used in conjunction with an and a cucumber test-runner for the language in question. The contains tests for the basic functionality of the .
Project: Vector (Observability and Analysis / Observability)
File: 2021-01-31-file-source-checkpointing.md

date: "2021-01-31" title: "Improved `file` source checkpointing" description: "The `file` source checkpointing strategy has been improved to solve surprising edge cases." authors: ["binarylogic"] featured: false pr_numbers: [6178] release: "0.12.0" hideonrelease_notes: false badges: type: "enhancement" domains: ["sources"] sources: ["file"] The Vector included an option called `startatbeginning` that would determine where Vector would begin reading a file based on a . As you can see, these conditions were quite confusing. To resolve this, deprecated the `startatbeginning` option and replaced it with new and options. Migrating is easy: ```diff [sources.file] type = "file" -startatbeginning = true +ignore_checkpoints = false # default +read_from = "beginning" # default ``` Adjust as necessary. The above values are the defaults and are not required to be specified.
Project: Netdata (Observability and Analysis / Observability)
File: scaleio_sdc_mdm_connection_state.md

The `scaleiosdcmdmconnectionstate` alert indicates that your ScaleIO Data Client (SDC) is disconnected from the ScaleIO MetaData Manager (MDM). This disconnection can lead to potential performance issues or data unavailability in your storage infrastructure. Check the connectivity between SDC and MDM nodes. Verify that the SDC and MDM nodes are reachable by performing a `ping` or using `traceroute` from the SDC node to the MDM node and vice versa. Network connectivity issues such as high latency or packet loss may cause the disconnection between SDC and MDM. Examine log files. Review the SDC and MDM log files to identify any error messages or warnings that can indicate the reason for the disconnection. Common log file locations are: SDC logs: `/opt/emc/scaleio/sdc/logs/sdc.log` MDM logs: `/opt/emc/scaleio/mdm/logs/mdm.log` Check the status of ScaleIO services. Verify that the ScaleIO services are running on both the SDC and MDM nodes. You can check the service status with the following commands: SDC service status: `sudo systemctl status scaleio-sdc` MDM service status: `sudo systemctl status scaleio-mdm` If any of the services are not running, start them and check the connection state again. Reconnect SDC to MDM. If the issue still persists after verifying the network connectivity and services' statuses, try to reconnect the SDC to MDM manually. Use the following command on the SDC node: ``` sudo scli --reconnectsdc --mdmip <MDMIPADDRESS> ``` Replace `<MDMIPADDRESS>` with the IP address of your MDM node. Contact support. If the disconnection issue persists after trying the above steps, consider contacting technical support for assistance.
Project: Netdata (Observability and Analysis / Observability)
File: ram_in_use.md

This alert shows the percentage of used RAM. If you receive this alert, there is high RAM utilization on the node. Running low on RAM memory, means that the performance of running applications might be affected. If there is no `swap` space available, the OOM Killer can start killing processes. When a system runs out of RAM, it can store it's inactive content in persistent storage (e.g. your main drive). The borrowed space is called `swap` or "swap space". The OOM Killer (Out of Memory Killer) is a process that the Linux Kernel uses when the system is critically low on RAM. As the name suggests, it has the duty to review all running processes and kill one or more of them in order to free up RAM memory and keep the system running. Check per-process RAM usage to find the top consumers Linux: ``` top -b -o +%MEM | head -n 22 ``` FreeBSD: ``` top -b -o res | head -n 22 ``` It would be helpful to close any of the main consumer processes, but Netdata strongly suggests knowing exactly what processes you are closing and being certain that they are not necessary.
Project: Checkmk (Observability and Analysis / Observability)
File: 16372.md

key | value | date | 2024-03-01T09:27:29+00:00 version | 2.4.0b1 class | feature edition | cre component | rest-api level | 1 compatible | yes Since not all Python regexes are ECMA (JavaScript) compliant, several parameter fields did not work in Swagger. This werk solves the problem by adjusting the regexes to be compatible with JavaScript.
Project: SkyWalking (Observability and Analysis / Observability)
File: backend-win-monitoring.md

SkyWalking leverages Prometheus windows_exporter to collect metrics data from the Windows and leverages OpenTelemetry Collector to transfer the metrics to and into the . Windows entity as a `Service` in OAP and on the `Layer: OS_WINDOWS`. For OpenTelemetry receiver: The Prometheus windows_exporter collects metrics data from the VMs. The OpenTelemetry Collector fetches metrics from windows_exporter via Prometheus Receiver and pushes metrics to the SkyWalking OAP Server via OpenTelemetry gRPC exporter. The SkyWalking OAP Server parses the expression with to filter/calculate/aggregate and store the results. For OpenTelemetry receiver: Setup . Setup . This is an example for OpenTelemetry Collector configuration . Config SkyWalking . | Monitoring Panel | Unit | Metric Name | Description | Data Source | |||-||--| | CPU Usage | % | meterwincputotalpercentage | The total percentage usage of the CPU core. If there are 2 cores, the maximum usage is 200%. | Prometheus windows_exporter | | Memory RAM Usage | MB | meterwinmemoryused | The total RAM usage | Prometheus windowsexporter | | Memory Swap Usage | % | meterwinmemoryswappercentage | The percentage usage of swap memory | Prometheus windows_exporter | | CPU Average Used | % | meterwincpuaverageused | The percentage usage of the CPU core in each mode | Prometheus windows_exporter | | Memory RAM | MB | meterwinmemorytotal<br />meterwinmemoryavailable<br />meterwinmemoryused | The RAM statistics, including Total / Available / Used | Prometheus windowsexporter | | Memory Swap | MB | meterwinmemoryswapfree<br />meterwinmemoryswaptotal | Swap memory statistics, including Free / Total | Prometheus windowsexporter | | The percentage usage of the file system at each mount point | Prometheus windowsexporter | | Disk R/W | KB/s | meterwindiskread,meterwindiskwritten | The disk read and written | Prometheus windows_exporter | | Network Bandwidth Usage | KB/s | meterwinnetworkreceive<br />meterwinnetworktransmit | The network receive and transmit | Prometheus windowsexporter | | The number of file descriptors allocated | Prometheus windowsexporter | You can customize your own metrics/expression/dashboard panel. The metrics definition and expression rules are found in `/config/otel-rules/windows.yaml`. The dashboard panel confirmations are found in `/config/ui-initialized-templates/os_windows`.
Project: Vector (Observability and Analysis / Observability)
File: homebrew.md

title: Install Vector using Homebrew short: Homebrew weight: 4 [Homebrew] is a free and open source package management system for Apple's macOS operating system and some supported Linux systems. This page covers installing and managing Vector using the Homebrew package repository. ```shell brew tap vectordotdev/brew && brew install vector ``` {{< tabs default="Upgrade Vector" >}} {{< tab title="Upgrade Vector" >}} ```shell brew update && brew upgrade vector ``` {{< /tab >}} {{< tab title="Uninstall Vector" >}} ```shell brew remove vector ``` {{< /tab >}} {{< /tabs >}} {{< jump "/docs/administration/management" "homebrew" >}}
Project: Netdata (Observability and Analysis / Observability)
File: asterisk.md

<!-- title: "Asterisk monitoring with Netdata" customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/statsd.plugin/asterisk.md" sidebar_label: "Asterisk" learn_status: "Published" learnrelpath: "Integrations/Monitor/VoIP" --> Monitors dialplan application's statistics. Asterisk . Netdata ships with with preconfigured charts. To receive Asterisk metrics in Netdata, uncomment the following lines in the `/etc/asterisk/statsd.conf` file: ```ini [general] enabled = yes ; When set to yes, statsd support is enabled server = 127.0.0.1 ; server[:port] of statsd server to use. ; If not specified, the port is 8125 prefix = asterisk ; Prefix to prepend to all metrics ``` See for all available options. <details><summary>Click to see screenshots of the charts.</summary> </details> Mapping Asterisk StatsD metrics and Netdata charts. | Chart | Metrics | ||--| | Active Channels | asterisk.channels.count | | Active Endpoints | asterisk.endpoints.count | | Active Endpoints by Status | asterisk.endpoints.state.* | | Active SIP channels by endpoint | asterisk.endpoints.SIP.*.channels | | Active PJSIP channels by endpoint | asterisk.endpoints.PJSIP.*.channels | | Distribution of Dial Statuses | asterisk.dialstatus.* | | Asterisk Channels Call Duration | asterisk.channels.calltime | | Distribution of Hangup Causes | asterisk.hangupcause.* | | Distribution of Hangup Causes for ANSWERed calls | asterisk.dialhangupcause.ANSWER.* | | Distribution of Hangup Causes for BUSY calls | asterisk.dialhangupcause.BUSY.* | | Distribution of Hangup Causes for CANCELled calls | asterisk.dialhangupcause.CANCEL.* | | Distribution of Hangup Causes for CHANUNVAILed calls | asterisk.dialhangupcause.CHANUNAVAIL.* | | Distribution of Hangup Causes for CONGESTIONed calls | asterisk.dialhangupcause.CONGESTION.* | | Asterisk Dialplan Events | asterisk.stasis.message.astchannel*_type | | Asterisk PJSIP Peers Qualify | asterisk.PJSIP.contacts.*.rtt |
Project: HertzBeat (Observability and Analysis / Observability)
File: dns.md

id: dns title: Monitoring DNS sidebar_label: DNS Monitor keywords: [ open source monitoring tool, open source DNS monitoring tool, monitoring DNS metrics ] Collect and monitor the general performance Metrics of DNS. Protocol UseDNS | Parameter name | Parameter help description | ||--| | Monitoring Host | Monitored IPV4, IPV6. NoteWithout protocol header (eg: https://, http://). | | Monitoring name | Identify the name of this monitoring. The name needs to be unique. | | Monitoring port | The port for DNS service provided to the outside,default is 53. | | Address For DNS | The address for domain name resolution. | | Connect Timeout | Set the timeout for connecting to the DNS server, default is 6000 milliseconds. | | Query Class | Resource class for DNS query. Optional values include `IN`, `CHAOS`, `HESIOD`, `NONE`, and `ANY`,default is IN. | | Use TCP Protocol | DNS queries use the TCP protocol. | | Collection interval | Interval time of monitor periodic data collection, unit: second, and the minimum interval that can be set is 30 seconds. | | Bind Tags | Used to classify and manage monitoring resources. | | Description remarks | For more information about identifying and describing this monitoring, users can note information here. | | Metric name | Metric unit | Metric help description | |-|-|| | Response Time | ms | Time taken for DNS server to respond to requests. | | Opcode | none | Type of the current message. | | Response Status | none | Status code of the response. | | Response Flags | none | Response flags. | | Question Record Count | none | Number of question records. | | Answer Record Count | none | Number of answer records. | | Authority Record Count | none | Number of authoritative resource records. | | Additional Record Count | none | Number of additional resource records. | | Metric name | Metric unit | Metric help description | |-|-|--| | Section | none | Question record information, including the queried domain name, resource type, resource record class, and additional information. | | Metric name | Metric unit | Metric help description | |-|-|-| | Section0 | none | Answer record information, including the queried domain name, TTL, resource record class, resource type, and query result. | The metric set collects up to 10 records, with metric names from Section0 to Section9. | Metric name | Metric unit | Metric help description | |-|-|-| | Section0 | none | SOA (Start of Authority) record for the domain name, including queried domain name, TTL, resource type, resource record class, and other information. | The metric set collects up to 10 records, with metric names from Section0 to Section9. | Metric name | Metric unit | Metric help description | |-|-|--| | Section0 | none | Additional information for DNS queries. | The metric set collects up to 10 records, with metric names from Section0 to Section9.
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_replicaSet.KubeReplicaSet.md

title: "Interface: KubeReplicaSet" linkTitle: "KubeReplicaSet" slug: "libk8sreplicaSet.KubeReplicaSet" .KubeReplicaSet `KubeReplicaSet` `Optional` apiVersion: `string` . _ kind: `string` Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. In CamelCase. Cannot be updated. `see` . _ metadata: . _ spec: `Object` | Name | Type | | : | : | | `minReadySeconds` | `number` | | `replicas` | `number` | | `selector` | | | `template` | { `metadata?`: ; `spec`: } | | `template.metadata?` | | | `template.spec` | | _ status: `Object` | Name | Type | | : | : | | `availableReplicas` | `number` | | `conditions` | `Omit`<, ``"lastProbeTime"`` \| ``"lastUpdateTime"``\>[] | | `fullyLabeledReplicas` | `number` | | `observedGeneration` | `number` | | `readyReplicas` | `number` | | `replicas` | `number` |
Project: Headlamp (Observability and Analysis / Observability)
File: lib_router.Route.md

title: "Interface: Route" linkTitle: "Route" slug: "lib_router.Route" .Route `Optional` disabled: `boolean` Whether the route should be disabled (not registered). _ `Optional` exact: `boolean` When true, will only match if the path matches the location.pathname exactly. _ `Optional` hideAppBar: `boolean` Hide the appbar at the top. _ `Optional` name: `string` Human readable name. Capitalized and short. _ `Optional` noAuthRequired: `boolean` This route does not require Authentication. _ `Optional` noCluster: `boolean` In case this route does not need a cluster prefix and context. `deprecated` please use useClusterURL. _ path: `string` Any valid URL path or array of paths that path-to-regexp@^1.7.0 understands. _ sidebar: ``null`` \| `string` \| { `item`: ``null`` \| `string` ; `sidebar`: `string` } The sidebar entry this Route should enable, or null if it shouldn't enable any. If an object is passed with item and sidebar, it will try to enable the given sidebar and the given item. _ `Optional` useClusterURL: `boolean` Should URL have the cluster prefix? (default=true) component(): `Element` Shown component for this route. `Element`
Project: Vector (Observability and Analysis / Observability)
File: influxdb_logs.md

title: InfluxDB logs description: Deliver log event data to component_kind: sink layout: component tags: ["influxdb", "influx", "component", "sink", "logs"] {{/* This doc is generated using: The template in layouts/docs/component.html The relevant CUE data in cue/reference/components/... */}}
Project: Netdata (Observability and Analysis / Observability)
File: versions.md

Netdata Cloud is provided in two versions: SaaS, we run and maintain Netdata Cloud and users use it to complement their observability with the additional features it provides. On Prem, we provide a licensed copy of the Netdata Cloud software, that users can install and run at their premises. The pricing of both versions is similar, with the On-Prem version introducing a monthly fixed-fee for the extra support and packaging required when users are running Netdata Cloud by themselves. For more information check our page. and start connecting your Netdata agents. The commands provided once you have signed up, include all the information to install and automatically connect (claim) Netdata agents to your Netdata Cloud space. To deploy Netdata Cloud On-premises, take a look at the on our Documentation.
Project: Grafana Pyroscope (Observability and Analysis / Observability)
File: sampling.md

title: "Sampling scrape targets" menuTitle: "Sampling targets" description: "Sampling scrape targets with the Grafana Agent" weight: 30 Applications often have many instances deployed. While Pyroscope is designed to handle large amounts of profiling data, you may want only a subset of the application's instances to be scraped. For example, the volume of profiling data your application generates may make it unreasonable to profile every instance, or you might be targeting cost-reduction. Through configuration of the Grafana Agent, Pyroscope can sample scrape targets. Before you begin, make sure you understand how to to scrape targets and are familiar with the Grafana Agent . The `hashmod` action and the `modulus` argument are used in conjunction to enable sampling behavior by sharding one or more labels. To read further on these concepts, see . In short, `hashmod` will perform an MD5 hash on the source labels and `modulus` will perform a modulus operation on the output. The sample size can be modified by changing the value of `modulus` in the `hashmod` action and the `regex` argument in the `keep` action. The `modulus` value defines the number of shards, while the `regex` value will select a subset of the shards. Note: Choose your source label(s) for the `hashmod` action carefully. They must uniquely define each scrape target or `hashmod` will not be able to shard the targets uniformly. For example, consider an application deployed on Kubernetes with 100 pod replicas, all uniquely identified by the label `pod_hash`. The following configuration is set to sample 15% of the pods: ```river discovery.kubernetes "profile_pods" { role = "pod" } discovery.relabel "profile_pods" { targets = concat(discovery.kubernetes.profile_pods.targets) // Other rule blocks ... rule { action = "hashmod" sourcelabels = ["podhash"] modulus = 100 targetlabel = "tmphashmod" } rule { action = "keep" sourcelabels = ["tmphashmod"] regex = "^([0-9]|1[0-4])$" } // Other rule blocks ... } ``` This strategy does not guarantee precise sampling. Due to its reliance on an MD5 hash, there is not a perfectly uniform distribution of scrape targets into shards. Larger numbers of scrape targets will yield increasingly accurate sampling. Keep in mind, if the label being hashed is deterministic, you will see deterministic sharding and thereby deterministic sampling of scrape targets. Similarly, if the label being hashed is non-deterministic, you will see scrape targets being sampled in a non-deterministic fashion.
Project: Grafana Loki (Observability and Analysis / Observability)
File: update-version-numbers.md

title: Update version numbers description: Update version numbers Upgrade the Loki version to the new release version in documents, examples, jsonnets, etc. Determine the . Skip this step if you are doing a patch release on old release branch. Example: Latest release branch is `release-2.9.x` but you are releasing patch version in `release-2.8.x` (or older) Upgrade the versions in the `release-VERSION_PREFIX` branch. Example commands: ``` LOKINEWVERSION=$VERSION ./tools/releaseupdatetags.sh ``` {{% admonition type="note" %}} Do not upgrade the version numbers in the `operator/` directory as @periklis and team have a different process to upgrade the Operator version. {{% /admonition %}}
Project: Netdata (Observability and Analysis / Observability)
File: dev.cpu.0.freq.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/freebsd.plugin/integrations/dev.cpu.0.freq.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/freebsd.plugin/metadata.yaml" sidebar_label: "dev.cpu.0.freq" learn_status: "Published" learnrelpath: "Collecting Metrics/FreeBSD" 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/freebsd.svg" width="150"/> Plugin: freebsd.plugin Module: dev.cpu.0.freq <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> Read current CPU Scaling frequency. Current CPU Scaling Frequency 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. The metric shows status of CPU frequency, it is direct affected by system load. This scope has no labels. Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | cpu.scalingcurfreq | frequency | MHz | There are no alerts configured by default for this integration. No action required. The configuration file name for this integration is `Config options`. Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file. You can edit the configuration file using the `edit-config` script from the Netdata . ```bash cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata sudo ./edit-config Config options ``` <details><summary></summary> | Name | Description | Default | Required | |:-|:--|:-|:--:| | dev.cpu.0.freq | Enable or disable CPU Scaling frequency metric. | yes | no | </details> There are no configuration examples.
Project: Litmus (Observability and Analysis / Chaos Engineering)
File: Shantanu_Deshpande.md

I was looking for a cloud-native way of introducing chaos and after going through the details and other options, Litmus was the best fit. Usage of Litmus is still in preliminary stages. A limited set of chaos experiments are being used for testing resiliency. This will change in the future, with more experiments planned to be adopted.