cwielenb/CNCF-Dataset huggingface dataset:
Project: Promscale (Observability and Analysis / Observability)
File: compression-job-hotfix.md

Users have reported that Promscale background maintenance jobs that handle data compression and retention get slower over time as the number of TimescaleDB chunks grows. We've identified the problem which is related to two suboptimal queries used when compressing data. The code that uses this queries are functions that run inside the database and so the hotfix involves updating those functions by executing SQL commands against the database. This problem affects Promscale versions 0.10.0 and earlier. Below we explain the steps to apply a hotfix to your Promscale instance. This fix will be included in the next release of Promscale. Upgrade Promscale to version 0.10.0. Download the . Apply the hotfix by executing the SQL code in the hotfix. For example you can use psql: `psql <your connection options> -f hotfix-compression-job-performance.sql` To rollback the hotfix and restore the original version of the functions in Promscale 0.10.0: Download the . Apply the rollback file by executing the SQL code in the hotfix: `psql <your connection options> -f rollback-hotfix-compression-job-performance.sql`
Project: Netdata (Observability and Analysis / Observability)
File: windows_disk_in_use.md

This alert is triggered when the disk space utilization on a Windows system surpasses the defined thresholds. If you receive this alert, it means your system's disk usage is high, and you might need to free up space. Disk space utilization is crucial for the stable and efficient operation of your system. As the disk fills up, system processes may slow down or fail due to insufficient storage space. Moreover, new applications and updates may require additional storage, which can cause issues if not enough disk space is available. Check disk usage in detail To check the disk usage on your Windows system, you can use `Disk Management` tool by searching for it in the Start menu, or by right-clicking on Computer in the File Explorer and selecting "Manage." Analyze disk usage by folders and files Use a disk space analyzer tool like or to find the largest files and folders on your system. These tools will help you identify areas where you can free up space. Clean up unnecessary files Empty the recycle bin on your Windows system. In the File Explorer, right-click on the system drive (usually C:), and select "Properties." Navigate to the "General" tab and click on "Disk Cleanup" to free up space by removing temporary files, system files and other items that can be safely deleted. Uninstall unused applications using the Programs and Features setting in the Control Panel. Move larger files such as media or documents to an external storage device or cloud storage service. Monitor disk usage Keep an eye on the disk usage to prevent it from surpassing the threshold again in the future. Pay attention to system and software updates that may require additional storage, as well as the growth of log files or temporary files generated by your computer's operation.
Project: SkyWalking (Observability and Analysis / Observability)
File: backend-setting-override.md

SkyWalking backend supports setting overrides by system properties and system environment variables. You may override the settings in `application.yml` ModuleName.ProviderName.SettingKey. Example Override `restHost` in this setting segment ```yaml core: default: restHost: ${SWCOREREST_HOST:0.0.0.0} restPort: ${SWCOREREST_PORT:12800} restContextPath: ${SWCORERESTCONTEXTPATH:/} gRPCHost: ${SWCOREGRPC_HOST:0.0.0.0} gRPCPort: ${SWCOREGRPC_PORT:11800} ``` Use command arg ``` -Dcore.default.restHost=172.0.4.12 ``` Example Override `restHost` in this setting segment through environment variables ```yaml core: default: restHost: ${REST_HOST:0.0.0.0} restPort: ${SWCOREREST_PORT:12800} restContextPath: ${SWCORERESTCONTEXTPATH:/} gRPCHost: ${SWCOREGRPC_HOST:0.0.0.0} gRPCPort: ${SWCOREGRPC_PORT:11800} ``` If the `REST_HOST ` environment variable exists in your operating system and its value is `172.0.4.12`, then the value of `restHost` here will be overwritten to `172.0.4.12`; otherwise, it will be set to `0.0.0.0`. Placeholder nesting is also supported, like `${RESTHOST:${ANOTHERREST_HOST:127.0.0.1}}`. In this case, if the `RESTHOST ` environment variable does not exist, but the ```RESTANOTHERRESTHOSTHOST``` environment variable exists, and its value is `172.0.4.12`, then the value of `restHost` here will be overwritten to `172.0.4.12`; otherwise, it will be set to `127.0.0.1`.
Project: GO Feature Flag (Observability and Analysis / Feature Flagging)
File: http.md

sidebar_position: 2 The will perform an HTTP Request with your configuration to get your flags. ```go linenums="1" err := ffclient.Init(ffclient.Config{ PollingInterval: 3 * time.Second, Retriever: &httpretriever.Retriever{ URL: "http://example.com/flag-config.yaml", Timeout: 2 * time.Second, }, }) defer ffclient.Close() ``` To configure your HTTP endpoint: | Field | Description | ||--| | `URL` | Location where to retrieve the file <br/> (ex: ). | | `Method` | the HTTP method you want to use <br/>(default is GET). | | `Body` | (optional)<br/>If you need a body to get the flags. | | `Header` | (optional)<br/>Header you should pass while calling the endpoint (useful for authorization). | | `Timeout` | (optional)<br/>Timeout for the HTTP call <br/>(default is 10 seconds). |
Project: Cortex (Observability and Analysis / Observability)
File: LICENSE.md

The MIT License (MIT) Copyright (c) 2014 Mitchell Hashimoto Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Project: Grafana Mimir (Observability and Analysis / Observability)
File: v4.2.md

title: "Grafana Mimir Helm chart version 4.2 release notes" menuTitle: "V4.2 release notes" description: "Release notes for Grafana Mimir Helm chart version 4.2" weight: 300 Grafana Labs is excited to announce version 4.2 of the Grafana Mimir Helm chart, which is compatible with Grafana Mimir v2.6 or Grafana Enterprise Metrics (GEM) v2.6. The `mimir-distributed` Helm chart is the best way to install Mimir on Kubernetes. To learn about new features and enhancements in Grafana Mimir or GEM, see the release notes for or . The highlights that follow include the top features, enhancements, and bugfixes in this release. For a comprehensive list of changes, see the . Note: If you are upgrading from a previous major version, review the changelog entry for all the major releases since then and perform the necessary migrations. This is a re-release of Grafana Mimir Helm chart version 4.1 to include GEM version v2.6. It also includes the following notable change: You can override the NGINX error log level with the `nginx.nginxConfig.errorLogLevel` value, and disable the access log with the `nginx.nginxConfig.accessLogEnabled` value. : Updated Go version in Mimir and GEM images to 1.20.3 and 1.19.8 to fix CVE-2023-24538.
Project: Graylog (Observability and Analysis / Observability)
File: SECURITY.md

Graylog is addressing vulnerabilities in the product for the current and the previous releases (a release is anything that increases either the major or the minor version part, in a understanding) of the last twelve months. We highly recommend anyone using a version that is older than twelve months or the last two releases to upgrade as soon as possible. We are grateful for anyone reporting a vulnerability, helping us to make Graylog better and more secure. Additionally, we encourage everyone to disclose bugs in a responsible way, allowing us and other Graylog users to react accordingly in a timely manner. That means: If you want to report a critical bug that could: allow someone to steal credentials, execute code or escalate privileges, please send a bug report to security@graylog.com before publishing it. This allows us to fix it, create a new version and allows other Graylog users to update before the information is out in the wild. After receiving the bug report, we will immediately get back to you to coordinate the required action. If you want to report a non-critical bug, write to security@graylog.com or . This is an open source project. If you discover a bug and fix it, you are very welcome to submit a PR. You will be rewarded with the everlasting gratitude of the Graylog team and the community! Thanks and happy logging!
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_serviceAccount.ServiceAccount.md

title: "Class: ServiceAccount" linkTitle: "ServiceAccount" slug: "libk8sserviceAccount.ServiceAccount" .ServiceAccount `any` `ServiceAccount` new ServiceAccount(`json`) | Name | Type | | : | : | | `json` | | makeKubeObject<KubeServiceAccount\>('serviceAccount').constructor `Static` apiEndpoint: `Object` | Name | Type | | : | : | | `scale?` | { `get`: (`namespace`: `string`, `name`: `string`, `clusterName?`: `string`) => `Promise`<`any`\> ; `put`: (`body`: { `metadata`: ; `spec`: { `replicas`: `number` } }, `clusterName?`: `string`) => `Promise`<`any`\> } | | `scale.get` | (`namespace`: `string`, `name`: `string`, `clusterName?`: `string`) => `Promise`<`any`\> | | `scale.put` | (`body`: { `metadata`: ; `spec`: { `replicas`: `number` } }, `clusterName?`: `string`) => `Promise`<`any`\> | _ `Static` className: `string` makeKubeObject<KubeServiceAccount\>('serviceAccount').className `get` secrets(): { `apiVersion`: `string` ; `fieldPath`: `string` ; `kind`: `string` ; `name`: `string` ; `namespace`: `string` ; `uid`: `string` }[] { `apiVersion`: `string` ; `fieldPath`: `string` ; `kind`: `string` ; `name`: `string` ; `namespace`: `string` ; `uid`: `string` }[] `Static` apiList(`onList`, `onError?`, `opts?`): `any` | Name | Type | | : | : | | `onList` | (`arg`: `any`[]) => `void` | | `onError?` | (`err`: ) => `void` | | `opts?` | | `any` makeKubeObject<KubeServiceAccount\>('serviceAccount').apiList _ `Static` `Optional` getAuthorization(`arg`, `resourceAttrs?`): `any` | Name | Type | | : | : | | `arg` | `string` | | `resourceAttrs?` | | `any` makeKubeObject<KubeServiceAccount\>('serviceAccount').getAuthorization _ `Static` getErrorMessage(`err?`): ``null`` \| `string` | Name | Type | | : | : | | `err?` | ``null`` \| | ``null`` \| `string` makeKubeObject<KubeServiceAccount\>('serviceAccount').getErrorMessage _ `Static` useApiGet(`onGet`, `name`, `namespace?`, `onError?`): `void` | Name | Type | | : | : | | `onGet` | (...`args`: `any`) => `void` | | `name` | `string` | | `namespace?` | `string` | | `onError?` | (`err`: ) => `void` | `void` makeKubeObject<KubeServiceAccount\>('serviceAccount').useApiGet _ `Static` useApiList(`onList`, `onError?`, `opts?`): `any` | Name | Type | | : | : | | `onList` | (`arg`: `any`[]) => `void` | | `onError?` | (`err`: ) => `void` | | `opts?` | | `any` makeKubeObject<KubeServiceAccount\>('serviceAccount').useApiList _ `Static` useGet(`name`, `namespace?`): , (`item`: `any`) => `void`, (`err`: ``null`` \| ) => `void`] | Name | Type | | : | : | | `name` | `string` | | `namespace?` | `string` | , (`item`: `any`) => `void`, (`err`: ``null`` \| ) => `void`] makeKubeObject<KubeServiceAccount\>('serviceAccount').useGet _ `Static` useList(`opts?`): , (`items`: `any`) => `void`] | Name | Type | | : | : | | `opts?` | | , (`items`: `any`) => `void`] makeKubeObject<KubeServiceAccount\>('serviceAccount').useList
Project: Headlamp (Observability and Analysis / Observability)
File: lib_k8s_mutatingWebhookConfiguration.KubeRuleWithOperations.md

title: "Interface: KubeRuleWithOperations" linkTitle: "KubeRuleWithOperations" slug: "libk8smutatingWebhookConfiguration.KubeRuleWithOperations" .KubeRuleWithOperations apiGroups: `string`[] _ apiVersions: `string`[] _ operations: `string`[] _ resources: `string`[] _ `Optional` scope: `string`
Project: Graylog (Observability and Analysis / Observability)
File: SearchForm.md

Search form with uncontrolled query string: ```js import createReactClass from 'create-react-class'; import { Button } from 'components/bootstrap'; const SearchFormExample = createReactClass({ getInitialState() { return { query: '', }; }, onSearch(query, resetState) { this.setState({ query: query }); setTimeout(resetState, 2 * 1000); }, onReset() { this.setState({ query: '' }); }, render() { return ( <div> <span>Query: "{this.state.query}"</span> <SearchForm onSearch={this.onSearch} onReset={this.onReset} label="Search" useLoadingState> <Button>Add-on</Button> </SearchForm> </div> ); }, }); <SearchFormExample /> ``` Search form with controlled query string and help: ```js import createReactClass from 'create-react-class'; import { Button } from 'components/bootstrap'; import { Icon } from 'components/common'; const SearchFormExample = createReactClass({ getInitialState() { return { queryTemplate: 'test', query: '', }; }, onQueryTemplateChange(e) { this.setState({ queryTemplate: e.target.value }); }, onSearch(query, resetState) { this.setState({ query: query }); setTimeout(resetState, 2 * 1000); }, onReset() { this.setState({ query: '' }); }, render() { return ( <div> Query template: <input type="text" value={this.state.queryTemplate} onChange={this.onQueryTemplateChange} /> <br /> <span>Query: "{this.state.query}"</span> <SearchForm onSearch={this.onSearch} onReset={this.onReset} query={this.state.queryTemplate} label="Search" queryHelpComponent={( <Button onClick={() => alert('help!')} bsStyle="link"> <Icon name="help" /> </Button>)} useLoadingState /> </div> ); }, }); <SearchFormExample /> ```
Project: Checkmk (Observability and Analysis / Observability)
File: 16048.md

key | value | date | 2024-01-29T07:26:41+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes Azure resource tags are now imported as service labels as well. Each service that is discovered for an Azure resource now holds the resource's tags as service labels. Also, you can now restrict the import of Azure tags via regex or disable the import altogether. This can be done in the rule "Microsoft Azure" via option "Import tags as host/service labels". Note that tags are validated to 1) not hold empty values - empty values are replaced by "true" and 2) not contain colons (":") - colons are replaced by underscores (""). So an Azure resource tag "tag:key":"" will now be shown as "tagkey":"true".
Project: Vector (Observability and Analysis / Observability)
File: nix.md

title: Nix short: Nix weight: 6 {{< info title="Community Maintained" >}} The Vector nixpkg is supported and maintained by the open source community. {{< /info >}} [Nix] is a cross-platform package manager implemented on a functional deployment model where software is installed into unique directories generated through cryptographic hashes, it is also the name of the programming language. This page covers installing and managing Vector through the Nix package repository. {{< warning title="Nix releases are typically delayed" >}} Because Nix releases for Vector must be manually updated, expect delays between official Vector releases and release of the Nix package. New Vector packages for Nix are typically available within a few days. {{< /warning >}} ```shell nix-env --install \ --file https://github.com/NixOS/nixpkgs/archive/master.tar.gz \ --attr vector ``` Vector is an end-to-end observability data pipeline designed to deploy under various roles. You mix and match these roles to create topologies. The intent is to make Vector as flexible as possible, allowing you to fluidly integrate Vector into your infrastructure over time. The deployment section demonstrates common Vector pipelines: {{< jump "/docs/setup/deployment/topologies" >}} {{< tabs default="Upgrade Vector" >}} {{< tab title="Upgrade Vector" >}} ```shell nix-env --upgrade vector \ --file https://github.com/NixOS/nixpkgs/archive/master.tar.gz ``` {{< /tab >}} {{< tab title="Uninstall Vector" >}} ```shell nix-env --uninstall vector ``` {{< /tab >}} {{< /tabs >}} {{< jump "/docs/administration/management" "nix" >}}
Project: Netdata (Observability and Analysis / Observability)
File: semaphores_used.md

This alert monitors the percentage of allocated `System V IPC semaphores`. If you receive this alert, it means that your system is experiencing high IPC semaphore utilization, and a lack of available semaphores can affect application performance. Identify processes using IPC semaphores You can use the `ipcs` command to display information about allocated semaphores. Run the following command to display a list of active semaphores: ``` ipcs -s ``` The output will show the key, ID, owner's UID, permissions, and other related information for each semaphore. Analyze process usage of IPC semaphores You can use `ps` or `top` commands to analyze which processes are using the IPC semaphores. This can help you identify if any process is causing high semaphore usage. ``` ps -eo pid,cmd | grep [process-name] ``` Replace `[process-name]` with the name of the process you suspect is related to the semaphore usage. Adjust semaphore limits if necessary If you determine that the high semaphore usage is a result of an inadequately configured limit, you can update the limits using the following steps: Check the current semaphore limits as mentioned earlier, using the `ipcs -ls` command. To increase the limit to a more appropriate value, edit the `/proc/sys/kernel/sem` file. The second field in the file represents the maximum number of semaphores that can be allocated per array. ``` echo "32000 64000 1024000000 500" > /proc/sys/kernel/sem ``` This command doubles the number of semaphores per array. Make sure to adjust the value according to your system requirements. Monitor semaphore usage after changes After making the necessary changes, continue to monitor semaphore usage to ensure that the changes were effective in resolving the issue. If the issue persists, further investigation may be required to identify the root cause.
Project: Checkmk (Observability and Analysis / Observability)
File: 15330.md

key | value | compatible | yes version | 2.4.0b1 date | 2024-04-10T08:38:00+00:00 level | 1 class | fix component | checks edition | cre Due to fixes introduced with <a href="https://checkmk.com/werk/16234">Werk #16234</a> a failed login to the oracle database was not reported as critical, but the services were going stale. This is now fixed.
Project: Tracetest (Observability and Analysis / Observability)
File: setup-k8s-with-k3d.md

Install k3d: ```sh brew install k3d curl -s https://raw.githubusercontent.com/k3d-io/k3d/main/install.sh | bash ``` Go to `kubetracing` folder and start Jaeger and OTel Collector with `docker compose`: ```sh cd ./kubetracing docker compose up -d ``` Run the following command, replacing the placeholder `PATHTOTHIS_FOLDER` with the current folder absolute path (that can get with `echo $PWD`): ```sh k3d cluster create tracingcluster \ --image=rancher/k3s:v1.27.1-k3s1 \ --volume '[PATHTOTHIS_FOLDER]/config.toml.tmpl:/var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl@server:*' \ --volume '[PATHTOTHIS_FOLDER]/config:/etc/kube-tracing@server:*' \ --k3s-arg '--kube-apiserver-arg=tracing-config-file=/etc/kube-tracing/apiserver-tracing.yaml@server:*' \ --k3s-arg '--kube-apiserver-arg=feature-gates=APIServerTracing=true@server:*' \ --k3s-arg '--kubelet-arg=config=/etc/kube-tracing/kubelet-tracing.yaml@server:*' ``` After setting up the cluster and Jaeger, you should be able to see Kubernetes traces with Jaeger on `http://localhost:16686`. A single test that you can do is to run: ```sh kubectl run -it --rm --restart=Never --image=alpine echo-command -- echo hi ``` Going to Jaeger again on `http://localhost:16686`, choosing the `kubelet` service, operation `syncPod` and adding the tag `k8s.pod=default/echo-command`, we should be able to see spans related to this pod.
Project: Checkmk (Observability and Analysis / Observability)
File: 16388.md

key | value | date | 2024-01-24T09:17:52+00:00 version | 2.3.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes Previously, when you had a host that had no check running, calling the following endpoint would cause a crash. GET /domain-type/host/collections/all?columns=mkinventory This werk addresses this issue by preventing the crash and now returns an appropriate response.
Project: Grafana (Observability and Analysis / Observability)
File: view-notification-errors.md

canonical: https://grafana.com/docs/grafana/latest/alerting/manage-notifications/view-notification-errors/ description: View notification errors and understand why they failed to be sent or were not received keywords: grafana alerting notification errors contact points labels: products: cloud enterprise oss title: View notification errors weight: 900 View notification errors and understand why they failed to be sent or were not received. Note: This feature only works if you are using Grafana Alertmanager. To view notification errors, complete the following steps. Navigate to Alerting -> Contact points. If any contact points are failing, a message at the right-hand corner of the screen alerts the user to the fact that there are errors and how many. Click on the contact point to view the details of errors for each contact point. Error details are displayed if you hover over the Error icon. If a contact point has more than one integration, you see all errors for each of the integrations listed. In the Health column, check the status of the notification. This can be either OK, No attempts, or Error.