cwielenb/CNCF-Dataset huggingface dataset:
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_pod.KubePod.md

title: "Interface: KubePod" linkTitle: "KubePod" slug: "libk8spod.KubePod" .KubePod `KubePod` `Optional` apiVersion: `string` . _ kind: `string` Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. In CamelCase. Cannot be updated. `see` . _ metadata: . _ spec: _ status: `Object` | Name | Type | | : | : | | `conditions` | [] | | `containerStatuses` | [] | | `ephemeralContainerStatuses?` | [] | | `hostIP` | `string` | | `initContainerStatuses?` | [] | | `message?` | `string` | | `phase` | `string` | | `qosClass?` | `string` | | `reason?` | `string` | | `startTime` | |
Project: Graylog (Observability and Analysis / Observability)
File: ColorPicker.md

```js import createReactClass from 'create-react-class'; const ColorPickerExample = createReactClass({ getInitialState() { return { color: undefined, }; }, handleColorChange(color) { this.setState({ color: color }); }, render() { const { color } = this.state; return ( <div> <p>{color ? `You picked ${color}.` : 'Pick a color'}</p> <ColorPicker color={color} onChange={this.handleColorChange} /> </div> ); }, }); <ColorPickerExample /> ```
Project: Netdata (Observability and Analysis / Observability)
File: vsphere_outbound_packets_dropped_ratio.md

This alert calculates the ratio of `outbound dropped packets` for a network interface on a VMware vSphere Virtual Machine over the last 10 minutes. If you receive this alert, it means your Virtual Machine may be experiencing network performance issues due to dropped packets. Outbound dropped packets are network packets that are discarded by a network interface when they are supposed to be transmitted (sent) from the Virtual Machine to the destination. This can be caused by several factors, such as network congestion, insufficient buffer resources, or malfunctioning hardware. There are several possible reasons for a high ratio of outbound dropped packets, including: Network congestion: High traffic may cause your network interface to drop packets if it cannot process all the outbound packets fast enough. Insufficient buffer resources: The network interface requires buffer memory to store and process outbound packets. If not enough buffer memory is available, packets may be dropped. Malfunctioning hardware: Issues with network hardware, such as the network adapter, could result in dropped packets. Check for network congestion Monitor your network traffic using monitoring tools such as `vSphere Client`, `vRealize Network Insight`, or other third-party tools. Identify whether there is an increase in traffic that could be causing congestion. Resolve any issues related to the cause of the increased traffic to relieve the congestion. Inspect buffer resources Use `vSphere Client` to check your Virtual Machine's network interface settings for correct buffer allocation. Increase buffer allocation if required or tune the buffer settings to ensure better resource usage. Verify network hardware Check the status of the network adapter using the `vSphere Client` or the VMware vSphere Command-Line Interface (vSphere CLI). Look for any signs of errors or issues. Verify that the network adapter driver is up-to-date and compatible with your vSphere environment. Consider troubleshooting or replacing the network adapter if hardware issues are suspected.
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_cluster.KubeObjectIface.md

title: "Interface: KubeObjectIface<T>" linkTitle: "KubeObjectIface" slug: "libk8scluster.KubeObjectIface" .KubeObjectIface | Name | Type | | : | : | | `T` | extends \| | new KubeObjectIface(`json`) | Name | Type | | : | : | | `json` | `T` | className: `string` apiList(`onList`, `onError?`, `opts?`): `any` | Name | Type | | : | : | | `onList` | (`arg`: `any`[]) => `void` | | `onError?` | (`err`: ) => `void` | | `opts?` | | `any` _ `Optional` getAuthorization(`arg`, `resourceAttrs?`): `any` | Name | Type | | : | : | | `arg` | `string` | | `resourceAttrs?` | | `any` _ getErrorMessage(`err?`): ``null`` \| `string` | Name | Type | | : | : | | `err?` | ``null`` \| | ``null`` \| `string` _ useApiGet(`onGet`, `name`, `namespace?`, `onError?`): `void` | Name | Type | | : | : | | `onGet` | (...`args`: `any`) => `void` | | `name` | `string` | | `namespace?` | `string` | | `onError?` | (`err`: ) => `void` | `void` _ useApiList(`onList`, `onError?`, `opts?`): `any` | Name | Type | | : | : | | `onList` | (`arg`: `any`[]) => `void` | | `onError?` | (`err`: ) => `void` | | `opts?` | | `any` _ useGet(`name`, `namespace?`): , (`item`: `any`) => `void`, (`err`: ``null`` \| ) => `void`] | Name | Type | | : | : | | `name` | `string` | | `namespace?` | `string` | , (`item`: `any`) => `void`, (`err`: ``null`` \| ) => `void`] _ useList(`opts?`): , (`items`: `any`) => `void`] | Name | Type | | : | : | | `opts?` | | , (`items`: `any`) => `void`]
Project: Grafana Mimir (Observability and Analysis / Observability)
File: feature_request.md

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

key | value | date | 2024-03-14T13:48:35+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes `invif.py` crashed on empty operstatus. This is fixed now as at least on some Cisco ASA/FirePower devices this value is empty.
Project: Headlamp (Observability and Analysis / Observability)
File: plugin_lib.Plugin.md

title: "Class: Plugin" linkTitle: "Plugin" slug: "plugin_lib.Plugin" .Plugin Plugins may call Headlamp.registerPlugin(pluginId: string, pluginObj: Plugin) to register themselves. They will have their initialize(register) method called at plugin initialization time. new Plugin() `Abstract` initialize(`register`): `boolean` \| `void` initialize is called for each plugin with a Registry which gives the plugin methods for doing things. `see` Registry | Name | Type | | : | : | | `register` | | `boolean` \| `void` The return code is not used, but used to be required.
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_crd.KubeCRD.md

title: "Interface: KubeCRD" linkTitle: "KubeCRD" slug: "libk8scrd.KubeCRD" .KubeCRD `KubeCRD` `Optional` apiVersion: `string` . _ kind: `string` Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. In CamelCase. Cannot be updated. `see` . _ metadata: . _ spec: `Object` | Name | Type | | : | : | | `group` | `string` | | `names` | { `kind`: `string` ; `listKind`: `string` ; `plural`: `string` ; `singular`: `string` } | | `names.kind` | `string` | | `names.listKind` | `string` | | `names.plural` | `string` | | `names.singular` | `string` | | `scope` | `string` | | `version` | `string` | | `versions` | { `additionalPrinterColumns`: { `description?`: `string` ; `format?`: `string` ; `jsonPath`: `string` ; `name`: `string` ; `priority?`: `number` ; `type`: `string` }[] ; `name`: `string` ; `served`: `boolean` ; `storage`: `boolean` }[] |
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_priorityClass.PriorityClass.md

title: "Class: PriorityClass" linkTitle: "PriorityClass" slug: "libk8spriorityClass.PriorityClass" .PriorityClass `any` `PriorityClass` new PriorityClass(`json`) | Name | Type | | : | : | | `json` | | makeKubeObject<KubePriorityClass\>('priorityClass').constructor `Static` apiEndpoint: `Object` | Name | Type | | : | : | | `apiInfo` | { `group`: `string` ; `resource`: `string` ; `version`: `string` }[] | | `delete` | (`name`: `string`, `queryParams?`: , `cluster?`: `string`) => `Promise`<`any`\> | | `get` | (`name`: `string`, `cb`: , `errCb`: , `queryParams?`: , `cluster?`: `string`) => `Promise`<() => `void`\> | | `isNamespaced` | `boolean` | | `list` | (`cb`: , `errCb`: , `queryParams?`: , `cluster?`: `string`) => `Promise`<() => `void`\> | | `patch` | (`body`: `OpPatch`, `cluster?`: `string`) => `Promise`<`any`\> | | `post` | (`body`: , `queryParams?`: , `cluster?`: `string`) => `Promise`<`any`\> | | `put` | (`body`: , `queryParams?`: , `cluster?`: `string`) => `Promise`<`any`\> | _ `Static` className: `string` makeKubeObject<KubePriorityClass\>('priorityClass').className `get` description(): `string` `string` _ `get` globalDefault(): ``null`` \| `boolean` ``null`` \| `boolean` _ `get` preemptionPolicy(): `string` `string` _ `get` value(): `string` `string` _ `Static` `get` listRoute(): `string` `string` _ `Static` `get` pluralName(): `string` `string` `Static` apiList(`onList`, `onError?`, `opts?`): `any` | Name | Type | | : | : | | `onList` | (`arg`: `any`[]) => `void` | | `onError?` | (`err`: ) => `void` | | `opts?` | | `any` makeKubeObject<KubePriorityClass\>('priorityClass').apiList _ `Static` `Optional` getAuthorization(`arg`, `resourceAttrs?`): `any` | Name | Type | | : | : | | `arg` | `string` | | `resourceAttrs?` | | `any` makeKubeObject<KubePriorityClass\>('priorityClass').getAuthorization _ `Static` getErrorMessage(`err?`): ``null`` \| `string` | Name | Type | | : | : | | `err?` | ``null`` \| | ``null`` \| `string` makeKubeObject<KubePriorityClass\>('priorityClass').getErrorMessage _ `Static` useApiGet(`onGet`, `name`, `namespace?`, `onError?`): `void` | Name | Type | | : | : | | `onGet` | (...`args`: `any`) => `void` | | `name` | `string` | | `namespace?` | `string` | | `onError?` | (`err`: ) => `void` | `void` makeKubeObject<KubePriorityClass\>('priorityClass').useApiGet _ `Static` useApiList(`onList`, `onError?`, `opts?`): `any` | Name | Type | | : | : | | `onList` | (`arg`: `any`[]) => `void` | | `onError?` | (`err`: ) => `void` | | `opts?` | | `any` makeKubeObject<KubePriorityClass\>('priorityClass').useApiList _ `Static` useGet(`name`, `namespace?`): , (`item`: `any`) => `void`, (`err`: ``null`` \| ) => `void`] | Name | Type | | : | : | | `name` | `string` | | `namespace?` | `string` | , (`item`: `any`) => `void`, (`err`: ``null`` \| ) => `void`] makeKubeObject<KubePriorityClass\>('priorityClass').useGet _ `Static` useList(`opts?`): , (`items`: `any`) => `void`] | Name | Type | | : | : | | `opts?` | | , (`items`: `any`) => `void`] makeKubeObject<KubePriorityClass\>('priorityClass').useList
Project: Graylog (Observability and Analysis / Observability)
File: ExternalLink.md

`ExternalLink` in a text: ```js <p>Please read the <ExternalLink href="http://docs.graylog.org/">Graylog documentation</ExternalLink> to learn about the product.</p> ``` `ExternalLink` with a different icon: ```js <ExternalLink href="http://docs.graylog.org/" iconName="help"> Graylog documentation </ExternalLink> ``` `ExternalLink` without a `href` prop: ```js <ExternalLink>Graylog documentation</ExternalLink> ```
Project: Grafana Mimir (Observability and Analysis / Observability)
File: CONDUCT.md

Cobra will follow a steady release cadence. Non breaking changes will be released as minor versions quarterly. Patch bug releases are at the discretion of the maintainers. Users can expect security patch fixes to be released within relatively short order of a CVE becoming known. For more information on security patch fixes see the CVE section below. Releases will follow . Users tracking the Master branch should expect unpredictable breaking changes as the project continues to move forward. For stability, it is highly recommended to use a release. We will maintain two major releases in a moving window. The N-1 release will only receive bug fixes and security updates and will be dropped once N+1 is released. Deprecation of Go versions or dependent packages will only occur in major releases. To reduce the change of this taking users by surprise, any large deprecation will be preceded by an announcement in the and an Issue on Github. Maintainers will make every effort to release security patches in the case of a medium to high severity CVE directly impacting the library. The speed in which these patches reach a release is up to the discretion of the maintainers. A low severity CVE may be a lower priority than a high severity one. Cobra maintainers will use GitHub issues and the as the primary means of communication with the community. This is to foster open communication with all users and contributors. Breaking changes are generally allowed in the master branch, as this is the branch used to develop the next release of Cobra. There may be times, however, when master is closed for breaking changes. This is likely to happen as we near the release of a new version. Breaking changes are not allowed in release branches, as these represent minor versions that have already been released. These version have consumers who expect the APIs, behaviors, etc, to remain stable during the lifetime of the patch stream for the minor release. Examples of breaking changes include: Removing or renaming exported constant, variable, type, or function. Updating the version of critical libraries such as `spf13/pflag`, `spf13/viper` etc... Some version updates may be acceptable for picking up bug fixes, but maintainers must exercise caution when reviewing. There may, at times, need to be exceptions where breaking changes are allowed in release branches. These are at the discretion of the project's maintainers, and must be carefully considered before merging. Maintainers will ensure the Cobra test suite utilizes the current supported versions of Golang. Changes to this document and the contents therein are at the discretion of the maintainers. None of the contents of this document are legally binding in any way to the maintainers or the users.
Project: HertzBeat (Observability and Analysis / Observability)
File: postgresql.md

id: postgresql title: MonitoringPostgreSQL database monitoring sidebar_label: PostgreSQL database keywords: [open source monitoring tool, open source database monitoring tool, monitoring postgresql database metrics] Collect and monitor the general performance Metrics of PostgreSQL database. Support PostgreSQL 10+. | 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 the database. The default is 5432 | | Query timeout | Set the timeout time when SQL query does not respond to data, unit: ms, default: 3000ms | | Database name | Database instance name, optional | | Username | Database connection user name, optional | | Password | Database connection password, optional | | URL | Database connection URLoptionalIf configured, the database name, user name, password and other parameters in the URL will overwrite the above configured parameters | | 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 | | -- | -- | -- | | server_version | none | Version number of the database server | | port | none | Database server exposure service port | | server_encoding | none | Character set encoding of database server | | data_directory | none | Database storage data disk address | | max_connections | connections | Database maximum connections | | Metric name | Metric unit | Metric help description | | -- | -- | -- | | name | none | Database name, or share-object is a shared object | | conflicts | times | The number of queries canceled in the database due to a conflict with recovery | | deadlocks | number | Number of deadlocks detected in the database | | blks_read | times | The number of disk blocks read in the database | | blks_hit | times | Times the disk block has been found to be in the buffer, so there is no need to read it once (This only includes hits in the PostgreSQL buffer, not in the operating system file system buffer) | | blkreadtime | ms | Time spent by the backend reading data file blocks in the database | | blkwritetime | ms | Time spent by the backend writing data file blocks in the database | | stats_reset | none | The last time these statistics were reset | | Metric name | Metric unit | Metric help description | | -- | -- | -- | | running | connections | Number of current client connections |
Project: VictoriaMetrics (Observability and Analysis / Observability)
File: migrationguide.md

This guide is intended to assist in the migration from the `azure-storage-blob-go` module, or previous betas of `azblob`, to the latest releases of the `azblob` module. The redesign of the `azblob` module separates clients into various sub-packages. In previous versions, the public surface area was "flat", so all clients and supporting types were in the `azblob` package. This made it difficult to navigate the public surface area. In `azure-storage-blob-go` a client constructor always requires a `url.URL` and `Pipeline` parameters. In `azblob` a client constructor always requires a `string` URL, any specified credential type, and a `*ClientOptions` for optional values. You pass `nil` to accept default options. ```go // new code client, err := azblob.NewClient("<my storage account URL>", cred, nil) ``` In `azure-storage-blob-go` you created a `Pipeline` with the required credential type. This pipeline was then passed to the client constructor. In `azblob`, you pass the required credential directly to the client constructor. ```go // new code. cred is an AAD token credential created from the azidentity module client, err := azblob.NewClient("<my storage account URL>", cred, nil) ``` The `azure-storage-blob-go` module provided limited support for OAuth token authentication via `NewTokenCredential`. This been replaced by using Azure Identity credentials from . Authentication with a shared key via `NewSharedKeyCredential` remains unchanged. In `azure-storage-blob-go` you created a `Pipeline` with `NewAnonymousCredential` to support anonymous or SAS authentication. In `azblob` you use the construtor `NewClientWithNoCredential()` instead. ```go // new code client, err := azblob.NewClientWithNoCredential("<public blob or blob with SAS URL>", nil) ``` In `azure-storage-blob-go` you explicitly created a `Marker` type that was used to page over results (). In `azblob`, operations that return paginated values return a `*runtime.Pager[T]`. ```go // new code pager := client.NewListBlobsFlatPager("my-container", nil) for pager.More() { page, err := pager.NextPage(context.TODO()) // process results } ``` In `azure-storage-blob-go` you explicitly created a HTTP pipeline with configuration before creating a client. This pipeline instance was then passed as an argument to the client constructor (). In `azblob` a HTTP pipeline is created during client construction. The pipeline is configured through the `azcore.ClientOptions` type. ```go // new code client, err := azblob.NewClient(account, cred, &azblob.ClientOptions{ ClientOptions: azcore.ClientOptions{ // configure HTTP pipeline options here }, }) ```
Project: Netdata (Observability and Analysis / Observability)
File: wireless_network_interfaces.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/integrations/wirelessnetworkinterfaces.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/proc.plugin/metadata.yaml" sidebar_label: "Wireless network interfaces" learn_status: "Published" learnrelpath: "Collecting Metrics/Linux Systems/Network" 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/network-wired.svg" width="150"/> Plugin: proc.plugin Module: /proc/net/wireless <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> Monitor wireless devices with metrics about status, link quality, signal level, noise level and more. 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 | |:|:-|:-| | wireless.status | status | status | | wireless.linkquality | linkquality | value | | wireless.signallevel | signallevel | dBm | | wireless.noiselevel | noiselevel | dBm | | wireless.discarded_packets | nwid, crypt, frag, retry, misc | packets/s | | wireless.missedbeacons | missedbeacons | frames/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: Graylog (Observability and Analysis / Observability)
File: Wizard.md

Using `Wizard` as uncontrolled component: ```js import createReactClass from 'create-react-class'; const Component1 = createReactClass({ render() { return (<span> Type 'hello': <input value={this.props.input_value} onChange={this.props.onChange} /> </span>); }, }); const WizardExample = createReactClass({ getInitialState() { return { input_value: "", }; }, onChange(e) { this.setState({ input_value: e.target.value }); }, enableNext() { return this.state.input_value !== 'hello'; }, render() { const steps = [ { key: 'Key1', title: 'Title1', component: (<Component1 inputvalue={this.state.inputvalue} onChange={this.onChange}/>) }, { key: 'Key2', title: 'Title2', component: (<div>Component2</div>), disabled: this.enableNext() }, { key: 'Key3', title: 'Title3', component: (<div>Component3</div>), disabled: this.enableNext() }, ]; return ( <Wizard steps={steps} horizontal={this.props.horizontal}> <div>Preview: {this.state.input_value}</div> </Wizard> ); }, }); <div> <WizardExample horizontal={false} /> <hr/> <WizardExample horizontal /> </div> ``` Using `Wizard` as controlled component with no previous/next buttons and no preview: ```js import createReactClass from 'create-react-class'; const Component1 = createReactClass({ render() { return (<span> Type 'hello': <input value={this.props.input_value} onChange={this.props.onChange} /> </span>); }, }); const ControlledWizardExample = createReactClass({ getInitialState() { return { activeStep: 'Key3', input_value: "", }; }, onChange(e) { this.setState({ input_value: e.target.value }); }, changeStep(nextStep) { if (nextStep === 'Key2') { this.setState({ activeStep: 'Key3' }); return; } this.setState({ activeStep: nextStep }); }, render() { const steps = [ { key: 'Key1', title: 'Title1', component: (<Component1 inputvalue={this.state.inputvalue} onChange={this.onChange}/>) }, { key: 'Key2', title: 'Title2', component: (<div>Component2</div>), disabled: false }, { key: 'Key3', title: 'Title3', component: (<div style={{ backgroundColor: 'lightblue' }}>Component3</div>), disabled: false }, { key: 'Key4', title: 'Title4', component: (<div>Component4</div>), disabled: false }, ]; return ( <Wizard activeStep={this.state.activeStep} steps={steps} horizontal={this.props.horizontal} onStepChange={this.changeStep} hidePreviousNextButtons /> ); }, }); <div> <p>Goes to <em>Title3</em> when selecting <em>Title2</em>.</p> <ControlledWizardExample horizontal /> </div> ```