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

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/integrations/zram.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/metadata.yaml" sidebar_label: "ZRAM" learn_status: "Published" learnrelpath: "Collecting Metrics/Linux Systems/Memory" 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/microchip.svg" width="150"/> Plugin: proc.plugin Module: /sys/block/zram <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> zRAM, or compressed RAM, is a block device that uses a portion of your system's RAM as a block device. The data written to this block device is compressed and stored in memory. The collectors provides information about the operation and the effectiveness of zRAM on your system. 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 | |:--|:-| | device | TBD | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | mem.zram_usage | compressed, metadata | MiB | | mem.zram_savings | savings, original | MiB | | mem.zram_ratio | ratio | ratio | | mem.zram_efficiency | percent | percentage | There are no alerts configured by default for this integration. No action required. There is no configuration file. There are no configuration options. There are no configuration examples.
Project: HertzBeat (Observability and Analysis / Observability)
File: ubuntu.md

id: ubuntu title: MonitoringUbuntu operating system monitoring sidebar_label: Ubuntu operating system keywords: [open source monitoring tool, open source linux ubuntu monitoring tool, monitoring ubuntu metrics] Collect and monitor the general performance Metrics of Ubuntu operating system. | Parameter name | Parameter help description | | -- | -- | | Monitoring Host | Monitored IPV4, IPV6 or domain name. NoteWithout protocol header (eg: https://, http://) | | Monitoring name | Identify the name of this monitoring. The name needs to be unique | | Port | Port provided by Linux SSH. The default is 22 | | Username | SSH connection user name, optional | | Password | SSH connection password, optional | | Collection interval | Interval time of monitor periodic data collection, unit: second, and the minimum interval that can be set is 30 seconds | | Whether to detect | Whether to detect and check the availability of monitoring before adding monitoring. Adding and modifying operations will continue only after the detection is successful | | Description remarks | For more information about identifying and describing this monitoring, users can note information here | | Metric name | Metric unit | Metric help description | | -- | -- | -- | | hostname | none | Host name | | version | none | Operating system version | | uptime | none | System running time | | Metric name | Metric unit | Metric help description | | -- | -- | -- | | info | none | CPU model | | cores | cores | Number of CPU cores | | interrupt | number | Number of CPU interrupts | | load | none | Average load of CPU in the last 1/5/15 minutes | | context_switch | number | Number of current context switches | | usage | % | CPU usage | | Metric name | Metric unit | Metric help description | | -- | -- | -- | | total | Mb | Total memory capacity | | used | Mb | User program memory | | free | Mb | Free memory capacity | | buff_cache | Mb | Memory occupied by cache | | available | Mb | Remaining available memory capacity | | usage | % | Memory usage | | Metric name | Metric unit | Metric help description | | -- | -- | -- | | disk_num | blocks | Total number of disks | | partition_num | partitions | Total number of partitions | | block_write | blocks | Total number of blocks written to disk | | block_read | blocks | Number of blocks read from disk | | write_rate | iops | Rate of writing disk blocks per second | | Metric name | Metric unit | Metric help description | | -- | -- | -- | | interface_name | none | Network card name | | receive_bytes | byte | Inbound data traffic(bytes) | | transmit_bytes | byte | Outbound data traffic(bytes) | | Metric name | Metric unit | Metric help description | | -- | -- | -- | | filesystem | none | File system name | | used | Mb | Used disk size | | available | Mb | Available disk size | | usage | % | usage | | mounted | none | Mount point directory |
Project: Grafana Tempo (Observability and Analysis / Observability)
File: metrics-from-traces.md

title: Metrics from traces description: Learn about how we can correlate traces and metrics. weight: 700 Tempo can generate metrics from ingested traces using the metrics-generator, an optional Tempo component. The metrics-generator runs two different processors: and . Metrics generated by Tempos metrics-generator can provide both RED (Rate/Error/Duration) metrics and interdependency graphs between services in a trace (the Service Graph functionality in Grafana). These capabilities rely on a set of generated span metrics and service metrics. RED metrics represent: Rate, the number of requests per second Errors, the number of those requests that are failing Duration, the amount of time those requests take For more information about RED method, refer to . The metrics-generator processes spans and writes metrics to a Prometheus data source using the Prometheus remote write protocol. Span metrics are of particular interest if your system is not monitored with metrics but it has distributed tracing implemented. You get out-of-the-box metrics from your tracing pipeline. {{< admonition type="note" >}} Metrics generation is disabled by default. Contact Grafana Support to enable metrics generation in your organization. {{% /admonition %}} After the metrics generator is enabled in your organization, refer to for information about metrics-generator options. <p align="center"><img src="../assets/traceservicegraph.png" alt="Trace service graph"></p> These metrics exist in your Hosted Metrics instance and can also be easily used to generate powerful custom dashboards. <p align="center"><img src="../assets/tracecustommetrics_dash.png" alt="Trace custom metrics dashboard"></p> The metrics generator automatically generates exemplars as well which allows easy metrics to trace linking. are available in Grafana Cloud so you can also push your own. <p align="center"><img src="../assets/trace_exemplars.png" alt="Trace exemplars"></p> Grafana can correlate different signals by adding the functionality to link between traces and metrics. The , a beta feature in Grafana 9.1, lets you quickly see trends or aggregated data related to each span. You can try it out by enabling the `traceToMetrics` feature toggle in your Grafana configuration file. . For example, you can use span attributes to metric labels by using the `$tags` keyword to convert span attributes to metrics labels. For more information, refer to the documentation.
Project: M3 (Observability and Analysis / Observability)
File: leader_follower.md

title: "Leader & Follower" weight: 2 A single `m3aggregator` node for is elected to be a leader. Both leader and follower nodes are receiving the writes and performing the aggregation. The main difference between the leader and the follower is that the leader node is responsible for flushing (persisting) the data it has aggregated (see for more details). The follower is standing by ready to take over flushing in case the current leader fails. Election state of the node can be checked by using `/status` endpoint: curl http://localhost:6001/status ```json { "status": { "flushStatus": { "electionState": "follower", "canLead": true } } } ``` `canLead` field is set to `true` on the follower node when that node is ready to take leader role without data loss. For that, the node must have accumulated all the data since the last flush done by the current leader (for the shardset that it owns). `canLead` is always `true` on leader nodes.
Project: Netdata (Observability and Analysis / Observability)
File: unbound_request_list_dropped.md

The `unboundrequestlist_dropped` alert indicates that the Unbound DNS resolver is dropping new incoming requests because its request queue is full. This situation may be caused by a high volume of DNS queries, possibly from a Denial of Service (DoS) attack or poor server optimization. Check the request queue length: Inspect the Unbound configuration file (usually located at `/etc/unbound/unbound.conf`) and check the `num-queries-per-thread` setting. If the value is too low for your system, you may encounter issues with dropped requests. Increase the queue length: If necessary, increase the `num-queries-per-thread` value in the Unbound configuration file. For example, if the current value is 1024, you can try setting it to a higher value, such as 2048 or 4096. Save the changes and restart the Unbound service: ``` sudo systemctl restart unbound ``` Monitor dropped requests: Use the `unbound-control` command to monitor the number of dropped requests in real-time: ``` sudo unbound-control stats_noreset | grep num.requestlist.dropped ``` If you see the dropped requests decreasing, your changes to the `num-queries-per-thread` value may have resolved the issue. Inspect server logs: Check the Unbound log file (usually located at `/var/log/unbound.log`) for any suspicious activity or error messages that may indicate the cause of the increased DNS queries. Check for potential DoS attacks: Use tools like `iftop`, `nload`, or `nethogs` to monitor network traffic and identify any potential DoS attacks or unusual traffic patterns. If you believe your server is experiencing a DoS attack: Investigate the source IP addresses of the high-volume traffic Block malicious traffic using firewall tools like `iptables` or `ufw` Contact your hosting provider, ISP, or network administrator for assistance Optimize Unbound: Review the and tune the settings in the Unbound configuration file to ensure optimal performance for your specific environment.
Project: Checkmk (Observability and Analysis / Observability)
File: 16084.md

key | value | date | 2024-02-15T08:39:14+00:00 version | 2.4.0b1 class | fix edition | cee component | agents level | 1 compatible | yes As an addition to Werk #15424, the Check_MK Agent service and the Agent update status page now also show the full 16-digit agent hash.
Project: Checkmk (Observability and Analysis / Observability)
File: 16315.md

key | value | date | 2024-02-05T13:05:04+00:00 version | 2.4.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes The page menu "Dashboards" in dashboards listed all other available dashboards in a random order. The defined sort index of each dashboard is now respected.
Project: Vector (Observability and Analysis / Observability)
File: aws_cloudwatch_logs.md

title: AWS Cloudwatch logs description: Publish log events to component_kind: sink layout: component tags: ["aws", "cloudwatch", "component", "sink", "logs"] {{/* This doc is generated using: The template in layouts/docs/component.html The relevant CUE data in cue/reference/components/... */}}
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_cluster.Cluster.md

title: "Interface: Cluster" linkTitle: "Cluster" slug: "libk8scluster.Cluster" .Cluster auth\_type: `string` Either 'oidc' or ''. '' means unknown. _ name: `string` _ `Optional` useToken: `boolean`
Project: VictoriaMetrics (Observability and Analysis / Observability)
File: setup-notifications.md

sort: 6 weight: 6 title: Notifications in Managed VictoriaMetrics menu: docs: parent: "managed" weight: 6 aliases: /managed-victoriametrics/setup-notifications.html The guide covers how to enable email and Slack notifications. Table of content: When you enter the notification section, you will be able to fill in the channels in which you want to receive notifications <img src="notifications_view.webp" > Setup Slack webhook How to do this is indicated on the following link <a href="https://api.slack.com/messaging/webhooks" target="_blank">https://api.slack.com/messaging/webhooks</a> <img src="notifications_view.webp" > Specify Slack channels Enter one or more channels into input and press enter or choose it after each input. <img src="notificationssetupslack.webp" > <img src="notificationssetupslackenterchannel.webp"> You can specify one or multiple emails for notifications in the input field. By default, email notifications are enabled for the account owner <img src="notificationssetupemails.webp" > <img src="notificationssetupemails_input.webp" > To test your notification settings, press Save and Test. If only Slack channels and webhook are specified correctly, you will receive the notification in the Slack channels. If only the emails are specified, you will receive notifications to those emails. When both notifications are specified, all notifications will be sent to Slack channels and emails. <img src="notificationssaveand_test.webp" > If the Save button is pressed, then entered channels will be only saved, and you get a success message. If the Save and Test button is pressed, then all entered information will be saved, and test notifications will be sent to the entered channels <img src="notificationssavesuccess.webp" > Examples of the test notification messages: <img src="notificationsslacktest.webp" > <img src="notificationsemailtest.webp" >
Project: Vector (Observability and Analysis / Observability)
File: 2020-02-20-new-sinks.md

date: "2020-04-13" title: "Lots of New Sinks!" description: "7 new sinks have been added to Vector" authors: ["binarylogic"] pr_numbers: [1555, 1562, 1668, 1716, 1759, 1783, 1794] release: "0.8.0" hideonrelease_notes: false badges: type: "new feature" domains: ["sinks"] We all love a good sink. Now you can enjoy our latest offerings:
Project: Checkmk (Observability and Analysis / Observability)
File: 16195.md

key | value | date | 2024-01-11T13:14:15+00:00 version | 2.3.0b1 class | fix edition | cce component | wato level | 1 compatible | yes In werk #16194 an issue was fixed where the UI was not reachable to apply a license when the CMC is not running. However, if the core was not running due to a license issue, a new core configuration would have to be generated in order to restart the core. This has been improved so that the core can now be started without further interaction.
Project: OpenCost (Observability and Analysis / Continuous Optimization)
File: opencost-bug-report.md

name: OpenCost Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the OpenCost bug is. Please ensure this is an issue related to the OpenCost cost model, API or specification. UI issues may be opened in the . 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. Which version of OpenCost are you using? You can find the version from the container's startup logging or from the bottom of the page in the UI. Additional context Add any other context about the problem here. Kubernetes versions and which public clouds you are working with are especially important.
Project: Headlamp (Observability and Analysis / Observability)
File: plugin_registry.RestartResourceEvent.md

title: "Interface: RestartResourceEvent" linkTitle: "RestartResourceEvent" slug: "plugin_registry.RestartResourceEvent" .RestartResourceEvent Event fired when restarting a resource. data: `Object` | Name | Type | Description | | : | : | : | | `resource` | `any` | The resource for which the deletion was called. | | `status` | `CONFIRMED` | What exactly this event represents. 'CONFIRMED' when the restart is selected by the user. For now only 'CONFIRMED' is sent. | _ type: `RESTART_RESOURCE`
Project: Grafana (Observability and Analysis / Observability)
File: release-notes-8-2-2.md

_build: list: false labels: products: cloud enterprise oss title: Release notes for Grafana 8.2.2 <!-- Auto generated by update changelog github action --> Annotations: We have improved tag search performance. , Application: You can now configure an error-template title. , AzureMonitor: We removed a restriction from the resource filter query. , Caching: Make cache size metric collection optional. (Enterprise) Packaging: We removed the ProcSubset option in systemd. This option prevented Grafana from starting in LXC environments. , Prometheus: We removed the autocomplete limit for metrics. , Request interceptor: Allow MSSQL's named instances. (Enterprise) Table: We improved the styling of the type icons to make them more distinct from column / field name. , ValueMappings: You can now use value mapping in stat, gauge, bar gauge, and pie chart visualizations. , Alerting: Fix panic when Slack's API sends unexpected response. , Alerting: The Create Alert button now appears on the dashboard panel when you are working with a default datasource. , Explore: We fixed the problem where the Explore log panel disappears when an Elasticsearch logs query returns no results. , Graph: You can now see annotation descriptions on hover. , Logs: The system now uses the JSON parser only if the line is parsed to an object. , Prometheus: We fixed the issue where the system did not reuse TCP connections when querying from Grafana Alerting. , Prometheus: We fixed the problem that resulted in an error when a user created a query with a$\\intervalmin step. , RowsToFields: We fixed the issue where the system was not properly interpreting number values. , Scale: We fixed how the system handles NaN percent when data min = data max. , Table panel: You can now create a filter that includes special characters. ,
Project: Tracetest (Observability and Analysis / Observability)
File: tracetest_completion_zsh.md

Generate the autocompletion script for zsh Generate the autocompletion script for the zsh shell. If shell completion is not already enabled in your environment you will need to enable it. You can execute the following once: ``` echo "autoload -U compinit; compinit" >> ~/.zshrc ``` To load completions in your current shell session: ``` source <(tracetest completion zsh) ``` To load completions for every new session, execute once: ``` tracetest completion zsh > "${fpath[1]}/_tracetest" ``` ``` tracetest completion zsh > $(brew --prefix)/share/zsh/site-functions/_tracetest ``` You will need to start a new shell for this setup to take effect. ``` tracetest completion zsh [flags] ``` ``` -h, --help help for zsh --no-descriptions disable completion descriptions ``` ``` -c, --config string config file will be used by the CLI (default "config.yml") -o, --output string output format [pretty|json|yaml] -s, --server-url string server url -v, --verbose display debug information ``` - Generate the autocompletion script for the specified shell
Project: Checkmk (Observability and Analysis / Observability)
File: 16166.md

key | value | compatible | yes version | 2.3.0b1 date | 2024-01-03T09:05:20+00:00 level | 1 class | fix component | checks edition | cre lsnodestats command was used for monitoring nodes in IBM Storwize devices. Storwize devices don't have the lsnodestats command which led to missing data in ibmsvcnodestats services. Now, the IBM SVC agent uses the lsnodestats if it's available and lsnodecanisterstats otherwise.
Project: Graylog (Observability and Analysis / Observability)
File: Timestamp.md

For the following examples we are using the date time `2010-07-30T16:03:25.000Z`. By default, the output will be based on the user time zone defined for the style guide. The component displays the date time in the default format for date times in the graylog UI, when no format is specified. ```tsx <Timestamp dateTime="2010-07-30T16:03:25.000Z" /> ``` In this example we are displaying the provided time as UTC. ```tsx <Timestamp dateTime="2010-07-30T16:03:25.000Z" tz="UTC" /> ``` ```tsx import { DATETIMEFORMATS } from 'util/DateTime'; <table cellPadding="10"> <thead> <tr> <th style={{ width: '150px' }}>Format</th> <th>Output</th> </tr> </thead> <tbody> {Object.keys(DATETIMEFORMATS).map((format) => ( <tr key={format}> <td>{format}</td> <td><Timestamp dateTime="2010-07-30T16:03:25.000Z" format={format}/></td> </tr> ))} </tbody> </table> ``` ```tsx <Timestamp dateTime={new Date()} /> ```
Project: Netdata (Observability and Analysis / Observability)
File: mdstat_nonredundant_last_collected.md

This alert, `mdstatnonredundantlast_collected`, is triggered when the Netdata Agent fails to collect data from the Multiple Device (md) driver for a certain period. The md driver is used to manage software RAID arrays in Linux. The md (multiple device) driver is responsible for managing software RAID arrays on Linux systems. It provides a way to combine multiple physical disks into a single logical disk, increasing capacity and providing redundancy, depending on the RAID level. Monitoring the status of these devices is crucial to ensure data integrity and redundancy. Check the status of the md driver: To inspect the status of the RAID arrays managed by the md driver, use the `cat` command: ``` cat /proc/mdstat ``` This will display the status and configuration of all active RAID arrays. Look for any abnormal status, such as failed or degraded disks, and replace or fix them as needed. Verify the Netdata configuration: Ensure that the Netdata Agent is properly configured to collect data from the md driver. Open the `netdata.conf` configuration file found in `/etc/netdata/` or `/opt/netdata/etc/netdata/`, and look for the `[plugin:proc:/proc/mdstat]` section. Make sure that the `enabled` option is set to `yes`: ``` [plugin:proc:/proc/mdstat] ``` If you make any changes to the configuration, restart the Netdata Agent for the changes to take effect: ``` sudo systemctl restart netdata ``` Check the md driver data collection: After verifying the Netdata configuration, check if data collection is successful. On the Netdata dashboard, go to the "Disks" section, and look for "mdX" (where "X" is a number) in the list of available disks. If you can see the charts for your RAID array(s), it means data collection is working correctly. Investigate system logs: If the issue persists, check the system logs for any errors or messages related to the md driver or Netdata Agent. You can use `journalctl` for this purpose: ``` journalctl -u netdata ``` Look for any error messages or warnings that could indicate the cause of the problem.
Project: Logging Operator (Kube Logging) (Observability and Analysis / Observability)
File: useragent.md

title: User Agent weight: 200 generated_file: true Fluentd Filter plugin to parse user-agent More information at https://github.com/bungoume/fluent-plugin-ua-parser Delete input key Default: false Join hashed data by '_' Default: false Target key name Default: user_agent Output prefix key name Default: ua {{< highlight yaml >}} apiVersion: logging.banzaicloud.io/v1beta1 kind: Flow metadata: name: demo-flow spec: filters: useragent: keyname: myagent delete_key: true outkey: uafields flatten: true selectors: {} localOutputRefs: demo-output {{</ highlight >}} Fluentd config result: {{< highlight xml >}} <filter > @type ua_parser @id test_useragent keyname myagent delete_key true outkey uafields flatten true </filter> {{</ highlight >}}