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

This document is intended to describe high-level plans for the Chaos Mesh project and is neither comprehensive nor prescriptive. For a more granular view of planned work, please refer to the project's upcoming . [x] Support time skew chaos. Simulate time jumping forward or backward. [x] Add container kill chaos. Simulate killing a specified container in a multi-container pod. [x] Add CPU chaos. Simulate CPU being busy. [x] Add memory chaos. Simulate memory allocation failure. [x] Make scheduler optional. Support single time chaos triggering. [x] Support helm-less install. [x] Support force clean finalizer with annotation. [x] Support the basic version of Chaos Dashboard. [x] Improve Chaos Dashboard and make it easier to use [x] Support status checks. A status check is used to evaluate the health of your environment. [x] Support defining the scenario to manage a group of chaos experiments. [x] Support generating the report for each chaos scenario. [x] Add JVM chaos. Support injecting faults into Java applications. [x] Add HTTP Chaos. Support injecting faults into http connections. [ ] Add GRPC Chaos. Support injecting faults into GRPC connections. [ ] Support injecting faults into native components of Kubernetes. [x] Manage and schedule chaos experiments on Kubernetes targets and non-Kubernetes targets on a unified dashboard. [x] Improve JVMChaos and support dynamic injection. [ ] Support injecting faults into native components of Kubernetes. [ ] More comprehensive status inspection mechanism and reports. [ ] Improve observability via events logs and metrics. [ ] Improve authentication system, and support using GCP/AWS account to log in chaos dashboard. [ ] Add GRPC Chaos. Support injecting faults into GRPC connections. [ ] A new component to force recovery chaos experiments, and avoid experiments going out of control. [ ] Build a hub for users sharing their own chaos workflow and chaos types. [ ] Support doing chaos experiments on multiple Kubernetes clusters. [ ] Provide a plugin approach to extend complex chaos types, such as RabbitMQChaos, RedisChaos... [ ] Continue to enrich fault types.
Project: Elastic (Observability and Analysis / Observability)
File: date_format.md

<!-- This is generated by ESQL's AbstractFunctionTestCase. Do no edit it. See ../README.md for how to regenerate it. --> Returns a string representation of a date, in the provided format. ``` FROM employees | KEEP firstname, lastname, hire_date | EVAL hired = DATEFORMAT("YYYY-MM-dd", hiredate) ```
Project: PowerfulSeal (Observability and Analysis / Chaos Engineering)
File: http-proxy.md

layout: default title: Different proxies for probes description: "" permalink: /http-proxy-http_proxy parent: Writing policies nav_order: 7 {: .no_toc } {: .no_toc .text-delta } TOC {:toc} Sometimes you need different proxies for different HTTP probes. ```yaml scenarios: name: Proxies steps: probeHTTP: target: service: name: myservice namespace: example port: 8000 probeHTTP: target: url: https://something.somewhere.com proxy: http://some-proxy:8080 probeHTTP: target: url: https://something.somewhere.com ```
Project: Botkube (Observability and Analysis / Observability)
File: botkube.md

title: botkube Botkube CLI botkube - Botkube CLI A utility that simplifies working with Botkube. Quick Start: $ botkube install # Install Botkube $ botkube uninstall # Uninstall Botkube Botkube Cloud: $ botkube login # Login into Botkube Cloud $ botkube migrate # Automatically migrates Open Source installation into Botkube Cloud ``` botkube [flags] ``` ``` -h, --help help for botkube -v, --verbose int/string[=simple] Prints more verbose output. Allowed values: 0 - disable, 1 - simple, 2 - trace (default 0 - disable) ``` - This command consists of multiple subcommands for working with Botkube configuration - install or upgrade Botkube in k8s cluster - Login to a Botkube Cloud - Automatically migrates Botkube installation into Botkube Cloud - Configure collection of anonymous analytics - uninstall Botkube from cluster - Print the CLI version
Project: Headlamp (Observability and Analysis / Observability)
File: platforms.md

title: Tested Kubernetes, Desktop and Browser Platforms linkTitle: Platforms weight: 300 This section shows the different platforms where Headlamp has been tested (in-cluster) or is intended to be tested, and useful observations about it. If you have tested Headlamp on a different flavor or Kubernetes, please file a PR or to add your remarks to the list. The "works" column refers to the overall Kubernetes related functionality when running in the respective platform; it may have 3 different values: : Has been tried and works fine to the extent of what has been tested : Has been tried and didn't work or had issues that prevented a regular use of it : Hasn't been tried/reported yet Platform<div style="min-width: 300px"></div> | Works | Comments -|:--:| | | - As reported . | | Worked fine in-cluster and also working perfectly while using kubeconfig file with headlamp application. | | - Have you tried Headlamp on this platform? Please report your experience. | | - Have you tried Headlamp on this platform? Please report your experience. | | - Simple to install / expose with the regular . | | - Simple to install / expose with the regular . | | - Testing (not suitable for production):<br/>- Deploy Headlamp from the <br/>- (this creates a DNS zone)<br/>- Use the DNS zone name as the domain for Headlamp, i.e. if it is `1234567.eastus.aksapp.io`, then apply using `headlamp.1234567.eastus.aksapp.io` as the path and use ``kubernetes.io/ingress.class: addon-http-application-routing`` as the ingress class annotation.<br/><br/>For production, please follow the . | | - For exposing with an ingress, enable ingresses with `minikube addons enable ingress`: <br> - There are docs about the with Minikube.| | | - Simple to install / expose with the regular . We mostly test with 'modern browsers' defined as the latest version and two older versions. But we try to make Headlamp work with web standards, so it's quite likely other standards conforming browsers will also work. Platform<div style="min-width: 300px"></div> | Works | Comments -|:--:| Edge | | Safari | | Firefox | | Chrome | | Internet Explorer 11 | | We test on MacOS, various flavours of Linux, and Windows. Headlamp runs in the browser, but also as an App. Platform<div style="min-width: 300px"></div> | Works | Comments -|:--:| Windows 10, 11 (including in WSL2) | | MacOS (arm, x86) | | Ubuntu 20.04, 22.04, 22.10 | | Fedora | |
Project: Netdata (Observability and Analysis / Observability)
File: 1hour_ecc_memory_correctable.md

This alert, `1houreccmemory_correctable`, monitors the number of Error Correcting Code (ECC) correctable errors that occur within an hour. If you receive this alert, it means that there are ECC correctable errors in your system's memory. While it does not pose an immediate threat, it may indicate that a memory module is slowly deteriorating. ECC memory is a type of computer data storage that can detect and correct the most common kinds of internal data corruption. It is used in systems that require high reliability and stability, such as servers or mission-critical applications. Inspect the memory modules If the alert is triggered, start by physically checking the memory modules in the system. Ensure that the contacts are clean, and all modules are firmly seated in their respective slots. Perform a memory test Run a thorough memory test using a tool like Memtest86+. This will help identify if any memory chips have problems that can cause the ECC errors. ``` sudo apt-get install memtester sudo memtester 1024M 5 ``` Replace `1024M` with the amount of memory you'd like to test (in MB) and `5` with the number of loops for the test. Monitor the errors Monitor the frequency of ECC correctable errors. Keep a record of when they occur and if there are any patterns or trends. If errors continue to occur, move to step 4. Replace faulty memory modules If ECC correctable errors persist, identify the memory modules with the highest error rates and consider replacing them as a preventive measure. This will help maintain the reliability and stability of your system.
Project: Checkmk (Observability and Analysis / Observability)
File: 16553.md

key | value | date | 2024-04-16T13:05:49+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes Previously, the active check "HTTP web service" failed to parse the site's password store when there was at least one stored password containing whitespaces. This was observable when configuring "Authentication" with a password from password store, and resulted in a CRIT state and an error message like ``` error: invalid value 'httppass' for '--auth-pw-pwstore <AUTHPW_PWSTORE>': Can't parse password store: Unexpected format. ``` in the service's summary.
Project: Keep (Observability and Analysis / Observability)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Go to '...' Click on '....' Scroll down to '....' See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: [e.g. iOS] Browser [e.g. chrome, safari] Version [e.g. 22] Smartphone (please complete the following information): Device: [e.g. iPhone6] OS: [e.g. iOS8.1] Browser [e.g. stock browser, safari] Version [e.g. 22] Additional context Add any other context about the problem here.
Project: HertzBeat (Observability and Analysis / Observability)
File: alert_threshold.md

id: alert_threshold title: Threshold alarm configuration sidebar_label: Threshold alarm configuration Configure the alarm threshold (warning alarm, critical alarm, emergency alarm) for the monitoring Metrics, and the system calculates and triggers the alarm according to the threshold configuration and the collected Metric data. Alarm configuration->Add new threshold-> Confirm after configuration As shown above Metric objectSelect the monitoring Metric object for which we need to configure the threshold. Egwebsite monitoring type -> summary Metric set -> responseTime-response time Metric Threshold trigger expressionCalculate and judge whether to trigger the threshold according to this expression. See the page prompts for expression environment variables and operators. Egset the response time greater than 50 to trigger an alarm, and the expression is `responseTime > 50`. For detailed help on threshold expression, see Alarm levelThe alarm level that triggers the threshold, from low to high: warning, critical, emergency. Trigger timesHow many times will the threshold be triggered before the alarm is really triggered. Notification templateNotification information Template sent after alarm triggering, See page prompts for template environment variables, eg`${app}.${metrics}.${metric} Metric's value is ${responseTime}, greater than 50 triggers an alarm` Global default Set whether this threshold is valid for such global Metrics, and the default is No. After adding a new threshold, you need to associate the threshold with the monitoring object, so that the threshold will take effect for this monitoring. Enable alarmThis alarm threshold configuration is enabled or disabled. Threshold association monitoring Alarm configuration-> Threshold just set-> Configure associated monitoring-> Confirm after configuration Note After adding a new threshold, you need to associate the threshold with the monitoring object(That is, to set this threshold for which monitoring is effective), so that the threshold will take effect for this monitoring. After the threshold alarm is configured, the alarm information that has been successfully triggered can be seen in alarm center. If you need to notify the relevant personnel of the alarm information by email, Wechat, DingDing and Feishu, it can be configured in alarm notification. Other issues can be fed back through the communication group ISSUE!
Project: Prometheus (Observability and Analysis / Observability)
File: usage.md

TSDB can be - and is - used by other applications such as , , and . This directory contains documentation for any developers who wish to work on or with TSDB. For a full example of instantiating a database, adding and querying data, see the . `tsdb/db_test.go` also demonstrates various specific usages of the TSDB library. Callers should use to open a TSDB (the directory may be new or pre-existing). This returns a which is the actual database. A `DB` has the following main components: Compactor: a . Note: it is currently the only compactor implementation. It runs automatically. The `Head` is responsible for a lot. Here are its main components: (Write Ahead Log). : this holds all the active series by linking to by an ID (aka "ref") and by labels hash. Postings list (reverse index): For any label-value pair, holds all the corresponding series refs. Used for queries. Tombstones. Use to obtain an "appender". The speak mostly for themselves. Remember: Use `Commit()` to add the samples to the DB and update the WAL. Create a new appender each time you commit. Appenders are not concurrency safe, but scrapes run concurrently and as such, leverage multiple appenders concurrently. This reduces contention, although Commit() contend the same critical section (writing to the WAL is serialized), and may inflate append tail latency if multiple appenders try to commit at the same time. Append may reject data due to these conditions: 1) `timestamp < minValidTime` where `minValidTime` is the highest of: the maxTime of the last block (i.e. the last truncation time of Head) - updated via and `tsdb.min-block-duration/2` older than the max time in the Head block. Note that while technically `storage.tsdb.min-block-duration` is configurable, it's a hidden option and changing it is discouraged. So We can assume this value to be 2h. Breaching this condition results in "out of bounds" errors. The first condition assures the block that will be generated doesn't overlap with the previous one (which simplifies querying) The second condition assures the sample won't go into the so called "compaction window", that is the section of the data that might be in process of being saved into a persistent block on disk. (because that logic runs concurrently with ingestion without a lock) 2) The labels don't validate. (if the set is empty or contains duplicate label names) 3) If the sample, for the respective series (based on all the labels) is out of order or has a different value for the last (highest) timestamp seen. (results in `storage.ErrOutOfOrderSample` and `storage.ErrDuplicateSampleForTimestamp` respectively) `Commit()` may also refuse data that is out of order with respect to samples that were added via a different appender. Use to obtain a "querier". The speak mostly for themselves. Remember: A querier can only see data that was committed when it was created. This limits the lifetime of a querier. A querier should be closed when you're done with it. Use mint/maxt to avoid loading unneeded data. Find the example code for ingesting samples and querying them in
Project: Checkmk (Observability and Analysis / Observability)
File: 16693.md

key | value | date | 2024-04-20T13:55:35+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes Due to a memory leak in the underlying library, Checkmk was using the 'classic' SNMP backend for all SNMPv1 hosts regardless of the user configuration. This memory leak has since been fixed, so we remove the fallback.
Project: Netdata (Observability and Analysis / Observability)
File: vsphere_inbound_packets_errors.md

The `vsphereinboundpackets_errors` alert is generated when there are inbound network errors in a VMware vSphere virtual machine. It calculates the number of inbound errors for the network interface in the last 10 minutes. If you receive this alert, it indicates that your virtual machine's network is experiencing errors, which could lead to issues with network performance, reliability, or availability. There are several reasons for network errors, including: Faulty hardware: physical problems with network adapters, cables, or switch ports. Configuration issues: incorrect network settings or driver issues. Network congestion: heavy traffic leading to packet loss or delays. Corrupted packets: data transmission errors caused by software bugs or electro-magnetic interference. Follow these steps to troubleshoot the `vsphereinboundpackets_errors` alert: Log in to the vSphere client and select the affected virtual machine. Check the VM's network settings: Verify that the network adapter is connected. Check if the network adapter's driver is up-to-date. Review network performance: Examine the virtual machine's performance charts to identify high network utilization or packet loss. Use network monitoring tools, like `ping`, `traceroute`, and `mtr`, to check the network connectivity and latency. Inspect the physical network: Look for damaged cables or disconnected switch ports. Ensure that the network equipment, like switches and routers, is operating correctly and is up-to-date. Analyze system logs: Check the virtual machine's logs for any network-related errors or warnings. Investigate the vSphere host logs for issues involving network hardware or configurations. If errors persist, consult VMware support or documentation for further guidance.
Project: Grafana (Observability and Analysis / Observability)
File: release-notes-8-5-4.md

aliases: [] hide_menu: true labels: products: cloud enterprise oss title: Release notes for Grafana 8.5.4 <!-- Auto generated by update changelog github action --> Alerting: Remove disabled flag for data source when migrating alerts. , Alerting: Show notification tab of legacy alerting only to editor. , Alerting: Update migration to migrate only alerts that belong to existing org\dashboard. , AzureMonitor: Do not quote variables when a custom "All" variable option is used. , AzureMonitor: Update allowed namespaces. , CloudMonitor: Correctly encode default project response. , Cloudwatch: Add support for new AWS/RDS EBS\* metrics. , InfluxDB: Use backend for influxDB by default via feature toggle. , Legend: Use correct unit for percent and count calculations. , LokI: use millisecond steps in Grafana 8.5.x. , Plugins: Introduce HTTP 207 Multi Status response to api/ds/query. , Reporting: Improve PDF file size using grid layout. (Enterprise) Transformations: Add an All Unique Values Reducer. , Transformers: avoid error when the ExtractFields source field is missing. , , [v8.5.x] Reporting: Improve PDF file size using grid layout. (Enterprise) Alerting: Allow disabling override timings for notification policies. , Alerting: Allow serving images from custom url path. , Alerting: Apply Custom Headers to datasource queries. , Alerting: Fix RBAC actions for notification policies. , Alerting: Fix access to alerts for viewer with editor permissions when RBAC is disabled. , Alerting: Fix anonymous access to alerting. , Alerting: correctly show all alerts in a folder. , AzureMonitor: Fixes metric definition for Azure Storage queue/file/blob/table resources. , Dashboard: Fix dashboard update permission check. , DashboardExport: Fix exporting and importing dashboards where query data source ended up as incorrect. , FileUpload: clicking the `Upload file` button now opens the modal correctly. , GrafanaUI: Fix color of links in error Tooltips in light theme. , LibraryPanels: Fix library panels not connecting properly in imported dashboards. , Loki: Improve unpack parser handling. , RolePicker: Fix menu position on smaller screens. , TimeRange: Fixes updating time range from url and browser history. , TimeSeries: Fix detection & rendering of sparse datapoints. , Timeseries: Fix outside range stale state. , Tooltip: Fix links not legible in Tooltips when using light theme. , Tooltip: Sort decimals using standard numeric compare. , Transforms: Labels to fields, fix label picker layout. , Variables: Fixes issue with data source variables not updating queries with variable. , , , , For a data source query made via /api/ds/query : If the `DatasourceQueryMultiStatus` feature is enabled and The data source response has an error set as part of the `DataResponse`, the resulting HTTP status code is now `207 Multi Status` instead of `400 Bad gateway` If the `DatasourceQueryMultiStatus` feature is not enabled and The data source response has an error set as part of the `DataResponse`, the resulting HTTP status code is `400 Bad Request` (no breaking change) --> Issue
Project: Pinpoint (Observability and Analysis / Observability)
File: BUILD.md

``` mvnw install -Dmaven.test.skip=true ``` ``` mvnw install -pl agent -am -Dmaven.test.skip=true ``` ``` mvnw install -pl collector -am -Dmaven.test.skip=true ``` ``` mvnw install -pl web -am -Dmaven.test.skip=true ``` Skip frontend build ``` mvnw install -pl web -am -Dbuild.frontend.skip=true -Dmaven.test.skip=true ```
Project: Graylog (Observability and Analysis / Observability)
File: ProgressBar.md

```js <ProgressBar bars={[{ value: 35 }]} /> ``` ```js const value = 60; <ProgressBar bars={[{ value, label: `${value}%` }]} /> ``` ```js <div> <ProgressBar bars={[{ value: 70, bsStyle: 'primary' }]} /> <ProgressBar bars={[{ value: 40, bsStyle: 'success' }]} /> <ProgressBar bars={[{ value: 20, bsStyle: 'info' }]} /> <ProgressBar bars={[{ value: 60, bsStyle: 'warning' }]} /> <ProgressBar bars={[{ value: 80, bsStyle: 'danger' }]} /> </div> ``` ```js <div> <ProgressBar bars={[{ value: 40, bsStyle: 'success', striped: true }]} /> <ProgressBar bars={[{ value: 20, bsStyle: 'info', striped: true }]} /> <ProgressBar bars={[{ value: 60, bsStyle: 'warning', striped: true }]} /> <ProgressBar bars={[{ value: 80, bsStyle: 'danger', striped: true }]} /> </div> ``` ```js <ProgressBar bars={[{ value: 45, bsStyle: 'danger', animated: true }]} /> ``` ```js <ProgressBar bars={[ { value: 35, bsStyle: 'success', striped: true }, { value: 20, bsStyle: 'warning' }, { value: 10, bsStyle: 'danger', animated: true } ]} /> ```
Project: Checkmk (Observability and Analysis / Observability)
File: 16631.md

key | value | date | 2024-04-12T08:34:09+00:00 version | 2.4.0b1 class | fix edition | cre component | packages level | 1 compatible | yes Due to a recent change in Microsoft 365, the access to Exchange mailbox folders via the active check `check_mailboxes` could fail with an error message like this: ``` Unhandled exception: ErrorAccessDenied('Not allowed to access Non IPM folder.') ``` With this werk we update the version of the package `exchangelib` to v5.2.1, fixing the respective error handling.