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

This alert calculates the number of deadlocks in your PostgreSQL database in the last minute. If you receive this alert, it means that the number of deadlocks has surpassed the warning threshold (10 deadlocks per minute by default). In a PostgreSQL database, a deadlock occurs when two or more transactions are waiting for one another to release a lock, causing a cyclical dependency. As a result, none of these transactions can proceed, and the database server may be unable to process other requests. Identify deadlock occurrences and problematic queries Check the PostgreSQL log for deadlock occurrence messages. You can typically find these logs in `/var/log/postgresql/` or `/pg_log/`. Look for messages like: `DETAIL: Process 12345 waits for ShareLock on transaction 67890; blocked by process 98765.` To find the problematic queries, examine the log entries before the deadlock messages. Most often, these entries will contain the SQL queries that led to the deadlocks. Analyze and optimize the problematic queries Analyze the execution plans of the problematic queries using the `EXPLAIN` command. This can help you identify which parts of the query are causing the deadlock. Optimize the queries by rewriting them or by adding appropriate indices to speed up the processing time. Avoid long-running transactions Long-running transactions increase the chances of deadlocks. Monitor your database for long-running transactions and try to minimize their occurrence. Set sensible lock timeouts to avoid transactions waiting indefinitely for a lock. Review your application logic Inspect your application code for any circular dependencies that could lead to deadlocks. Use advisory locks when possible to minimize lock contention in the database.
Project: Elastic (Observability and Analysis / Observability)
File: mv_first.md

<!-- This is generated by ESQL's AbstractFunctionTestCase. Do no edit it. See ../README.md for how to regenerate it. --> Converts a multivalued expression into a single valued column containing the first value. This is most useful when reading from a function that emits multivalued columns in a known order like <<esql-split>>. The order that <<esql-multivalued-fields, multivalued fields>> are read from underlying storage is not guaranteed. It is frequently ascending, but don't rely on that. If you need the minimum value use <<esql-mv_min>> instead of `MVFIRST`. `MVMIN` has optimizations for sorted values so there isn't a performance benefit to `MV_FIRST`. ``` ROW a="foo;bar;baz" | EVAL firsta = MVFIRST(SPLIT(a, ";")) ```
Project: Grafana (Observability and Analysis / Observability)
File: sign-in-to-grafana.md

description: Learn how to sign in to Grafana labels: products: enterprise oss title: Sign in to Grafana weight: 400 This topic describes how to sign in to Grafana. To sign in to Grafana for the first time, follow these steps: Open your web browser and go to root URL specified in . Unless you have configured Grafana differently, it is set to use `http://localhost:3000` by default. On the signin page, enter `admin` for username and password. Click Sign in. If successful, you will see a prompt to change the password. Click OK on the prompt and change your password. Note: We strongly recommend that you change the default administrator password.
Project: Grafana (Observability and Analysis / Observability)
File: tooltip-options-2.md

title: Tooltip options comments: | There are two tooltip shared files, tooltip-options-1.md and tooltip-options-2.md, to cover the most common combinations of options. Using two shared files ensures that content remains consistent across visualizations that share the same options and users don't have to figure out which options apply to a specific visualization when reading that content. This file is used in the following visualizations: candlestick, time series, trend Tooltip options control the information overlay that appears when you hover over data points in the visualization. When you hover your cursor over the visualization, Grafana can display tooltips. Choose how tooltips behave. Single - The hover tooltip shows only a single series, the one that you are hovering over on the visualization. All - The hover tooltip shows all series in the visualization. Grafana highlights the series that you are hovering over in bold in the series list in the tooltip. Hidden - Do not display the tooltip when you interact with the visualization. Use an override to hide individual series from the tooltip. When you set the Tooltip mode to All, the Values sort order option is displayed. This option controls the order in which values are listed in a tooltip. Choose from the following: None - Grafana automatically sorts the values displayed in a tooltip. Ascending - Values in the tooltip are listed from smallest to largest. Descending - Values in the tooltip are listed from largest to smallest. Set the hover proximity (in pixels) to control how close the cursor must be to a data point to trigger the tooltip to display. Set the maximum height of the tooltip box. The default is 600 pixels.
Project: Flagsmith (Observability and Analysis / Feature Flagging)
File: index.md

title: Authentication description: Customise how your users log in to the Flagsmith dashboard sidebar_label: Overview sidebar_position: 1 :::tip Flagsmith organisations can force their users to always use a single authentication method. Please get in touch to enable this. ::: Flagsmith supports a variety of authentication methods for logging into the dashboard: Email and password GitHub Google Two-factor authentication requires a . Using the following authentication methods requires an : Active Directory (LDAP) Microsoft ADFS Please get in touch in order to integrate with LDAP or ADFS.
Project: Grafana Tempo (Observability and Analysis / Observability)
File: RELEASE.md

Create a PR "Preparing for release X.Y.Z" against master branch Alter CHANGELOG.md from `<placeholder_version> (unreleased)` to `<X.Y.Z> (YYYY-MM-DD)` Use `git log --pretty=format:'- %s -- %an'` as the basis for for changelog entries Update `JaegerClientVersion` in constants.go to `Go-X.Y.Z` Create a release "Release X.Y.Z" on Github Create Tag `vX.Y.Z` Copy CHANGELOG.md into the release notes Create a PR "Back to development" against master branch Add `<next_version> (unreleased)` to CHANGELOG.md Update `JaegerClientVersion` in constants.go to `Go-<next_version>dev`
Project: SkyWalking (Observability and Analysis / Observability)
File: community.md

There are many ways you can connect and contribute to the SkyWalking community. Submit an for an addressed issue or feature implementation plan. Submit a to ask questions, feature proposal and uncertain bug discussion. Mail list: dev@skywalking.apache.org*. Mail to `dev-subscribe@skywalking.apache.org`. Follow the instructions in the reply to subscribe to the mail list. Send `Request to join SkyWalking slack` mail to the mail list(`dev@skywalking.apache.org`), we will invite you in. For Chinese speaker, send `[CN] Request to join SkyWalking slack` mail to the mail list(`dev@skywalking.apache.org`), we will invite you in.
Project: Vector (Observability and Analysis / Observability)
File: remap.md

title: Remap with VRL description: > Modify your observability data as it passes through your topology using (VRL) component_kind: transform featured: true layout: component weight: 1 tags: ["remap", "vrl", "vector remap language", "modify", "component", "transform"] {{/* This doc is generated using: The template in layouts/docs/component.html The relevant CUE data in cue/reference/components/... */}}
Project: Grafana (Observability and Analysis / Observability)
File: release-notes-7-4-2.md

_build: list: false labels: products: cloud enterprise oss title: Release notes for Grafana 7.4.2 <!-- Auto generated by update changelog github action --> Explore: Do not show non queryable data sources in data source picker. , Security: Do not allow an anonymous user to create snapshots. CVE-2021-27358. , CloudWatch: Ensure empty query row errors are not passed to the panel. , DashboardLinks: Fix the links that always cause a full page to reload. , DashboardListPanel: Fix issue with folder picker always showing All and using old form styles. , IPv6: Support host address configured with enclosing square brackets. , Permissions: Fix team and role permissions on folders/dashboards not displayed for non Grafana Admin users. , Postgres: Fix timeGroup macro converts long intervals to invalid numbers when TimescaleDB is enabled. , Prometheus: Fix enabling of disabled queries when editing in dashboard. , QueryEditors: Fix an issue that happens after moving queries then editing would update other queries. , SqlDataSources: Fix the Show Generated SQL button in query editors. , StatPanels: Fix an issue where the palette color scheme is not cleared when loading panel. , Variables: Add the default option back for the data source variable. , Variables: Fix missing empty elements from regex filters. ,
Project: Checkmk (Observability and Analysis / Observability)
File: 15516.md

key | value | date | 2024-04-03T13:42:35+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 2 compatible | yes The checkhttp_ plug-in was previously the only method to monitor certificates out-of-the-box with Checkmk. With the new plug-in Checkmk provides an extensive functionality to monitor certificates. This includes but is not limited to certificates provided by the HTTP protocol. With the new plug-in you can monitor all certificates provided through a TCP connection to encrypt communication. This includes the monitoring of validity times (max and remaining) issuer fields subject fields encryption algorithm alternative names response times public key algorithm and size serial number As with the reworked plugin to monitor web services, you are able to configure multiple services within a single rule.
Project: Cortex (Observability and Analysis / Observability)
File: version-documentation.md

title: "Documentation Versioning" linkTitle: "Documentation Versioning" weight: 1 slug: documentation-versioning Author: Date: March 2020 Status: proposal In Cortex, currently, we are missing versioning of documentation. The idea is to have version documentation just like Prometheus.. Documentation is the main source of information for current contributors and first-timers. A properly versioned documentation will help everyone to have a proper place to look for answers before flagging it in the community. In this proposal, we want to solve this. In particular, we want to: Version specific pages of the documentation Include links to change version (the version must be in the URL) Include the master version and last 3 minor releases. Documentation defaults to the last minor release. Currently, the documentation is residing under the docs/ folder of cortexproject/cortex. It is built by Hugo using the theme . It will have a proper which will enable proper versioning. It has a section in config.toml which will allow us to map URLs with proper versions. We will have to change all the occurrences of older doc links with new links. We will keep `master` version with 3 latest `release` versions. Each release is a minor version expressed as `1.x`. The document would default to latest minor version. From the current doc, the following paths (and all their subpages) should be versioned for now: https://cortexmetrics.io/docs/apis/ https://cortexmetrics.io/docs/configuration/ (moving v1.x Guarantees outside of the tree, because these shouldn't be versioned) The above should be versioned under a single URL path (`/docs/running-cortex/` in the following example, but final prefix is still to be decided). For `master` version we would be able to use the above links via the following path ``` /docs/running-cortex/master/configuration/ /docs/running-cortex/master/api/ ``` And for a minor version like `1.x`: ``` /docs/running-cortex/1.0/configuration/ /docs/running-cortex/1.0/apis/ ``` we'll have versioned documentation only under the /docs/running-cortex/ prefix and, as a starting point, all versioned pages should go there.
Project: Cortex (Observability and Analysis / Observability)
File: VENDORED_CODE.md

Weave Cortex is licensed under the . Some vendored code is under different licenses though, all of them ship the entire license text they are under. The following bits of vendored code are under the MPL-2.0 and can be found in the ./vendor/ directory: https://github.com/hashicorp/go-cleanhttp and https://github.com/hashicorp/consul Pulled in by dependencies are https://github.com/hashicorp/golang-lru https://github.com/hashicorp/serf https://github.com/hashicorp/go-rootcerts is under LGPL-3, that's why we ship the license text in this repository.
Project: Vector (Observability and Analysis / Observability)
File: 2021-10-06-source-codecs.md

date: "2021-10-06" title: "New `decoding` and `framing` options for sources" description: "" authors: ["jszwedko"] pr_numbers: [] release: "0.17.0" hideonrelease_notes: false badges: type: "announcement" Often, when consuming data from a source, the first operation you have to do on it is decode the data from its source representation. To make this easier, we've added new `decoding` options to . For example, if you have a `kafka` source that has JSON-encoded messages, now you can simply add `decoding.codec = "json"` to your source configuration like: ```toml [sources.kafka] type = "kafka" bootstrap_servers = "localhost:9200" topics = ["my_topic"] decoding.codec = "json" ``` This will decode your messages from JSON, thus saving you from an additional `remap` transform. In addition, we've added a new `framing` option to allow configuration for sources that have non-standard framing (for example a custom-delimiter separating messages). For example, if you have an `http` source where the messages are delimited by commas instead of newlines, you can configure this like: ```toml [sources.http] type = "http" address = "0.0.0.0:8080" framing.method = "character_delimited" framing.character_delimited.delimiter = "," ``` To have Vector parse each comma-delimited element as a new message. This can be used with `decoding` option specified above. See the for other framing options.
Project: Vector (Observability and Analysis / Observability)
File: heroku_logs.md

title: Heroku Logplex description: Collect logs from Heroku's , the router responsible for receiving logs from your Heroku apps component_kind: source layout: component tags: ["heroku", "logplex", "component", "source", "logs"] {{/* This doc is generated using: The template in layouts/docs/component.html The relevant CUE data in cue/reference/components/... */}}
Project: Netdata (Observability and Analysis / Observability)
File: hw.intrcnt.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/freebsd.plugin/integrations/hw.intrcnt.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/freebsd.plugin/metadata.yaml" sidebar_label: "hw.intrcnt" learn_status: "Published" learnrelpath: "Collecting Metrics/FreeBSD" 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/freebsd.svg" width="150"/> Plugin: freebsd.plugin Module: hw.intrcnt <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> Get total number of interrupts The plugin calls `sysctl` function to collect necessary data. 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. These metrics show system interrupts frequency. This scope has no labels. Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | system.intr | interrupts | interrupts/s | | system.interrupts | a dimension per interrupt | interrupts/s | There are no alerts configured by default for this integration. No action required. The configuration file name for this integration is `netdata.conf`. Configuration for this specific integration is located in the `[plugin:freebsd]` section within that file. The file format is a modified INI syntax. The general structure is: ```ini [section1] option1 = some value option2 = some other value [section2] option3 = some third value ``` You can edit the configuration file using the `edit-config` script from the Netdata . ```bash cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata sudo ./edit-config netdata.conf ``` <details><summary>Config option</summary> | Name | Description | Default | Required | |:-|:--|:-|:--:| | hw.intrcnt | Enable or disable Interrupts metric. | yes | no | </details> There are no configuration examples.
Project: Grafana (Observability and Analysis / Observability)
File: TODO.md

This is an experiment, if it doesn't work or is disruptive to our workflow we'll revise and adapt. We often identify smaller items to work on while we refactor code or build a new feature. These items may be small enough not to deserve their own GitHub issue and might make a PR either confusing or too large. This document aims to make the threshold of adding such items very small to prevent ideas or small improvements from being forgotten or not recorded because we don't feel like creating a formal GitHub issue. If the item needs more rationale and you feel like a single sentence is inedequate to describe the issue, create a regular GitHub issue. Add a `edit` button to the alert detail page Get rid of "+ Add new" in drop-downs : Let's see if is there a way we can make it work with `<Select allowCustomValue />` Create a shared timings form that can be used in both `EditDefaultPolicyForm.tsx` and `EditNotificationPolicyForm.tsx` Re-enable some skipped tests in `NotificationPolicies.test.tsx` Preferably these should go to GitHub for discoverability, but not all bugs are equal, use your best judgment.
Project: Logstash (Observability and Analysis / Observability)
File: PULL_REQUEST_TEMPLATE.md

<!-- Type of change Please label this PR with the release version and one of the following labels, depending on the scope of your change: bug enhancement breaking change doc --> <!-- Add content to appear in , or add [rn:skip] to leave this PR out of release notes --> <!-- Mandatory Explain here the changes you made on the PR. Please explain the WHAT: patterns used, algorithms implemented, design architecture, message processing, etc. Example: Expose 'xpack.monitoring.elasticsearch.proxy' in the docker environment variables and update logstash.yml to surface this config option. This commit exposes the 'xpack.monitoring.elasticsearch.proxy' variable in the docker by adding it in env2yaml.go, which translates from being an environment variable to a proper yaml config. Additionally, this PR exposes this setting for both xpack monitoring & management to the logstash.yml file. --> <!-- Mandatory Explain here the WHY or the IMPACT to the user, or the rationale/motivation for the changes. Example: This PR fixes an issue that was preventing the docker image from using the proxy setting when sending xpack monitoring information. and/or This PR now allows the user to define the xpack monitoring proxy setting in the docker container. --> <!-- Mandatory Add a checklist of things that are required to be reviewed in order to have the PR approved List here all the items you have verified BEFORE sending this PR. Please DO NOT remove any item, striking through those that do not apply. (Just in case, strikethrough uses two tildes. Scratch this.) --> [ ] My code follows the style guidelines of this project [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] I have made corresponding change to the default configuration files (and/or docker env variables) [ ] I have added tests that prove my fix is effective or that my feature works <!-- Recommended Add a checklist of things that are required to be reviewed in order to have the PR approved --> [ ] <!-- Recommended Explain here how this PR will be tested by the reviewer: commands, dependencies, steps, etc. --> <!-- Recommended Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it. Closes #123 Relates #123 Requires #123 Superseeds #123 --> <!-- Recommended Explain here the different behaviors that this PR introduces or modifies in this project, user roles, environment configuration, etc. If you are familiar with Gherkin test scenarios, we recommend its usage: https://cucumber.io/docs/gherkin/reference/ --> <!-- Optional Add here screenshots about how the project will be changed after the PR is applied. They could be related to web pages, terminal, etc, or any other image you consider important to be shared with the team. --> <!-- Recommended Paste here output logs discovered while creating this PR, such as stack traces or integration logs, or any other output you consider important to be shared with the team. -->
Project: PowerfulSeal (Observability and Analysis / Chaos Engineering)
File: DCO.md

Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or The contribution was provided directly to me by some other person who certified (1), (2) or (3) and I have not modified it. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.