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

Meter system is another streaming calculation mode designed for metrics data. In the , there are clear , including definitions for native objects. Meter system is focused on the data type itself, and provides a more flexible approach to the end user in defining the scope entity. The meter system is open to different receivers and fetchers in the backend, see the for more details. Every metric is declared in the meter system to include the following attributes: Metrics Name. A globally unique name to avoid overlapping between the OAL variable names. Function Name. The function used for this metric, namely distributed aggregation, value calculation or down sampling calculation based on the function implementation. Further, the data structure is determined by the function as well, such as function Avg is for Long. Scope Type. Unlike within the OAL, there are plenty of logic scope definitions. In the meter system, only type is required. Type values include service, instance, and endpoint, just as we have described in the Overview section. The values of scope entity name, such as service name, are required when metrics data are generated with the metrics data values. NOTE: The metrics must be declared in the bootstrap stage, and there must be no change to runtime. The Meter System supports the following binding functions: avg. Calculates the avg value for every entity under the same metrics name. histogram. Aggregates the counts in the configurable buckets. Buckets are configurable but must be assigned in the declaration stage. percentile. See . Unlike the OAL, we provide 50/75/90/95/99 by default. In the meter system function, the percentile function accepts several ranks, which should be in the (0, 100) range.
Project: Cortex (Observability and Analysis / Observability)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.
Project: Vector (Observability and Analysis / Observability)
File: mezmo.md

title: Mezmo (formerly LogDNA) description: Deliver log event data to component_kind: sink layout: component tags: ["logdna", "mezmo", "component", "sink", "logs"] aliases: ["/docs/reference/configuration/sinks/logdna"] {{/* This doc is generated using: The template in layouts/docs/component.html The relevant CUE data in cue/reference/components/... */}}
Project: Centreon (Observability and Analysis / Observability)
File: proxy.md

This module aims to give the possibility to Gorgone to become distributed. It is not needed in a Centreon standalone configuration, but must be enabled if there is Poller or Remote servers. The module includes mechanisms like ping to make sure nodes are alive, synchronisation to store logs in the Central Gorgone database, etc. A SSH client library make routing to non-gorgoned nodes possible. | Directive | Description | Default value | | :- | : | : | | pool | Number of childs to instantiate to process events | `5` | | synchistory_time | Time in seconds between two logs synchronisation | `60` | | synchistory_timeout | Time in seconds before logs synchronisation is considered timed out | `30` | | ping | Time in seconds between two node pings | `60` | | pongdiscardtimeout | Time in seconds before a node is considered dead | `300` | ```yaml name: proxy package: "gorgone::modules::core::proxy::hooks" enable: false pool: 5 synchistory_time: 60 synchistory_timeout: 30 ping: 60 pongdiscardtimeout: 300 ``` | Event | Description | | :-- | :-- | | PROXYREADY | Internal event to notify the core | | REMOTECOPY | Copy files or directories from the server running the daemon to another server | | SETLOGS | Internal event to insert logs into the database | | PONG | Internal event to handle node ping response | | REGISTERNODES | Internal event to register nodes | | UNREGISTERNODES | Internal event to unregister nodes | | PROXYADDNODE | Internal event to add nodes for proxying | | PROXYDELNODE | Internal event to delete nodes from proxying | | PROXYADDSUBNODE | Internal event to add nodes of nodes for proxying | | PONGRESET | Internal event to deal with no pong nodes | | Endpoint | Method | | :- | :-- | | /api/core/proxy/remotecopy | `POST` | | Header | Value | | :-- | : | | Accept | application/json | | Content-Type | application/json | | Key | Value | | :- | : | | source | Path of the source file or directory | | destination | Path of the destination file or directory | | cache_dir | Path to the cache directory for archiving purpose | ```json { "source": "<file or directory path>", "destination": "<file or directory path>", "cache_dir": "<cache directory path>" } ``` ```bash curl --request GET "https://hostname:8443/api/core/proxy/remotecopy" \ --header "Accept: application/json" \ --header "Content-Type: application/json" \ --data " { \"source\": \"/var/cache/centreon/config/engine/2/\", \"destination\": \"/etc/centreon-engine\", \"cache_dir\": \"/var/cache/centreon\" }" ```
Project: OpenTelemetry (Observability and Analysis / Observability)
File: using-actuated.md

is available as a GitHub App which can be enabled on repositories, and allows GH Actions to execute on runners hosted by the CNCF. . Using actuated is ideal if you need to run an Action on an an ARM64 environment, which GitHub doesn't currently provide. It should not replace the GitHub Actions runners in every job. Before it can be used, the App has to be enabled on the repository, through a maintenance request. [See an example](https://github.com/open-telemetry/community/issues/1954). Using actuated on a GitHub Actions job consists in changing the `runs-on` section to be `actuated-arm64-*`, with the required CPUs and RAM in the name. See the [actuated documentation](https://docs.actuated.dev/examples/custom-vm-size/) about custom VM sizes. For example: ```yaml runs-on: actuated-arm64-4cpu-16gb ``` This configuration will ensure your job has 4 CPUs and 16GB of RAM available. While not specifying any CPU/RAM values (`runs-on: actuated-arm64`) currently works, using that format is deprecated and will be removed. As you set up your job, you may need an estimation of the resources it needs, to better set your requirements. Actuated provides VMMeter, a small action which will output system information at the end of a run. Follow [the instructions](https://gist.github.com/alexellis/1f33e581c75e11e161fe613c46180771) to set it up in your job. see [the actuated documentation](https://actuated.dev/blog/right-sizing-vms-github-actions).
Project: Grafana (Observability and Analysis / Observability)
File: connect-null-values.md

title: Connect null values Choose how null values, which are gaps in the data, appear on the graph. Null values can be connected to form a continuous line or set to a threshold above which gaps in the data are no longer connected. Never: Time series data points with gaps in the data are never connected. Always: Time series data points with gaps in the data are always connected. Threshold: Specify a threshold above which gaps in the data are no longer connected. This can be useful when the connected gaps in the data are of a known size and/or within a known range, and gaps outside this range should no longer be connected.
Project: Trickster (Observability and Analysis / Observability)
File: simulated-latency.md

Trickster supports simulating latency on a per-backend basis, and can simulate both consistent and random durations of latency. Simulated latency is introduced in the frontend part of the proxy, and thus works with any backend provider. In `rule`, `alb` and other backend providers, where a request may transit multiple backend routes, only the Simulated Latency configs associated with the request entrypoint (first route) will be processed, and not any subsequent routes the request is sent through. In the Backend configuration, add a `latencyminms` value > 0, and the configured amount of latency will be introduced for each incoming request. To simulate random latency, set `latencymaxms` to a value > `latencyminms`, which may be 0 for random latency. Trickster will introduce a random amount of latency between (inclusive) the provided min and max values. When simulated latency is applied to a request, an `x-simulated-latency` header will be included in the corresponding response indicating the duration of the latency applied in milliseconds. The format of the latency header is as follows: ```bash GET /api/v1/query?query=up HTTP/1.1 Accept: / ... HTTP/1.1 200 OK X-Simulated-Latency: 300ms X-Trickster-Result: engine=DeltaProxyCache; status=hit; ffstatus=hit Date: Mon, 06 Sep 2021 04:07:20 GMT ... ``` ```yaml frontend: listen_port: 8480 backends: default: origin_url: https://www.example.com provider: reverseproxy latencyminms: 50 latencymaxms: 150 backend2: origin_url: https://www.trickstercache.org provider: reverseproxy latencyminms: 300 ```
Project: Netdata (Observability and Analysis / Observability)
File: 1m_tcp_syn_queue_drops.md

This alert indicates that the average number of SYN requests dropped due to the TCP SYN queue being full has exceeded a specific threshold in the last minute. A high number of dropped SYN requests may indicate a SYN flood attack, causing the system to become unresponsive to legitimate traffic. Monitor incoming traffic: Analyze the incoming network traffic to determine if there is a sudden surge in SYN requests, which might indicate a SYN flood attack. Use tools like `tcpdump`, `iftop`, or `nload` to monitor network traffic. Check system resources: Inspect the system's CPU and memory usage to ensure there are enough resources available to handle incoming connections. High resource usage might lead to dropped SYN requests. Enable SYN cookies: If the traffic is legitimate, consider enabling SYN cookies to help mitigate the impact of a SYN flood attack, as described in the provided guide above. Adjust SYN queue settings: Increase the SYN queue size by adjusting the `net.core.somaxconn` and `net.ipv4.tcpmaxsyn_backlog` sysctl parameters. Make sure to set these values according to your system's capacity and traffic requirements. Implement traffic filtering: Use traffic filtering techniques such as rate limiting, IP blocking, or firewall rules to mitigate the impact of SYN flood attacks.
Project: OpenFeature (Observability and Analysis / Feature Flagging)
File: appendix-a-included-utilities.md

id: appendix-a title: "Appendix A: Included Utilities" description: Information on OpenFeature ecosystem utilities sidebar_position: 4 This document contains requirements for auxiliary utilities provided by the SDK, such as testing utilities. Language-specific OpenFeature SDK implementations SHOULD expose an in-memory provider built into the SDK. The in-memory provider is intended to be used for testing; SDK consumers may use it for their use cases. Hence, the packaging, naming, and access modifiers must be set appropriately. Given below are features this provider MUST support, Provider must be initiated with a pre-defined set of flags provided to a constructor Feature Flag structure must be minimal but should help to test OpenFeature specification EvaluationContext support should be provided through callbacks/lambda expressions Provider must support a means of updating flag values, resulting in the emission of `PROVIDERCONFIGURATIONCHANGED` events Provider must be maintained to support specification changes E2E tests must utilize defined within the SDK and must be self-contained. OpenFeature project maintains an end-to-end(e2e) test suite defined with . These test definitions reside in ```mermaid flowchart LR subgraph SDK A[e2e Tests] -.-> B[In-memory provider] end ```
Project: SkyWalking (Observability and Analysis / Observability)
File: ttl.md

In SkyWalking, there are two types of observability data: Records include traces, logs, topN sampled statements and alarm. `recordDataTTL` applies to record data. Metrics include all metrics for service, instance, endpoint, and topology map. Metadata(lists of services, instances, or endpoints) also belongs to metrics. `metricsDataTTL` applies to Metrics data. These are the settings for the different types: ```yaml recordDataTTL: ${SWCORERECORDDATATTL:3} # Unit is day metricsDataTTL: ${SWCOREMETRICSDATATTL:7} # Unit is day ```
Project: Chaos Mesh (Observability and Analysis / Chaos Engineering)
File: feature-request.md

name: "\U0001F680 Feature Request" about: I have a suggestion Is your feature request related to a problem? Please describe: <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] --> Describe the feature you'd like: <!-- A clear and concise description of what you want to happen. --> Describe alternatives you've considered: <!-- A clear and concise description of any alternative solutions or features you've considered. --> Teachability, Documentation, Adoption, Migration Strategy: <!-- If you can, explain some scenarios how users might use this, situations it would be helpful in. Any API designs, mockups, or diagrams are also helpful. -->
Project: Kiali (Observability and Analysis / Observability)
File: CODE_OF_CONDUCT.md

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality. Examples of unacceptable behavior by participants include: The use of sexualized language or imagery Personal attacks Trolling or insulting/derogatory comments Public or private harassment Publishing other's private information, such as physical or electronic addresses, without explicit permission Other unethical or unprofessional conduct. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team. This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a Kiali project maintainer, Jay Shaughnessy <jshaughn@redhat.com>, John Mazzitelli <jmazzite@redhat.com> and/or Lucas Ponce <lponce@redhat.com>. This Code of Conduct is adapted from the which is adapted from the Contributor Covenant (http://contributor-covenant.org), version 1.2.0, available at http://contributor-covenant.org/version/1/2/0/
Project: Logstash (Observability and Analysis / Observability)
File: doc-request.md

name: Documentation about: Report a documentation issue labels: "docs,status:needs-triage" <!-- Please search . The issue may already exist. --> <!-- What's the problem? Is information missing? Inaccurate? Just not clear? Please include a link to the page (if applicable). --> Description: URL: Example: https://www.elastic.co/guide/en/logstash/current/introduction.html Anything else?
Project: Checkmk (Observability and Analysis / Observability)
File: 16242.md

key | value | date | 2024-03-06T12:43:13+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes The agent plugin `mk_oracle` creates forked processes, e.g. from `sqlplus`. In order to reliable clean up stale processes, we kill now the whole process chain under AIX which corresponds to the stored `PID`. We introduce this only for `AIX` now as we have customers which are affected under that OS.
Project: Netdata (Observability and Analysis / Observability)
File: nfs_client.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/integrations/nfs_client.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/metadata.yaml" sidebar_label: "NFS Client" learn_status: "Published" learnrelpath: "Collecting Metrics/Linux Systems/Filesystem/NFS" 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/nfs.png" width="150"/> Plugin: proc.plugin Module: /proc/net/rpc/nfs <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> This integration provides statistics from the Linux kernel's NFS Client. 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. This scope has no labels. Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | nfs.net | udp, tcp | operations/s | | nfs.rpc | calls, retransmits, auth_refresh | calls/s | | nfs.proc2 | a dimension per proc2 call | calls/s | | nfs.proc3 | a dimension per proc3 call | calls/s | | nfs.proc4 | a dimension per proc4 call | calls/s | 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: M3 (Observability and Analysis / Observability)
File: CONTRIBUTING.md

M3 welcomes your help! Before making any significant changes, . Discussing your proposed changes ahead of time makes the contribution process smoother for everyone. Any major changes or feature requests will be reviewed by the . To make sure an issue or pull request is reviewed by the steering committee, add the . For code changes that affect M3 functionality, or fix bugs, read the . If you have found a bug in M3, and fill in the details asked for in the issue template as much as possible. For additions and changes to M3 documentation, read the .
Project: Promscale (Observability and Analysis / Observability)
File: PromscaleStorageUnhealthy.md

Promscale database is unhealthy with frequent errors while checking the health Ingestion and querying operations can witness frequent failures, timeouts or may take more time to complete Storage unhealthy alert is fired when the `/healthz` endpoint does not report success for a significant duration of time. Check Postgres logs and see if there are any errors Refer to the Mitigation for Database is unhealthy in
Project: OpenSearch (Observability and Analysis / Observability)
File: opensearch.release-notes-2.7.0.md

Add GeoTile and GeoHash Grid aggregations on GeoShapes. () Disallow multiple data paths for search nodes () ) The truncation limit of the OpenSearchJsonLayout logger is now configurable () Add 'base_path' setting to File System Repository () Return success on DeletePits when no PITs exist. () Add initial search pipelines () Add node repurpose command for search nodes () Add waitforcompletion parameter to resize, open, and forcemerge APIs () ) ) Enable sort optimization for all NumericTypes ( Remove 'cluster_manager' role attachment when using 'node.master' deprecated setting () Add new cluster settings to ignore weighted round-robin routing and fallback to default behaviour. () Add experimental support for ZSTD compression. () ) Add retry delay as dynamic setting for cluster maanger throttling. () Introduce full support for searchable snapshots () Introduce full support for Segment Replication () Introduce a new field type: flat_object to help prevent mapping explosions () Bump `org.apache.logging.log4j:log4j-core` from 2.18.0 to 2.20.0 () Bump `com.azure:azure-storage-common` from 12.19.3 to 12.20.0 ( Bump `snakeyaml` from 1.33 to 2.0 () Bump `io.projectreactor.netty:reactor-netty` from 1.1.3 to 1.1.4 Bump `com.avast.gradle:gradle-docker-compose-plugin` from 0.15.2 to 0.16.11 Bump `net.minidev:json-smart` from 2.4.8 to 2.4.9 Bump `com.google.protobuf:protobuf-java` to 3.22.2 () Bump Netty to 4.1.90.Final ( Bump `com.diffplug.spotless` from 6.15.0 to 6.17.0 Bump `org.apache.zookeeper:zookeeper` from 3.8.0 to 3.8.1 Bump `net.minidev:json-smart` from 2.4.7 to 2.4.10 Bump `org.apache.maven:maven-model` from 3.6.2 to 3.9.1 Bump `org.codehaus.jettison:jettison` from 1.5.3 to 1.5.4 () Add `com.github.luben:zstd-jni:1.5.5-1` () Bump: Netty from 4.1.90.Final to 4.1.91.Final , ASM 9.4 to ASM 9.5, ByteBuddy 1.14.2 to 1.14.3 () Bump `com.azure:azure-storage-blob` from 12.15.0 to 12.21.1 Bump `org.gradle.test-retry` from 1.5.1 to 1.5.2 Bump `org.apache.hadoop:hadoop-minicluster` from 3.3.4 to 3.3.5 Require MediaType in Strings.toString API () ) Changed `opensearch-env` to respect already set `OPENSEARCH_HOME` environment variable () Increased visibility of BaseRestHandlers `unrecognized` method using a new public `unrecognizedStrings` method. () Map, List, and Set in org.opensearch.common.collect () Added depth check in doc parser for deep nested document () Added equals/hashcode for named DocValueFormat.DateTime inner class () Fixed bug for searchable snapshot to take 'base_path' of blob into account () Fix fuzziness validation () Avoid negative memory result in IndicesQueryCache stats calculation () Fix GetSnapshots to not return non-existent snapshots with ignore_unavailable=true () Fix GlobalAggregation with profile option enabled returns incorrect result ()