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

Fluentd: Open-Source Log Collector =================================== ](https://github.com/fluent/fluentd/actions/workflows/linux-test.yaml) ](https://github.com/fluent/fluentd/actions/workflows/windows-test.yaml) ](https://github.com/fluent/fluentd/actions/workflows/macos-test.yaml) ](https://codeclimate.com/github/fluent/fluentd) ](https://bestpractices.coreinfrastructure.org/projects/1189) collects events from various data sources and writes them to files, RDBMS, NoSQL, IaaS, SaaS, Hadoop and so on. Fluentd helps you unify your logging infrastructure (Learn more about the ). <p align="center"> <img src="https://www.fluentd.org/images/fluentd-architecture.png" width="500px"/> </p> $ gem install fluentd $ fluentd -s conf $ fluentd -c conf/fluent.conf & $ echo '{"json":"message"}' | fluent-cat debug.test master: For v1 development. v0.12: For v0.12. This is deprecated version. we already stopped supporting (See https://www.fluentd.org/blog/drop-schedule-announcement-in-2019). Ruby 2.7 or later git `git` should be in `PATH`. On Windows, you can use `Github for Windows` and `GitShell` for easy setup. Use bundler: $ gem install bundler $ bundle install --path vendor/bundle $ bundle exec rake test You can run specified test via `TEST` environment variable: $ bundle exec rake test TEST=test/testspecifiedpath.rb $ bundle exec rake test TEST=test/test_*.rb Website: https://www.fluentd.org/ Documentation: https://docs.fluentd.org/ Project repository: https://github.com/fluent Discussion: https://github.com/fluent/fluentd/discussions Slack / Community: https://slack.fluentd.org Newsletters: https://www.fluentd.org/newsletter Author: Copyright: 2011-2021 Fluentd Authors License: Apache License, Version 2.0 A third party security audit was performed by Cure53, you can see the full report . See to contact us about vulnerability. Patches contributed by .
Project: Beats (Observability and Analysis / Observability)
File: ISSUE_TEMPLATE.md

name: Bug about: "Report confirmed bugs. For unconfirmed bugs please visit https://discuss.elastic.co/c/beats" Please post all questions and issues on https://discuss.elastic.co/c/beats before opening a Github Issue. Your questions will reach a wider audience there, and if we confirm that there is a bug, then you can open a new issue. For security vulnerabilities please only send reports to security@elastic.co. See https://www.elastic.co/community/security for more information. Please include configurations and logs if available. For confirmed bugs, please report: Version: Operating System: Discuss Forum URL: Steps to Reproduce:
Project: Sidekick (Observability and Analysis / Observability)
File: CONTRIBUTING.md

<p align="center"> Welcome to Sidekick contribution guidelines </p> <p align="center"> <a href="https://www.runsidekick.com/discord-invitation" target="_blank"><img width="40%" height="40%" src="https://4750167.fs1.hubspotusercontent-na1.net/hubfs/4750167/Sidekick%20OS%20repo/joindiscord.png"></a> </p> The best way to contribute to Sidekick is . If you found any bug on Sidekick or mistake in our documents, contents you can open an issue about it to let us know. Evaluating problems and fixing them is high priority for us. If you plan to work on a problem, please check that same problem or topic does not already exist. If you plan to work on a new feature, our advice it discuss it with other community members/maintainers who might give you a idea or support. If you stuck anywhere, ask for help in our discord community. Please relate one bug with one issue, do not use issues as bug lists. After issue creation, If you are looking to make your contribution follow the steps below. Fork this repository. Clone the repository you forked. Create a branch with spesified name. Its better to related with your issue title. Make necessary changes and commit those changes. Make sure to test your changes. Push changes to your branch. Submit your changes for review. You can create an issue and contribute about anything you want but following above steps will definitely ease your work and other maintainers too.
Project: Netdata (Observability and Analysis / Observability)
File: windows_outbound_packets_discarded.md

This alert is triggered when the number of outbound discarded packets for a network interface on a Windows system reaches or exceeds 5 in the last 10 minutes. Discarded packets indicate network problems or misconfigurations and can lead to decreased performance, slow connections and communication errors. Outbound discarded packets are network packets that were not sent successfully from a Windows host to the intended destination. This might be due to various reasons such as buffer overflows, device driver errors, or network congestion. Discarded packets may result in retransmissions, which could cause increased latencies and reduced network throughput. Check network performance statistics Use the built-in `netstat` command to display network statistics: ``` netstat -s ``` Look for errors or high discard rates, which may indicate network problems. Monitor network interface performance Use the `Performance Monitor` tool in Windows to monitor the network interface for issues. Look for counters related to discarded packets, such as `Packets Outbound Errors`, `Packets Received Errors`, and `Packets Sent/sec`. Identify if there are specific applications with high discard rates Use the `Resource Monitor` tool in Windows to check which applications are consuming the most network resources and identify if any specific application is causing high discard rates. Check for errors, warnings, or unusual events in the Windows Event Viewer Open the `Event Viewer` in Windows and browse through the System and Application logs for any network-related events. Look for errors or warnings that could be related to network configurations, device driver problems, or application-specific issues. Update or reinstall network drivers Outdated or corrupt network drivers can cause discarded packets. Ensure your network drivers are up to date and, if necessary, reinstall the drivers. Check network components and configurations Inspect network cables, switches, and routers for any physical damage or malfunction. Check the network settings on the Windows host to ensure they are correctly configured, including DNS, gateway, and subnet mask. Network congestion If your network is congested, it can cause an increase in discarded packets. Consider upgrading network equipment or implementing quality of service (QoS) policies to prioritize and manage network traffic more effectively.
Project: Grafana Loki (Observability and Analysis / Observability)
File: match.md

title: match menuTitle: description: The 'match' Promtail pipeline stage. aliases: ../../../clients/promtail/stages/match/ weight: The match stage is a filtering stage that conditionally applies a set of stages or drop entries when a log entry matches a configurable LogQL and . {{% admonition type="note" %}} The filters do not include label filter expressions such as `| label == "foobar"`. {{% /admonition %}} ```yaml match: selector: <string> [pipeline_name: <string>] [action: <string> | default = "keep"] [dropcounterreason: <string> | default = "match_stage"] stages: [<stages>...] ``` Refer to the for the schema on the various stages supported here. For the given pipeline: ```yaml pipeline_stages: json: expressions: app: labels: app: match: selector: '{app="loki"}' stages: json: expressions: msg: message match: pipeline_name: "app2" selector: '{app="pokey"}' action: keep stages: json: expressions: msg: msg match: selector: '{app="promtail"} |~ ".noisy error."' action: drop dropcounterreason: promtailnoisyerror output: source: msg ``` And given log lines: ```json { "time":"2012-11-01T22:08:41+00:00", "app":"loki", "component": ["parser","type"], "level" : "WARN", "message" : "app1 log line" } { "time":"2012-11-01T22:08:41+00:00", "app":"promtail", "component": ["parser","type"], "level" : "ERROR", "message" : "foo noisy error" } ``` The first stage will add `app` with a value of `loki` into the extracted map for the first log line, while the second stage will add `app` as a label (again with the value of `loki`). The second line will follow the same flow and will be added the label `app` with a value of `promtail`. The third stage uses LogQL to only execute the nested stages when there is a label of `app` whose value is `loki`. This matches the first line in our case; the nested `json` stage then adds `msg` into the extracted map with a value of `app1 log line`. The fourth stage uses LogQL to only executed the nested stages when there is a label of `app` whose value is `pokey`. This does not match in our case, so the nested `json` stage is not ran. The fifth stage will drop any entries from the application `promtail` that matches the regex `.*noisy error`. and will also increment the `logentrydroppedlines_total` metric with a label `reason="promtailnoisyerror"` The final `output` stage changes the contents of the log line to be the value of `msg` from the extracted map. In this case, the log line is changed to `app1 log line`.
Project: Grafana (Observability and Analysis / Observability)
File: release-notes-9-0-2.md

aliases: [] hide_menu: true labels: products: cloud enterprise oss title: Release notes for Grafana 9.0.2 <!-- Auto generated by update changelog github action --> Alerting: Add support for images in Pushover alerts. , Alerting: Don't stop the migration when alert rule tags are invalid. , Alerting: Don't stop the migration when alert rule tags are invalid (. , Alerting: Skip the default data source if incompatible. , AzureMonitor: Parse non-fatal errors for Logs. , OAuth: Restore debug log behavior. , Plugins: Improved handling of symlinks. , Alerting: Code-gen parsing of URL parameters and fix related bugs. , Alerting: Code-gen parsing of URL parameters and fix related bugs. , Annotations: Fix annotation autocomplete causing panels to crash. , Barchart: Fix warning not showing. , CloudWatch: Enable custom session duration in AWS plugin auth. , Dashboards: Fixes issue with the initial panel layout counting as an unsaved change. , Plugins: Use a Grafana specific SDK logger implementation for core plugins. , Search: Fix pagination in the new search page. ,
Project: Netdata (Observability and Analysis / Observability)
File: 10min_disk_utilization.md

This alert presents the average percentage of time the disk was busy over the last 10 minutes. If you receive this it indicates high disk load and that the disk spent most of the time servicing read or write requests. This alert is triggered in a warning state when the metric exceeds 98%. This metric is the same as the %util column on the command `iostat -x`. Check per-process disk usage to find the top consumers (If you got this alert for a device serving requests in parallel, you can ignore it) On Linux use `iotop` to see which processes are the main Disk I/O consumers on the `IO` column. ``` sudo iotop ``` Using this, you can see which processes are the main Disk I/O consumers on the `IO` column. On FreeBSD use `top` ``` top -m io -o total ``` `iotop` is a useful tool, similar to `top`, used to monitor Disk I/O usage, if you don't have it, then
Project: Elastic (Observability and Analysis / Observability)
File: mv_sum.md

<!-- This is generated by ESQL's AbstractFunctionTestCase. Do no edit it. See ../README.md for how to regenerate it. --> Converts a multivalued field into a single valued field containing the sum of all of the values. ``` ROW a=[3, 5, 6] | EVAL suma = MVSUM(a) ```
Project: Vector (Observability and Analysis / Observability)
File: 2021-08-23-removing-wasm.md

date: "2021-08-23" title: "`wasm` transform to be removed from Vector" description: "Removing experimental WASM support from Vector" authors: ["jszwedko"] pr_numbers: [] release: "0.16.0" hideonrelease_notes: false badges: type: "deprecation" domains: ["extensions"] In `v0.10.0` we released experimental WASM support via the `wasm` transform to allow transforms to be written in Rust. While this idea shows promise for extensions in Vector, we have not been able to invest the time into it to make it a first-class feature of Vector and so are removing it until such time. We may revisit adding this back in the future, This component is deprecated as of `v0.16.0` and will be removed in `v0.17.0`. The primary purpose of this is removal to reduce maintenance burden and avoid pushing users to use a transform for extensions that has a poor user experience and poor performance. In its place, the `lua` transform can be used to accomplish most custom tasks the `wasm` transform would have been used for. Are you currently using the `wasm` transform? We would like to hear about your use-cases to ensure we accommodate them through other Vector features. Please leave a comment on this [GitHub issue](https://github.com/vectordotdev/vector/issues/8036).
Project: Vector (Observability and Analysis / Observability)
File: 2021-01-20-wildcard-identifiers.md

date: "2021-01-20" title: "Wildcards are now supported in component names" description: "Wildcards allow for dynamic Vector topologies" authors: ["binarylogic"] featured: false pr_numbers: [6170] release: "0.12.0" hideonrelease_notes: false badges: type: "enhancement" domains: ["topology"] introduced wildcards when referencing component names in the `inputs` option. This allows you to build dynamic topologies. This feature comes with one limitation: the wildcard must be at the end of the string. ```toml [sources.app1_logs] type = "file" includes = ["/var/log/app1.log"] [sources.app2_logs] type = "file" includes = ["/var/log/app.log"] [sources.system_logs] type = "file" includes = ["/var/log/system.log"] [sinks.app_logs] type = "datadog_logs" inputs = ["app*"] [sinks.archive] type = "aws_s3" inputs = ["app*", "system_logs"] ```
Project: Netdata (Observability and Analysis / Observability)
File: ping_host_reachable.md

This `pinghostreachable` alert checks the network reachability status of a specific host. When you receive this alert, it means that the host is either `up` (reachable) or `down` (unreachable). Network reachability refers to the ability of a particular host to communicate with other devices or systems within a network. In this alert, the reachability is monitored using the `ping` command, which sends packets to the host and checks for the response. The alert evaluates the packet loss percentage over a 30-second period. Verify if the alert is accurate: Check if there are transient network issues or if there is a problem with the particular host. You can run the `ping` command manually to see if the packet loss percentage is consistent over time. ``` ping -c 10 <host IP or domain> ``` Check the network connectivity: Ensure there are no issues with the local network or the physical connections (switches, routers, etc.). Look for potential network bottlenecks, high traffic, and hardware failures that can affect reachability. Check the host's health: If the host is reachable, log in to the system and examine its performance, stability, and resource usage. Look for indicators of high system load, resource constraints, or unresponsive processes. Examine network security policies and firewalls: Network reachability can be affected by misconfigured firewalls or security policies. Ensure there are no restrictions blocking the communication between the monitoring system and the host. Analyze logs for any relevant information: Check system logs (e.g., `/var/log/syslog`) and application logs on both the monitoring system and the target host. Look for error messages, timeouts, or connectivity problems.
Project: Grafana (Observability and Analysis / Observability)
File: release-notes-7-3-4.md

_build: list: false labels: products: cloud enterprise oss title: Release notes for Grafana 7.3.4 <!-- Auto generated by update changelog github action --> Dashboard: Fixes kiosk state after being redirected to login page and back. , InfluxDB: Update flux library to fix support for boolean label values. , Security: Fixes minor security issue with alert notification webhooks that allowed GET & DELETE requests. , Table: Fixes issues with phantom extra 0 for zero values. ,
Project: GO Feature Flag (Observability and Analysis / Feature Flagging)
File: provider-cache.md

title: Provider Cache Specification | | | |-|--| | Creation Date | 06/04/2023 | | Last Update Date | 04/08/2023 | | Authors | Thomas Poignant | OpenFeature Providers are used to call the GO Feature Flag the relay proxy to evaluate flags. The purpose of this specification document is to outline the requirements for implementing the cache policy in the providers that is compatible with GO Feature Flag. The provider should implement an LRU cache with a configurable size and TTL. The cache size and TTL should be configurable by the user of the provider. The cache should be activated by default, but it should be possible to deactivate it in the configuration. The cache key should be a combination of the flag name and user key. When a flag is evaluated, the provider should first check the cache for the result before querying the relay proxy. When there is no entry in the cache, we should query the relay proxy and update the cache with this entry. When we have reached the max time for a cache entry, it should not be possible to retrieve it. When we have reached the max size of the cache we should remove the oldest entry. We should collect the cache evaluations and call the API `/v1/data/collector` for statistics reason. If we perform a remote evaluation (meaning that the flag is evaluated by the server), we should not collect the usage because the evaluation data is already tracked on the server side. The data collection should be activated by default, but it should be possible to deactivate it in the configuration. We should not call the relay proxy API `/v1/data/collector` for every evaluation, but call it in bulk with a periodic threshold. The threshold should be configurable by the user of the provider.
Project: Pinpoint (Observability and Analysis / Observability)
File: README.md

<img src="./assets/img/server-map-logo.png" /> <br /> alpha version ServerMap component is an open-source network-map library, specifically for application topology. With ServerMap component, you will find it easy to understand how your services are interconnected and how the transactions are going on between them. Besides, since we provide a various of cool features such as merge and customizing label, feel free to check out them if you are interested in making your topology look nicer. For your information, ServerMap component builds the network-map using which is light, highly optimized and well-maintained so it's all ready to provide a pleasant experience. ```sh npm install @pinpoint-fe/server-map ``` or ```sh yarn add @pinpoint-fe/server-map ``` ```typescript import React from 'react'; import { ServerMap } from '@pinpoint-fe/server-map'; export default function MyServerMapPage() { return ( <ServerMap data={data} baseNodeId={'MY-APP'} /> ); } ``` | Props | Type | Required | Description | | | | | | | data | <code>{ nodes: Node[], edges: Edge[] }</code> | | Data to render | | baseNodeId | string | | Central node id in the server-map | | customTheme | ThemeType | | Custom style object | | onClickNode | `ClickEventHandler<MergedNode>` | | Callback to execute when clicking nodes | | onClickEdge | `ClickEventHandler<MergedEdge>` | | Callback to execute when clicking edges | | onClickBackground | `ClickEventHandler<{}>` | | Callback to execute when clicking background | | renderNodeLabel | `(node: MergedNode) => string undefined` | | Custom node label | | renderEdgeLabel | `(node: MergedEdge) => string undefined` | | Custom edge label |
Project: HertzBeat (Observability and Analysis / Observability)
File: mailing_lists.md

id: 'mailing_lists' title: 'Mailing Lists' sidebar_position: 1 <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> The is the community-recommended way to communicate and obtain the latest information. Before you post anything to the mailing lists, be sure that you already subscribe to them. Use this list for your HertzBeat questions Used by HertzBeat contributors to discuss development of HertzBeat | List Name | Address | Subscribe | Unsubscribe | Archive | ||||-|-| | Developer List | dev@hertzbeat.apache.org | | | | Notifications on changes to the HertzBeat codebase | List Name | Address | Subscribe | Unsubscribe | Archive | |-|||-|-| | Notification List | notifications@hertzbeat.apache.org | | | | Sending a subscription email is also very simple. The steps are as follows: 1Subscribe: Click the subscribe button in the above table, and it redirects to your mail client. The subject and content are arbitrary. After that, you will receive a confirmation email from dev-help@hertzbeat.apache.org (if not received, please confirm whether the email is automatically classified as SPAM, promotion email, subscription email, etc.). 2Confirm: Reply directly to the confirmation email, or click on the link in the email to reply quickly. The subject and content are arbitrary. 3Welcome: After completing the above steps, you will receive a welcome email with the subject WELCOME to dev@hertzbeat.apache.org, and you have successfully subscribed to the Apache HertzBeat mailing list. When posting to the mailing lists, please use plain text emails. Do not use HTML emails. HTML emails are more likely to be targeted as spam mails and rejected. It may get malformed through different mail clients and not easily readable by others.
Project: Grafana Loki (Observability and Analysis / Observability)
File: MAINTAINERS.md

This page lists all active maintainers of this repository. If you were a maintainer and would like to add your name to the Emeritus list, please send us a PR. See for governance guidelines and how to become a maintainer. See for general contribution guidelines. , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC , Google LLC