cwielenb/CNCF-Dataset huggingface dataset:
Project: TDengine (App Definition and Development / Database)
File: 06-statsd.md

title: StatsD Writing sidebar_label: StatsD description: This document describes how to integrate TDengine with StatsD. import StatsD from "../14-reference/_statsd.mdx" StatsD is a simple daemon for aggregating application metrics, which has evolved rapidly in recent years into a unified protocol for collecting application performance metrics. You can write StatsD data to TDengine by simply modifying the configuration file of StatsD with the domain name (or IP address) of the server running taosAdapter and the corresponding port. It can take full advantage of TDengine's efficient storage query performance and clustering capabilities for time-series data. To write StatsD data to TDengine requires the following preparations. The TDengine cluster is deployed and functioning properly taosAdapter is installed and running properly. Please refer to the taosAdapter manual for details. StatsD has been installed. To install StatsD, please refer to <StatsD /> Start StatsD: ``` $ node stats.js config.js & [1] 8546 $ 20 Apr 09:54:41 - [8546] reading config file: config.js 20 Apr 09:54:41 - server is up INFO ``` Using the utility software `nc` to write data for test: ``` $ echo "foo:1|c" | nc -u -w0 127.0.0.1 8125 ``` Use the TDengine CLI to verify that StatsD data is written to TDengine and can read out correctly. ``` taos> show databases; name | ================================= information_schema | performance_schema | statsd | Query OK, 3 row(s) in set (0.003142s) taos> use statsd; Database changed. taos> show stables; name | ================================= foo | Query OK, 1 row(s) in set (0.002161s) taos> select * from foo; ts | value | metric_type | ======================================================================================= 2022-04-20 09:54:51.219614235 | 1 | counter | Query OK, 1 row(s) in set (0.004179s) taos> ``` :::note TDengine will automatically create unique IDs for sub-table names by the rule. :::
Project: KICS (Provisioning / Security & Compliance)
File: daaace5f-c0dc-4835-b526-7a116b7f4b4e.md

title: Enum Name Not CamelCase hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: daaace5f-c0dc-4835-b526-7a116b7f4b4e Query name: Enum Name Not CamelCase Platform: GRPC Severity: <span style="color:#5bc0de">Info</span> Category: Best Practices URL: All Enum Names should follow CamelCase and start with Capital Letter<br> ```proto title="Positive test num. 1 - proto file" hl_lines="18 10 3" syntax = "proto3" ; enum noInitCap { option allow_alias = true ; UNKNOWN = 0 ; STARTED = 1 ; RUNNING = 2[(custom_option) = "hello world"] ; } enum NOTCAMELCASE { option allow_alias = true ; UNKNOWN = 0 ; STARTED = 1 ; RUNNING = 2[(custom_option) = "hello world"] ; } message Testing { enum ALLCAPS { option allow_alias = true ; UNKNOWN = 0 ; STARTED = 1 ; RUNNING = 2[(custom_option) = "hello world"] ; } } ``` ```proto title="Negative test num. 1 - proto file" syntax = "proto3" ; enum EnumAllowingAlias { option allow_alias = true ; UNKNOWN = 0 ; STARTED = 1 ; RUNNING = 2[(custom_option) = "hello world"] ; } ```
Project: Druid (App Definition and Development / Database)
File: druid-vs-elasticsearch.md

id: druid-vs-elasticsearch title: "Apache Druid vs Elasticsearch" <!-- ~ 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 ~ ~ http://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. --> We are not experts on search systems, if anything is incorrect about our portrayal, please let us know on the mailing list or via some other means. Elasticsearch is a search system based on Apache Lucene. It provides full text search for schema-free documents and provides access to raw event level data. Elasticsearch is increasingly adding more support for analytics and aggregations. have pointed out the resource requirements for data ingestion and aggregation in Elasticsearch is much higher than those of Druid. Elasticsearch also does not support data summarization/roll-up at ingestion time, which can compact the data that needs to be stored up to 100x with real-world data sets. This leads to Elasticsearch having greater storage requirements. Druid focuses on OLAP work flows. Druid is optimized for high performance (fast aggregation and ingestion) at low cost, and supports a wide range of analytic operations. Druid has some basic search support for structured event data, but does not support full text search. Druid also does not support completely unstructured data. Measures must be defined in a Druid schema such that summarization/roll-up can be done.
Project: KubeArmor (Provisioning / Security & Compliance)
File: file-copy.md

```sh root@wordpress-fb448db97-wj7n7:/usr/bin# scp /etc/ca-certificates.conf 104.192.3.74:/mine/ bash: /usr/bin/scp: Permission denied root@wordpress-fb448db97-wj7n7:/usr/bin# ``` ``` { "Action": "Block", "ClusterName": "d3mo", "ContainerID": "548176888fca6bb6d66633794f3d5f9d54930a9d9f43d4f05c11de821c758c0f", "ContainerImage": "docker.io/library/wordpress:4.8-apache@sha256:6216f64ab88fc51d311e38c7f69ca3f9aaba621492b4f1fa93ddf63093768845", "ContainerName": "wordpress", "Data": "syscall=SYS_EXECVE", "Enforcer": "AppArmor", "HostName": "master-node", "HostPID": 72178, "HostPPID": 30490, "Labels": "app=wordpress", "Message": "Alert! remote file copy tools execution prevented.", "NamespaceName": "wordpress-mysql", "Operation": "Process", "Owner": { "Name": "wordpress", "Namespace": "wordpress-mysql", "Ref": "Deployment" }, "PID": 259, "PPID": 193, "ParentProcessName": "/bin/bash", "PodName": "wordpress-fb448db97-wj7n7", "PolicyName": "harden-wordpress-remote-file-copy", "ProcessName": "/usr/bin/scp", "Resource": "/usr/bin/scp /etc/ca-certificates.conf 104.192.3.74:/mine/", "Result": "Permission denied", "Severity": "5", "Source": "/bin/bash", "Tags": "MITRE,MITRETA0008lateralmovement,MITRETA0010exfiltration,MITRETA0006credentialaccess,MITRET1552unsecuredcredentials,NIST800-53SI-4(18),NIST,NIST800-53,NIST800-53SC-4", "Timestamp": 1696487496, "Type": "MatchedPolicy", "UpdatedTime": "2023-10-05T06:31:36.085860Z", "cluster_id": "2302", "component_name": "kubearmor", "instanceGroup": "0", "instanceID": "0", "tenant_id": "167", "workload": "1" } ```
Project: Numaflow (App Definition and Development / Streaming & Messaging)
File: SECURITY.md

Numaflow controller can be deployed in two scopes. It can be either at the Cluster level or at the Namespace level. When the Numaflow controller is deployed at the Namespace level, it will only have access to the Namespace resources. Data movement happens only within the namespace (no cross-namespaces). Numaflow provides the ability to encrypt data at rest and also in transit. All communications between the controller and Numaflow pipeline components are encrypted. These are uni-directional read-only communications.
Project: YugabyteDB (App Definition and Development / Database)
File: ddl_alter_matview.md

title: ALTER MATERIALIZED VIEW statement [YSQL] headerTitle: ALTER MATERIALIZED VIEW linkTitle: ALTER MATERIALIZED VIEW description: Use the `ALTER MATERIALIZED VIEW` statement to change the definition of a materialized view. menu: preview: identifier: ddlaltermatview parent: statements aliases: /preview/api/ysql/commands/ddlaltermatview/ type: docs Use the `ALTER MATERIALIZED VIEW` statement to change the definition of a materialized view. {{%ebnf%}} altermaterializedview, altermaterializedview_action, {{%/ebnf%}} Specify one of the following actions. Rename the materialized view to the specified name. {{< note title="Note" >}} Renaming a materialized view is a non-blocking metadata change operation. {{< /note >}} Asynchronously change the tablespace of an existing materialized view. The tablespace change will immediately reflect in the config of the materialized view, however the tablet move by the load balancer happens in the background. While the load balancer is performing the move it is perfectly safe from a correctness perspective to do reads and writes, however some query optimization that happens based on the data location may be off while data is being moved. ```sql yugabyte=# ALTER MATERIALIZED VIEW mv SET TABLESPACE mv_tblspace2; ``` ```output yugabyte=# NOTICE: Data movement for table mv is successfully initiated. yugabyte=# DETAIL: Data movement is a long running asynchronous process and can be monitored by checking the tablet placement in http://<YB-Master-host>:7000/tables ```
Project: StarRocks (App Definition and Development / Database)
File: cot.md

displayed_sidebar: "English" Returns the cotangent of the angle in radians `x`. If the angle in radians `x` is `0` or `NULL`, `NULL` is returned. ```SQL COT(x); ``` `x`: the angle in radians. DOUBLE is supported. Returns a value of the DOUBLE data type. ```Plaintext mysql> select cot(3.1415926/2); ++ | cot(3.1415926 / 2) | ++ | 2.6794896585028646e-08 | ++ 1 row in set (0.25 sec) mysql> select cot(0); +--+ | cot(0) | +--+ | NULL | +--+ 1 row in set (0.03 sec) ```
Project: YugabyteDB (App Definition and Development / Database)
File: chapter1-similarity-search.md

```text I'd like to watch a movie about a space adventure ``` The service turns your prompt into an embedding with OpenAI's model, then searches for similar movie descriptions. The results should look like this: PostgreSQL can filter movies by rank and category before doing the vector search. For instance, set rank to 7, choose Science Fiction as the category, and repeat the search again: (Hint: Pick a movie you like and add it to your library with the Add to Library button.) Here's the SQL query that YugaPlus uses to find the movie recommendations: ```sql SELECT id, title, overview, voteaverage, releasedate FROM movie WHERE vote_average >= :rank AND genres @> :category::jsonb AND 1 - (overviewvector <=> :promptvector::vector) >= :similarity_threshold ORDER BY overviewvector <=> :promptvector::vector LIMIT :max_results ```
Project: Chef InSpec (Provisioning / Security & Compliance)
File: google_logging_folder_log_sinks.md

+++ title = "googleloggingfolderlogsinks resource" draft = false gh_repo = "inspec" platform = "gcp" [menu] [menu.inspec] title = "googleloggingfolderlogsinks" identifier = "inspec/resources/gcp/googleloggingfolderlogsinks.md googleloggingfolderlogsinks resource" parent = "inspec/resources/gcp" +++ A `googleloggingfolderlogsinks` is used to test a Google FolderLogSink resource ```ruby describe.one do googleresourcemanagerfolders(parent: 'organizations/12345').names.each do |folder_name| describe googleloggingfolderlogsinks(folder: folder_name.split('/')[1]) do its('names') { should include 'inspec-gcp-folder-sink' } its('filters') { should include 'resource.type = gce_instance AND severity >= ERROR' } end end end ``` Properties that can be accessed from the `googleloggingfolderlogsinks` resource: See the resource for more information. `folders` : an array of `googleloggingfolderlogsink` folder `names` : an array of `googleloggingfolderlogsink` name `filters` : an array of `googleloggingfolderlogsink` filter `destinations` : an array of `googleloggingfolderlogsink` destination `writer_identities` : an array of `googleloggingfolderlogsink` writer_identity `include_children` : an array of `googleloggingfolderlogsink` include_children This resource supports all of the above properties as filter criteria, which can be used with `where` as a block or a method. Ensure the is enabled for the current project.
Project: YDB (App Definition and Development / Database)
File: hive.md

The Hive web-viewer provides an interface for working with Hive. Hive can be shared by a cluster or be tenant. You can go to the Hive web-viewer from the {{ ydb-short-name }} Monitoring. The home page provides information about the distribution and usage of resources by tablets on each node in the form of a table. The table is preceded by the following brief information: Tenant*: The tenant that Hive is responsible for. Tablets*: The percentage of tablets started and the number of running tablets to their total number. Boot Queue*: The number of tablets in the boot queue. Wait Queue*: The number of tablets that can't be started. Resource Total*: Resource utilization by tablets (cpu, net). Resource StDev*: Standard deviation of resource utilization (cnt, cpu, mem, net). Then there is a table where each row represents a node managed by Hive. It has the following columns: Node*: The node number. Name*: The node FQDN and ic-port. DC*: The datacenter where the node resides. Domain*: The node tenant. Uptime*: The node uptime. Unknown*: The number of tablets whose state is unknown. Starting*: The number of tablets being started. Running*: The number of tablets running. Types*: Tablet distribution by type. Usage*: A normalized dominant resource. Resources* : cnt*: The number of tablets that are not using any resources. cpu*: CPU usage by tablets. mem*: RAM usage by tablets. net*: Bandwidth usage by tablets. Active*: Enables/disables the node to move tablets to this node. Freeze*: Disables tablets to be deployed on other nodes. Kick*: Moves all tablets from the node at once. Drain*: Smoothly moves all tablets from the node. Additional pages are presented below the table: Bad tablets*: A list of tablets having issues or errors. Heavy tablets*: A list of tablets utilizing a lot of resources. Waiting tablets*: A list of tablets that can't be started. Resources*: Resource utilization by each tablet. Tenants*: A list of tenants indicating their local Hive tablets. Nodes*: A list of nodes. Storage*: A list of storage group pools. Groups*: A list of storage groups for each tablet. Settings*: The Hive configuration page. Reassign Groups*: The page for reassigning storage groups across tablets. You can also view what tablets use a particular group and, vice versa, what groups are used on a particular tablet. Click Reassign Groups to open the window with parameters for balancing: Storage pool*: Pool of storage groups for balancing. Storage group*: If the previous item is not specified, you can specify only one group separately. Type*: Type of tablets that balancing will be performed for. Channels*: Range of channels that balancing will be performed for. Percent*: Percentage of the total number of tablet channels that will be moved as a result of balancing. Inflight*: The number of tablets being moved to other groups at the same time. After specifying all the parameters, click "Query" to get the number of channels moved and unlock the "Reassign" button. Clicking this button starts reassigning.
Project: Meshery (Provisioning / Automation & Configuration)
File: cilium-past-results.md

layout: past-results-layout title: Meshery-Cilium Past Results permalink: installation/compatibility-matrix/meshery-cilium-past-results abstract: a complete compatibility matrix and project test status dashboard. language: en display-title: "false" list: exclude type: "project" service-mesh: "meshery-cilium" subheading: "Meshery-Cilium"
Project: KICS (Provisioning / Security & Compliance)
File: 6a4080ae-79bd-42f6-a924-8f534c1c018b.md

title: Google Compute Subnetwork with Private Google Access Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 6a4080ae-79bd-42f6-a924-8f534c1c018b Query name: Google Compute Subnetwork with Private Google Access Disabled Platform: Ansible Severity: <span style="color:#edd57e">Low</span> Category: Networking and Firewall URL: Google Compute Subnetwork should have Private Google Access enabled, which means 'privateipgoogle_access' should be set to yes<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="2" name: create a subnetwork google.cloud.gcpcomputesubnetwork: name: ansiblenet region: us-west1 network: "{{ network }}" ipcidrrange: 172.16.0.0/16 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" state: present ``` ```yaml title="Positive test num. 2 - yaml file" hl_lines="10" name: create a subnetwork2 google.cloud.gcpcomputesubnetwork: name: ansiblenet region: us-west1 network: "{{ network }}" ipcidrrange: 172.16.0.0/16 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" privateipgoogle_access: no state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: create a subnetwork3 google.cloud.gcpcomputesubnetwork: name: ansiblenet region: us-west1 network: "{{ network }}" ipcidrrange: 172.16.0.0/16 project: test_project auth_kind: serviceaccount serviceaccountfile: "/tmp/auth.pem" privateipgoogle_access: yes state: present ```
Project: YugabyteDB (App Definition and Development / Database)
File: dcl_alter_user.md

title: ALTER USER statement [YSQL] headerTitle: ALTER USER linkTitle: ALTER USER description: Use the ALTER USER statement to alter a role. ALTER USER is an alias for ALTER ROLE and is used to alter a role. menu: v2.18: identifier: dclalteruser parent: statements type: docs Use the `ALTER USER` statement to alter a role. `ALTER USER` is an alias for and is used to alter a role. {{%ebnf%}} alter_user, alterroleoption, role_specification, alteruserrename, alteruserconfig, config_setting {{%/ebnf%}} See for more details.
Project: Beam (App Definition and Development / Streaming & Messaging)
File: ADD_LOGO.md

<!-- 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 http://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. --> Please follow these steps to add your company or project logo to Apache Beam page: Fork repository Add file with company or project name to the folder e.g., `company.md` Add company/project logo to the folder. Please use your company/project name e.g. `ricardo.png` Copy template below to the created file and replace next fields with your data | Field | Description | |-|| | `title` | Company/project name | | `icon` | Path to the company/project logo e.g. "/images/logos/powered-by/company_name.png" | | `hasNav` | Specified logo page has space for left & right nav menu | | `hasLink` | Links logo image to the company/project website instead of displaying cardDescription, optional | | `cardDescription` | Company or project description, optional | ``` title: "Cloud Dataflow" icon: /images/logos/powered-by/company_name.png hasNav: true hasLink: false cardDescription: "Google Cloud Dataflow is a fully managed service for executing Apache Beam pipelines within the Google Cloud Platform ecosystem." <!-- Licensed 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 http://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. --> ``` Create pull request to the Apache Beam repository with your changes
Project: KICS (Provisioning / Security & Compliance)
File: caa93370-791f-4fc6-814b-ba6ce0cb4032.md

title: Not Limited Capabilities For Pod Security Policy hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: caa93370-791f-4fc6-814b-ba6ce0cb4032 Query name: Not Limited Capabilities For Pod Security Policy Platform: Kubernetes Severity: <span style="color:#5bc0de">Info</span> Category: Insecure Configurations URL: Limit capabilities for a Pod Security Policy<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="10" apiVersion: policy/v1beta1 kind: PodSecurityPolicy metadata: name: restricted annotations: seccomp.security.alpha.kubernetes.io/allowedProfileNames: 'docker/default,runtime/default' apparmor.security.beta.kubernetes.io/allowedProfileNames: 'runtime/default' seccomp.security.alpha.kubernetes.io/defaultProfileName: 'runtime/default' apparmor.security.beta.kubernetes.io/defaultProfileName: 'runtime/default' spec: privileged: false allowPrivilegeEscalation: false volumes: 'configMap' 'emptyDir' 'projected' 'secret' 'downwardAPI' 'persistentVolumeClaim' hostNetwork: false hostIPC: false hostPID: false runAsUser: rule: 'MustRunAsNonRoot' seLinux: rule: 'RunAsAny' supplementalGroups: rule: 'MustRunAs' ranges: min: 1 max: 65535 fsGroup: rule: 'MustRunAs' ranges: min: 1 max: 65535 readOnlyRootFilesystem: false ``` ```yaml title="Negative test num. 1 - yaml file" apiVersion: policy/v1beta1 kind: PodSecurityPolicy metadata: name: restricted annotations: seccomp.security.alpha.kubernetes.io/allowedProfileNames: 'docker/default,runtime/default' apparmor.security.beta.kubernetes.io/allowedProfileNames: 'runtime/default' seccomp.security.alpha.kubernetes.io/defaultProfileName: 'runtime/default' apparmor.security.beta.kubernetes.io/defaultProfileName: 'runtime/default' spec: privileged: false allowPrivilegeEscalation: false requiredDropCapabilities: ALL volumes: 'configMap' 'emptyDir' 'projected' 'secret' 'downwardAPI' 'persistentVolumeClaim' hostNetwork: false hostIPC: false hostPID: false runAsUser: rule: 'MustRunAsNonRoot' seLinux: rule: 'RunAsAny' supplementalGroups: rule: 'MustRunAs' ranges: min: 1 max: 65535 fsGroup: rule: 'MustRunAs' ranges: min: 1 max: 65535 readOnlyRootFilesystem: false ```
Project: Kui (App Definition and Development / Application Definition & Image Build)
File: kui_shell_core.EditableSpec.md

/ / EditableSpec .EditableSpec clearable: `boolean` Should we offer a Clear button? Default: false readOnly: `boolean` Should the editor be opened in read-only mode? Default: false revert: `Object` Button and Controller to handle reverts | Name | Type | | : | :- | | `label?` | `string` | | `onRevert` | () => `string` \| `Promise`<`string`\> | save: `Object` Button and Controller to handle saves | Name | Type | | :- | :- | | `label` | `string` | | `onSave` | (`data`: `string`) => `Save` \| `Promise`<`Save`\> |
Project: ClickHouse (App Definition and Development / Database)
File: detached_parts.md

slug: /en/operations/system-tables/detached_parts Contains information about detached parts of tables. The `reason` column specifies why the part was detached. For user-detached parts, the reason is empty. Such parts can be attached with command. For the description of other columns, see . If part name is invalid, values of some columns may be `NULL`. Such parts can be deleted with .