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

key | value | date | 2024-02-08T17:25:53+00:00 version | 2.4.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes In support for labels in CSV exports was removed (among other things). Instead, for affected columns a constant `"NOTCSVEXPORTABLE"` value was exported. This change reintroduces host & service labels as JSON serialized strings. This only relates to CSV exports, other formats are not affected. Sample export: ```csv "host";"host_labels" "test";"{""cmk\/osplatform"": ""linux"", ""cmk\/osfamily"": ""linux"", ""cmk\/checkmkserver"": ""yes"", ""cmk\/site"": ""test""}" "dummy";"{""my_label"": ""works""}" "nothing";"{}" ```
Project: Netdata (Observability and Analysis / Observability)
File: ioping_disk_latency.md

This alert presents the average `I/O latency` over the last 10 seconds. `I/O latency` is the time that is required to complete a single I/O operation on a block device. This alert might indicate that your disk is under high load, or that the disk is slow. Check per-process I/O usage: Use `iotop` to see the processes that are the main I/O consumers: ``` sudo iotop ``` If you don't have `iotop` installed, then Analyze the running processes: Investigate the top I/O consumers and determine if these processes are expected to consume that much I/O, or if there might be an issue with these processes. Minimize the load by closing any unnecessary main consumer processes: If you find that any unnecessary or unexpected processes are heavily utilizing your disk, try stopping or closing those processes to reduce the load on the disk. Always double-check if the process you want to close is necessary. Verify your disk health: Make sure your disk is not facing any hardware issues or failures. For this, you can use the `smartmontools` package, which contains the `smartctl` utility. If it's not installed, you can . To check the disk health, run: ``` sudo smartctl -a /dev/sdX ``` Replace `/dev/sdX` with the correct disk device identifier (for example, `/dev/sda`). Consider upgrading your disk: If your disk consistently experiences high latency and you have already addressed any performance issues with the running processes, consider upgrading your disk to a faster drive (e.g., replace an HDD with an SSD).
Project: Flagsmith (Observability and Analysis / Feature Flagging)
File: newrelic.md

title: New Relic Analytics Integration description: Integrate Flagsmith with New Relic sidebar_label: New Relic hide_title: true You can integrate Flagsmith with New Relic. Send flag change events from Flagsmith into your New Relic event stream. Log into New Relic and navigate to the APM project that you want to integrate with. Make a note of the `App ID`. Generate a New Relic API key. Account Settings > API keys > Create Key. The Key type is `User`. Go to your Flagsmith project, and click Integrations. Add the New Relic Integration. Enter the New Relic `API Key` and `App ID`. For the API URL, enter either: `https://api.newrelic.com/` for the US datacenter `https://api.eu.newrelic.com/` for the EU datacenter Click Save. Flag change events will now be sent to New Relic as `Deployments`.
Project: Flagsmith (Observability and Analysis / Feature Flagging)
File: LICENSE.md

Copyright (c) 2024 Bullet Train Ltd (https://www.flagsmith.com/) and individual contributors. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Project: Jaeger (Observability and Analysis / Observability)
File: storage-file-non-root-permission.md

After the release of 1.50, Jaeger's Docker image is no longer running with root privileges (in ). In some installations it may cause issues such as "permission denied" errors when writing data. A possible workaround for this () is to run an initialization step as `root` that pre-creates the Badger data directory and updates its owner to the user that will run the main Jaeger process. ```yaml version: "3.9" services: [...] jaeger: image: jaegertracing/all-in-one:latest command: "--badger.ephemeral=false" "--badger.directory-key=/badger/data/keys" "--badger.directory-value=/badger/data/values" "--badger.span-store-ttl=72h0m0s" # limit storage to 72hrs environment: SPANSTORAGETYPE=badger volumes: jaegerbadgerdata:/badger ports: "16686:16686" "14250" "4317" depends_on: prepare-data-dir: condition: servicecompletedsuccessfully prepare-data-dir: user: root image: jaegertracing/all-in-one:latest command: "/bin/sh -c 'mkdir -p /badger/data && touch /badger/data/.initialized && chown -R 10001:10001 /badger/data'" volumes: jaegerbadgerdata:/badger volumes: jaegerbadgerdata: ```
Project: Sentry (Observability and Analysis / Observability)
File: recording_consumer.md

This file defines the contract between the recording consumer and its producers. All messages are transmitted as `msgpack` encoded bytes. Messages smaller than 1MB in size are processed as one message. Their structure is defined in the "Small Recordings" section. All other message types are defined in the "Large Recordings" section. Authors: @cmanallen | Column | Type | Description | | - | | - | | type | string | Literal: replayrecordingnot_chunked | | replay_id | string | - | | key_id | Optonal[int] | - | | org_id | int | - | | project_id | int | - | | received | int | Unix timestamp of when the event was received | | payload | bytes | JSON encoded headers are prefixed to the payload. | Request (application/octet-stream) ```python { "type": "replayrecordingnot_chunked", "replay_id": "515539018c9b4260a6f999572f1661ee", "key_id": 1, "org_id": 132, "project_id": 10459681, "received": 1342632621, "payload": b"{'segment_id': 0}\n\x14ftypqt\x00\x00\x00\x00qt\x00\x00x08wide\x03\xbdd\x11mdat" } ``` | Column | Type | Description | | -- | | - | | type | string | Literal: replayrecordingchunk | | replay_id | string | - | | project_id | int | - | | chunk_index | int | - | | id | string | - | | payload | bytes | - | Request (application/octet-stream) ```python { "type": "replayrecordingchunk", "replay_id": "515539018c9b4260a6f999572f1661ee", "project_id": 1, "chunk_index": 10, "id": "e4a28052c54743a286be419c9d168ef5", "payload": b"\x14ftypqt\x00\x00\x00\x00qt\x00\x00x08wide\x03\xbdd\x11mdat" } ``` | Column | Type | Description | | - | | -- | | type | string | Literal: replay_recording | | replay_id | string | - | | key_id | Optonal[int] | - | | org_id | int | - | | project_id | int | - | | received | int | Unix timestamp of when the event was received | | replay_recording | dict | Contains the number of chunks and a unique identifier | Request (application/octet-stream) ```python { "type": "replay_recording", "replay_id": "515539018c9b4260a6f999572f1661ee", "key_id": 1, "org_id": 132, "project_id": 10459681, "received": 1342632621, "replay_recording": { "id": "e4a28052c54743a286be419c9d168ef5", "chunks": 5 } } ```
Project: Netdata (Observability and Analysis / Observability)
File: 1m_tcp_syn_queue_cookies.md

This alert presents the average number of sent SYN cookies due to the full TCP SYN queue over the sixty seconds. Receiving this means that the incoming traffic is excessive. SYN queue cookies are used to resist any potential SYN flood attacks. This alert is raised to warning when the average exceeds 1 and will enter critical when the value exceeds an average of 5 sent SYN cookies in sixty seconds. The SYN Queue stores inbound SYN packets (specifically: struct inetrequestsock). It is responsible for sending out SYN+ACK packets and retrying them on timeout. After transmitting the SYN+ACK, the SYN Queue waits for an ACK packet from the client - the last packet in the three-way-handshake. All received ACK packets must first be matched against the fully established connection table, and only then against data in the relevant SYN Queue. On SYN Queue match, the kernel removes the item from the SYN Queue, successfully creates a full connection (specifically: struct inet_sock), and adds it to the Accept Queue. This alert likely indicates a SYN flood. A SYN flood is a form of denial-of-service attack in which an attacker rapidly initiates a connection to a server without finalizing the connection. The server has to spend resources waiting for half-opened connections, which can consume enough resources to make the system unresponsive to legitimate traffic. If the traffic is legitimate, then increase the limit of the SYN queue. If you can determine that the traffic is legitimate, consider expanding the limit of the SYN queue through configuration; (If the traffic is not legitimate, then this is not safe! You will expose more resources to an attacker if the traffic is not legitimate.) Open the /etc/sysctl.conf file and look for the entry "net.core.somaxconn". This value will affect both SYN and accept queue limits on newer Linux systems. Set the value accordingly (By default it is set to 128) `net.core.somaxconn=128` (if the value doesn't exist, append it to the file) Save your changes and run this command to apply the changes. ``` sysctl -p ``` Note: Netdata strongly suggests knowing exactly what values you need before making system changes.
Project: Elastic (Observability and Analysis / Observability)
File: mv_max.md

<!-- This is generated by ESQL's AbstractFunctionTestCase. Do no edit it. See ../README.md for how to regenerate it. --> Converts a multivalued expression into a single valued column containing the maximum value. ``` ROW a=[3, 5, 1] | EVAL maxa = MVMAX(a) ```
Project: Vector (Observability and Analysis / Observability)
File: SUPPORT.md

Vector is a growing open source project with a variety of people willing to help you through various mediums. Take a look at those mediums listed at <https://vector.dev/community> Whether in our community server or , framing your question well and providing the right level of details will improve your chances of getting your question answered. Here are some tips: Check the first to see if it answers your question. If your question is about , you can also try out the . If the docs do not answer your question, try using the search feature on or , to search for keywords related to your issue. It is quite possible someone has already asked your question before. This is especially useful if you have a specific error message you are observing. Essential details to include: Errors- for each error, please provide the full error message snippet, and details such as where the error is observed, at what stage in the process (e.g. at boot time, after some specific condition etc.). What is the version of Vector (and the Helm chart if deploying via Helm) and the versions of any other systems in use (like Elasticsearch, NATS, etc.). What is your Vector configuration. See the below section on [how to format your config](#formatting). How are you Vector? What is your complete deployment architecture? For example: I have Logstash agents sending to Vector over syslog that is being forwarded to Loki. Situation specific (not exhaustive): Did it occur after upgrading to a new version of Vector? Are you trying out Vector for the first time, or did you have a previous working configuration? These are just some examples of questions that may or may not apply to your situation. When providing snippets of configuration files, or log messages, format these with backticks to improve the legibility for readers. Blocks should be formatted with three backticks (\`\`\`) This should be used for any configuration snippets of Vector, Helm values, etc. and for Vector console log messages. See the for an explanation. For example: [sinks.sink0] inputs = ["source0"] target = "stdout" type = "console" should be written as ```toml [sinks.sink0] inputs = ["source0"] target = "stdout" type = "console" ``` Formatting things like component names, versions etc. is done with single backticks (\`) around the word or phrase. This is less critical but also helps readability a lot and is greatly appreciated. See the for an explanation. For example: We upgraded from v24 to 25.1 and are seeing the following error output from kafka. should be written as We upgraded from `v0.24.0` to `v0.25.1` and are seeing the following error output from the `kafka` sink.
Project: Graylog (Observability and Analysis / Observability)
File: Alert.md

```tsx <Alert> Default - Lorem ipsum dolor sit amet consectetur adipisicing elit. </Alert> ``` ```tsx const styles = ['Danger', 'Info', 'Success', 'Warning']; styles.map((style, i) => { return ( <Alert bsStyle={style.toLowerCase()} key={`button-${style}-${i}`}> {style} - Lorem ipsum dolor sit amet consectetur adipisicing elit. </Alert> ) }) ``` ```tsx <Alert title="The Title"> Lorem ipsum dolor sit amet consectetur adipisicing elit. </Alert> ``` ```tsx import Icon from 'components/common/Icon'; <Alert onDismiss={() => window.alert('You clicked on the alert close icon.')}> Lorem ipsum dolor sit amet consectetur adipisicing elit. </Alert> ```
Project: Checkmk (Observability and Analysis / Observability)
File: 16480.md

key | value | date | 2024-02-12T09:14:03+00:00 version | 2.4.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes When retrieving BI availability timeline data for a time range greater than one month the livestatus query is split into multiple queries. The reason for this is to avoid reaching the maximum limit for the size of the livestatus response.
Project: Checkmk (Observability and Analysis / Observability)
File: 16651.md

key | value | date | 2024-04-04T13:12:06+00:00 version | 2.4.0b1 class | feature edition | cee component | agents level | 1 compatible | yes Multiple matching rules of the bakery configuration ruleset "TSM - IBM Tivoli Storage Manager (Linux, Unix)" will now be merged to compute the set of effective parameters. Previously only the first matching rule was applied. During the migration to Checkmk 2.4 existing rules will be "filled", such that the outcome of the rule evaluation will not change on existing configurations.
Project: Netdata (Observability and Analysis / Observability)
File: load_average_5.md

This alarm calculates the system `load average` (CPU and I/O demand) over the period of five minutes. If you receive this alarm, it means that your system is "overloaded." The alert gets raised into warning if the metric is 4 times the expected value and cleared if the value is 3.5 times the expected value. For further information on how our alerts are calculated, please have a look at our . 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 or I/O bound First you need to check if you are running on a CPU load or an I/O load problem. 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. List your currently running processes using the `ps` command: The `grep` command will fetch the processes that their state code starts either with R (running or runnable (on run queue)) or D(uninterruptible sleep (usually IO)). 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. 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: Grafana Pyroscope (Observability and Analysis / Observability)
File: feature_request.md

name: Feature request about: Suggest an idea for Pyroscope. title: '' labels: '' assignees: '' A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] A clear and concise description of what you want to happen. A clear and concise description of any alternative solutions or features you've considered. Add any other context or screenshots about the feature request here.
Project: Vector (Observability and Analysis / Observability)
File: tag_cardinality_limit.md

title: Tag cardinality limit description: Limit the cardinality of tags on metrics events as a safeguard against cardinality explosion component_kind: transform layout: component tags: ["tag", "cardinality", "component", "transform", "metrics"] {{/* This doc is generated using: The template in layouts/docs/component.html The relevant CUE data in cue/reference/components/... */}}
Project: Flipt (Observability and Analysis / Feature Flagging)
File: README.md

](https://pkg.go.dev/go.flipt.io/flipt/sdk/go) The Flipt Go SDK supports developing applications in Go against Flipt. It also supports the ability to access the resource management APIs and other systems, such as authentication and metadata. The SDK supports both Flipts `gRPC` and `HTTP` RPC APIs. A majority of this client is generated directly from Flipt's `protobuf` definitions. The can be found locally within this repository. Go `>= v1.20` | client / server | <= 1.19.\* | >= 1.20.0 | | - | - | | | 0.1.\ | | \ | | >= 0.2.\* | | | \* Backwards compatible, but can only access the `"default"` namespace. ```sh go get go.flipt.io/flipt/sdk/go ``` Constructing an SDK client is easy. Pick your transport of choice. Both`grpc` or `http` are sub-packages with respective implementations. Pass a constructed `Transport` implementation to `sdk.New(...)`. Optionally pass in a `sdk.ClientAuthenticationProvider` to authenticate your RPC calls. ```go package main import ( sdk "go.flipt.io/flipt/sdk/go" sdkgrpc "go.flipt.io/flipt/sdk/go/grpc" grpc "google.golang.org/grpc" ) func main() { token := sdk.StaticTokenAuthenticationProvider("a-flipt-client-token") conn := grpc.Dial("localhost:9090") transport := sdkgrpc.NewTransport(conn) client := sdk.New(transport, sdk.WithAuthenticationProvider(token)) } ```
Project: Checkmk (Observability and Analysis / Observability)
File: 16600.md

key | value | date | 2024-03-15T14:10:08+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes As of Checkmk version 2.3.0b4, the special agent "NetApp via WebAPI" (agentnetapp_) is deprecated and will be removed in a future version. This also affects the associated checks and inventory plugins: NetApp Filer: Cluster-Mode CPU Utilization (netappapiaggr) NetApp Ontap Filer: 7Mode Cluster Status (netappapicluster) NetApp API Connection (netappapiconnection) NetApp Filer: Cluster-Mode CPU Utilization (netappapicpu) NetApp Clustermode Filer: NVRAM Battery (netappapicpunvrambat) NetApp Filer: 7Mode Global CPU Utilization (netappapicpuutilization_) NetApp Filer: Disk (Summarynetappapidisksummary_) NetApp Filer Clustermode: PSU Fault Info (netappapienvironment) NetApp Filer Clustermode: System Electrical Current (netappapienvironmentcurrent_) NetApp Filer Clustermode: Fan Fault Info (netappapienvironmentfanfaults) NetApp Filer Clustermode: System Fan Speed (netappapienvironmentfans_) NetApp Filer Clustermode: System Temperature (netappapienvironmenttemperature_) NetApp Filer Clustermode: System Electrical Voltage (netappapienvironmentvoltage_) NetApp Filer: FANs (netappapifan) NetApp Filer: FANs Summary (netappapifansummary_) NetApp Cluster-Mode: State of Fibrechannel Interfaces (netappapifcp) NetApp Filer: State of Network Interfaces (netappapiif) NetApp Filer: Version Info (netappapiinfo) NetApp Filer: Used Space of LUNs (netappapiluns) NetApp Filer: Ports (netappapiports) NetApp Filer 7Mode: Protocols (netappapiprotocol) NetApp Filer: Power Supplies (netappapipsu) NetApp Filer: Power Supplies Summary (netappapipsusummary_) NetApp Filer: Used Space of qtrees in Volumes (netappapiqtreequota_) NetApp Filer: Used Space in Snapshots of Volumes (netappapisnapshots) NetApp Filer: Snapvault/Snapmirror Lag-time (netappapisnapvault) NetApp Filer: Overall System Health (netappapistatus) NetApp Filer: Systemtime (netappapisystemtime) NetApp Filer: Temperature Sensors (netappapitemp) NetApp Filer 7Mode: vFiler CPU Utilization (netappapivfstats_) NetApp Filer: vFiler Traffic (netappapivfstatstraffic) NetApp Filer: vFiler Status (netappapivfstatus_) NetApp Filer: Used Space and Traffic of Volumes (netappapivolumes) NetApp Filer: vServer Status (netappapivsstatus_) NetApp Filer: vServer Traffic Summary (netappapivstraffic_)