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

title: "Enumeration: DefaultDetailsViewSection" linkTitle: "DefaultDetailsViewSection" slug: "plugin_registry.DefaultDetailsViewSection" .DefaultDetailsViewSection BACK\_LINK = `"BACK_LINK"` _ CHILDREN = `"CHILDREN"` _ ERROR = `"ERROR"` _ EVENTS = `"EVENTS"` _ LOADING = `"LOADING"` _ MAIN\_HEADER = `"MAIN_HEADER"` _ METADATA = `"METADATA"`
Project: Grafana (Observability and Analysis / Observability)
File: bind-net-capabilities.md

labels: products: enterprise oss title: Serving Grafana on a port < 1024 If you are using `systemd` and want to start Grafana on a port that is lower than 1024, you must add a `systemd` unit override. Run the following command to create an override file in your configured editor. ```bash sudo systemctl edit grafana-server.service ``` Add the following additional settings to grant the `CAPNETBIND_SERVICE` capability. To learn more about capabilities, refer to . ``` [Service] CapabilityBoundingSet=CAPNETBIND_SERVICE AmbientCapabilities=CAPNETBIND_SERVICE PrivateUsers=false ```
Project: OpenTelemetry (Observability and Analysis / Observability)
File: how-meeting-recordings-upload-works.md

Videos are being recorded using one of used by OpenTelemetry. OpenTelemetry zoom accounts are paid for and owned by CNCF. All meetings are configured for automatic recording start. No host present necessary. Once meeting is concluded, all participants need to leave the meeting room so the recording will be uploaded to zoom cloud. Every recorded meeting (of length 1 minute or longer) is picked up by (https://zapier.com). Zapier is configured to automatically post links of the Zoom cloud recordings (along with the meeting name, start time and duration) to a . It typically takes an hour for the video to be processed by Zapier. Post the , provide the following information: meeting name (e.g. Java SIG) exact datetime with the timezone of the meeting zoom link used duration (as you remember it), approx 30 min, approx 1 hour, etc. any details like meeting was back to back with other meeting and people joined for the next meeting before this one concluded. Or meeting had some strange accounts joining and zoom bombing, etc. Find the zoom account corresponding to the meeting link. Mapping from static rooms to the account may be found in the zoom bombing document referred from . If non OpenTelemetry zoom account was used, there will be no recording available. Please contact the owner of the zoom account linked from the event. In the zoom account, check if the meeting recording present. If recording is there, it is a Zapier integration issue. If recording is missing in zoom account, check the meeting room settings. Make sure that automatic meeting recording is enabled. If setting is set, likely the meeting recording was stopped using the host key and the recording doesn't exist.
Project: GO Feature Flag (Observability and Analysis / Feature Flagging)
File: ofrep.md

Note that this a work in progress and the protocol is subject to change. OpenFeature Remote Flag Evaluation Protocol is an API specification for feature flagging that allows the use of generic providers to connect to any feature flag management systems that supports the protocol. Currently, the protocol is in the early stages of development and is not yet ready for production use, but GO Feature Flag is supporting the protocol and is the first implementation of the protocol. We are part of the leading team in the protocol, and we try to follow the specification during the early stages of the protocol to allow people to try it and be able to develop the providers. The OFREP implementation is part of the GO Feature Flag Relay Proxy. We have a new API endpoints `/ofrep/v1/evaluate/flags/{key}` and `/ofrep/v1/evaluate/flags` that you can use to test the protocol. You just have to start the GO Feature Flag Relay Proxy (starting from version `v1.24.0`) and use the API to evaluate your flags. For this, follow the instruction on how to use the relay-proxy . ```shell curl https://gist.githubusercontent.com/thomaspoignant/181a067291a04bd1fbb55468629625d2/raw/eacfc2ae1036c1cfef669b41ec7b54c119639c0c/goff-proxy.yaml -o goff-proxy.yaml docker run -p 1031:1031 -v $(pwd)/goff-proxy.yaml:/goff/goff-proxy.yaml thomaspoignant/go-feature-flag:latest ``` This will launch a GO Feature Flag Relay Proxy with a configuration file that will retrieve the flags from the test server. Swagger is enabled, so you can directly go to http://localhost:1031/swagger/index.html to test the OFREP endpoints (the API Key to use is `apikey1`).
Project: Sentry (Observability and Analysis / Observability)
File: snuba_consumer.md

```json { "type": "replay_event", "start_time": 1678478346.735299, "replay_id": "e5e062bf2e1d4afd96fd2f90b6770431", "project_id": 1, "retention_days": 30, "payload": { "type": "replay_event", "replay_id": "e5e062bf2e1d4afd96fd2f90b6770431", "replay_type": "session", "segment_id": 0, "event_hash": "8bea4461d8b944f393c15a3cb1c4169a", "urls": ["https:://www.sentry.io", "https:://www.sentry.io/login"], "is_archived": false, "trace_ids": ["36e980a9c6024cde9f5d089f15b83b5f", "8bea4461d8b944f393c15a3cb1c4169a"], "error_ids": ["36e980a9c6024cde9f5d089f15b83b5f"], "dist": "", "platform": "javascript", "timestamp": 1678478346, "replaystarttimestamp": 1678478346, "environment": "prod", "release": "34a554c14b68285d8a8eb6c5c4c56dfc1db9a83a", "user": { "id": "101", "username": "sentaur", "email": "sentaur@sentry.io", "ip_address": "127.0.0.1" }, "sdk": { "name": "sentry.javascript", "version": "7.41.0" }, "tags": { "customtag": "is_set", "transaction": "/organizations/:orgId/issues/" }, "contexts": { "trace": { "op": "pageload", "span_id": "affa5649681a1eeb", "trace_id": "23eda6cd4b174ef8a51f0096df3bfdd1" }, "replay": { "errorsamplerate": 0.5, "sessionsamplerate": 0.5 }, "os": { "name": "iOS", "version": "16.2" }, "browser": { "name": "Firefox", "version": "110.0" }, "device": { "name": "iPhone 11", "brand": "Apple", "family": "iPhone", "model": "iPhone" } }, "request": { "url": "https:://www.sentry.io", "headers": { "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/110.0" } } } } ``` ```json { "type": "replay_event", "start_time": 1678478346.735299, "replay_id": "e5e062bf2e1d4afd96fd2f90b6770431", "project_id": 1, "retention_days": 30, "payload": { "type": "replay_actions", "replay_id": "e5e062bf2e1d4afd96fd2f90b6770431", "segment_id": 0, "actions": [ { "dom_action": "click", "dom_element": "div", "dom_id": "id", "dom_classes": ["class1", "class2"], "domarialabel": "test", "domariarole": "aria-button", "dom_role": "button", "domtextcontent": "text", "domnodeid": 59, "timestamp": 1678478346, "event_hash": "df3c3aa2daae465e89f1169e49139827" } ] } } ```
Project: Cortex (Observability and Analysis / Observability)
File: TESTS.md

`go test` is used for testing. A running PostgreSQL server is required, with the ability to log in. The database to connect to test with is "pqgotest," on "localhost" but these can be overridden using [environment variables](https://www.postgresql.org/docs/9.3/static/libpq-envars.html). Example: PGHOST=/run/postgresql go test A benchmark suite can be run as part of the tests: go test -bench . Run a postgres container: ``` docker run --expose 5432:5432 postgres ``` Run tests: ``` PGHOST=localhost PGPORT=5432 PGUSER=postgres PGSSLMODE=disable PGDATABASE=postgres go test ```
Project: VictoriaMetrics (Observability and Analysis / Observability)
File: FAQ.md

sort: 9 weight: 9 title: FAQ menu: docs: parent: "operator" weight: 9 identifier: "operator-faq" aliases: /operator/FAQ.html /operator/faq.html You can read about vmoperator monitoring in . With Helm chart deployment: Update the PVCs manually Run `kubectl delete statefulset --cascade=orphan {vmstorage-sts}` which will delete the sts but keep the pods Update helm chart with the new storage class in the volumeClaimTemplate Run the helm chart to recreate the sts with the updated value With Operator deployment: Update the PVCs manually Run `kubectl delete vmcluster --cascade=orphan {cluster-name}` Run `kubectl delete statefulset --cascade=orphan {vmstorage-sts}` Update VMCluster spec to use new storage class Apply cluster configuration You can use `VM_CONTAINERREGISTRY` parameter for operator: See details about tuning . See here. You can read about backups: for `VMSingle`: for `VMCluster`: You can read about migration from prometheus operator on . You can read about it on . You can read about it in following sections of "Migration from prometheus-operator" docs: You can read about needed permissions for operator in . See . In addition, you can use or . that's where we describe default version of VictoriaMetrics components. See this document for details: . See this example in operator repository: https://github.com/VictoriaMetrics/operator/blob/master/config/examples/vmagent-istio.yaml Operator tested at kubernetes versions from 1.16 to 1.27.
Project: Grafana Loki (Observability and Analysis / Observability)
File: backport-commits.md

title: Backport commits description: Backport commits Any PRs or commits not on the release branch that you want to include in the release must be backported to the release branch. Determine the . If the release branch already has all the code changes on it, skip this step. Pick a PR that you want to backport to `release-VERSION_PREFIX` branch. Add two labels to the PR. First, one of the `product-approved`, `type/doc` or `type/bug` appropriately. This is to make sure the PRs that are backported are done with right intention. Second `backport release-VERSION_PREFIX` label. Now CI should automatically create backport PR to the correct release branch. Example {{% admonition type="note" %}} CI automation can fail sometimes if there are some merge conflicts in cherry picking the commits. In those cases, the original PR where you added the label should have additional comment explaining how to backport it manually. {{% /admonition %}} {{% admonition type="note" %}} The CI job that helps with backporting PR is `.github/workflows/backport.yml`. Useful for debugging purposes. {{% /admonition %}} Repeat the above steps for any PRs that need to be backported. If backporting a release PR, make sure you remove any `autorelease: pending` or `autorelease: tagged` labels before merging the backport PR. By default our backport action brings over all labels, but these labels are reserved for the release workflow and will cause future pipelines to fail if left of backport PRs.
Project: Falcon (Observability and Analysis / Observability)
File: 2017-01-01-user_list.md

category: User apiurl: '/api/v1/user/users' title: 'User List' type: 'GET' sample_doc: 'user.html' layout: default Required ```Status: 200``` ```[ { "id": 1, "name": "root", "cnname": "", "email": "", "phone": "", "im": "", "qq": "904394234239", "role": 2 }, { "id": 32, "name": "owltester", "cnname": "", "email": "root123@cepave.com", "phone": "99999999999", "im": "44955834958", "qq": "904394234239", "role": 0 } ]``` For more example, see the . For errors responses, see the .
Project: M3 (Observability and Analysis / Observability)
File: prometheus_aggregation.md

title: "Prometheus: Aggregation for Prometheus, Thanos or other remote write storage with M3" weight: 2 This document is a getting started guide to using M3 Coordinator or both M3 Coordinator and M3 Aggregator roles to aggregate metrics for a compatible Prometheus remote write storage backend. What's required is any Prometheus storage backend that supports the [Prometheus Remote write protocol](https://docs.google.com/document/d/1LPhVRSFkGNSuU1fBd81ulhsCPR4hkSZyyBj1SZ8fWOM/). To test out a full end-to-end example you can clone the M3 repository and use the corresponding guide for the . Start by downloading the . Update the endpoints with your Prometheus Remote Write compatible storage setup. You should endup with config similar to: ```yaml backend: prom-remote prometheusRemoteBackend: endpoints: name: unaggregated address: "http://prometheus-raw:9090/api/v1/write" name: aggregated address: "http://prometheus-agg:9090/api/v1/write" storagePolicy: retention: 1440h resolution: 5m name: historical address: "http://prometheus-hist:9090/api/v1/write" storagePolicy: retention: 8760h resolution: 1h downsample: all: false ``` Refer to the for more details on more advanced deployment options.
Project: GO Feature Flag (Observability and Analysis / Feature Flagging)
File: relay_proxy_endpoints.md

sidebar_position: 60 description: Description of the available endpoints in the relay proxy. The most updated documentation about the relay proxy endpoints is the Swagger docs (see to see how to access to the documentation). Swagger endpoint is serving a to test your REST endpoints. By default, this endpoint is not exposed, you need to have this configuration in your relay proxy configuration file: ```yaml enableSwagger: true host: my-proxy-domain.com # the DNS to access the proxy ``` When enabled, you can go to the `/swagger/` endpoint with your browser, and you will have access to the Swagger UI for the relay proxy. If you don't want to install the relay proxy to check the endpoints, you can go to this directly.
Project: HertzBeat (Observability and Analysis / Observability)
File: alert_discord.md

id: alert_discord title: Alert Discord Bot Notifications sidebar_label: Alert Discord bot notification keywords: [open source monitoring tool, open source alerter, open source Discord bot notification] Send an alarm message after the threshold is triggered, and notify the recipient through the Discord robot. Visit to create an application Create a robot under the application and get the robot Token Authorize the bot to the chat server Authorize the robot under the OAuth2 menu, select `bot` for `SCOPES`, `BOT PERMISSIONS` select `Send Messages` Obtain the URL generated at the bottom, and the browser accesses this URL to officially authorize the robot, that is, to set which chat server the robot will join. Check if your chat server has joined robot members Personal Settings -> Advanced Settings -> Enable Developer Mode Get channel Channel ID Right-click the chat channel you want to send the robot message to, click the COPY ID button to get the Channel ID [Alarm notification] -> [Add recipient] -> [Select Discord robot notification method] -> [Set robot Token and ChannelId] -> [OK] Configure the associated alarm notification strategy [Add notification strategy] -> [Associate the recipient just set] -> [OK] Note Adding a new recipient does not mean that it has taken effect and can receive alarm information. It is also necessary to configure the associated alarm notification strategy, that is, specify which messages are sent to which recipients. Discord doesn't receive bot alert notifications Please check whether the alarm information has been triggered in the alarm center Please check whether the robot Token and ChannelId are configured correctly, and whether the alarm policy association has been configured Please check whether the bot is properly authorized by the Discord chat server Other questions can be fed back through the communication group ISSUE!
Project: Grafana (Observability and Analysis / Observability)
File: release-notes-8-3-5.md

_build: list: false labels: products: cloud enterprise oss title: Release notes for Grafana 8.3.5 Security: Fixes CVE-2022-21702. For more information, see our Security: Fixes CVE-2022-21703. For more information, see our Security: Fixes CVE-2022-21713. For more information, see our
Project: Checkmk (Observability and Analysis / Observability)
File: 15199.md

key | value | date | 2024-04-17T10:08:23+00:00 version | 2.4.0b1 class | security edition | cre component | omd level | 1 compatible | yes OpenSSL was updated to version 3.0.13. OpenSSL 3 uses requirements regarding allowed configurations, such as allowed ciphers, renegotiation, and so on. In some scenarios, this can break monitoring for hosts with TLS configurations that are no longer considered secure. We have published a blog post to help you mitigate these issues, should they affect you: https://checkmk.com/blog/how-monitor-servers-broken-tls-checkmk. To aid automated scanning we assign a CVSS score of 0.0 (None) (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N).
Project: Checkmk (Observability and Analysis / Observability)
File: 16170.md

key | value | compatible | yes version | 2.4.0b1 date | 2024-02-07T09:54:40+00:00 level | 1 class | fix component | checks edition | cre SNMP caching didn't take contexts in consideration when storing OID data. This led to the same result being reported for the OID in different sections even if sections use different contexts. Now, SNMP caching stores fetched OID data for every group of contexts it was called with.
Project: Checkmk (Observability and Analysis / Observability)
File: 15319.md

key | value | compatible | yes version | 2.3.0b1 date | 2024-01-24T09:50:01+00:00 level | 1 class | fix component | checks edition | cre Previously the path was prefixed with a space, so the spool files where saved in: <code>/omd/sites/cmk220d/var/check_mk/core/ /omd/sites/cmk220d/var/mkeventd/spool</code>
Project: Grafana (Observability and Analysis / Observability)
File: 2-accessibility.md

name: Accessibility issue about: Help make Grafana be better at keyboard navigation, screen-readable and accessible to all. labels: 'type: accessibility' <!-- Please only use this template for submitting accessibility issues. This is a new feature area for Grafana that we want to improve. We have long way to go to really improve accessibility and would like your help to know where to start. --> Steps to reproduce: Actual Result: Expected Result Relevant WCAG Criteria: Environment: Grafana version: Data source type & version: User OS & Browser: Others:
Project: Grafana Tempo (Observability and Analysis / Observability)
File: CHANGES.md

v2/callctx:* add new callctx package () () v2:* add BuildHeaders and InsertMetadataIntoOutgoingContext to header () () v2:* add GoVersion package variable () () v2:* handle space in non-devel go version () () update dependencies () () v2:* drop cloud lro test dep () (), refs apierror:* add method to return HTTP status code conditionally () (), refs add ref to usage with clients () (), refs v2:* add WithTimeout option () () v2/apierror:* return Unknown GRPCStatus when err source is HTTP () (), refs update google.golang.org/api to latest () () v2/apierror:* add apierror.FromWrappingError () () v2:* copy DetermineContentType functionality () () v2:* resolve bad genproto pseudoversion in go.mod () () add ExtractProtoMessage to apierror () () v2:* add OnHTTPCodes CallOption () () v2/apierror:* use errors.As in FromError () () v2:* bump release-please processing () ()
Project: Spring Cloud Sleuth (Observability and Analysis / Observability)
File: ISSUE_TEMPLATE.md

<!-- Thanks for raising a Spring Cloud issue. What sort of issue are you raising? Question Please ask questions about how to use something, or to understand why something isn't working as you expect it to, on Stack Overflow using the spring-cloud tag. Bug report Please provide details of the problem, including the version of Spring Cloud that you are using. If possible, please provide a test case or sample application that reproduces the problem. This makes it much easier for us to diagnose the problem and to verify that we have fixed it. Enhancement Please start by describing the problem that you are trying to solve. There may already be a solution, or there may be a way to solve it that you hadn't considered. -->
Project: Netdata (Observability and Analysis / Observability)
File: btrfs_system.md

The `btrfs_system` alert monitors the percentage of used Btrfs system space. If you receive this alert, it means that your Btrfs system space usage has reached a critical level and could potentially cause issues on your system. Important: Data is priceless. Before you perform any action, make sure that you have taken any necessary backup steps. Netdata is not liable for any loss or corruption of any data, database, or software. Add more physical space Adding a new disk always depends on your infrastructure, disk RAID configuration, encryption, etc. To add a new disk to a filesystem: Determine which disk you want to add and in which path: ``` root@netdata~ # btrfs device add -f /dev/<new_disk> <path> ``` If you get an error that the drive is already mounted, you might have to unmount: ``` root@netdata~ # btrfs device add -f /dev/<new_disk> <path> ``` See the newly added disk: ``` root@netdata~ # btrfs filesystem show Label: none uuid: d6b9d7bc-5978-2677-ac2e-0e68204b2c7b Total devices 2 FS bytes used 192.00KiB devid 1 size 10.01GiB used 536.00MiB path /dev/sda1 devid 2 size 10.01GiB used 0.00B path /dev/sdb ``` Balance the system to make use of the new drive: ``` root@netdata~ # btrfs filesystem balance <path> ``` Delete snapshots You can identify and delete snapshots that you no longer need. Find the snapshots for a specific path: ``` root@netdata~ # sudo btrfs subvolume list -s <path> ``` Delete a snapshot that you do not need any more: ``` root@netdata~ # btrfs subvolume delete <path>/@some_dir-snapshot-test ``` Enable a compression mechanism Apply compression to existing files. This command will re-compress the `mount/point` path, with the `zstd` compression algorithm: ``` root@netdata # btrfs filesystem defragment -r -v -czstd /mount/point ``` Enable a deduplication mechanism Tools dedicated to deduplicate a Btrfs formatted partition include duperemove, bees, and dduper. These projects are 3rd party, and it is strongly suggested that you check their status before you decide to use them. - Perform a balance Especially in a Btrfs with multiple disks, data/metadata might be unevenly allocated into the disks. ``` root@netdata # btrfs balance start -musage=10 -dusage=10 -susage=50 /mount/point ``` > This command will attempt to relocate data/metdata/system-data in empty or near-empty chunks (at most X% used, in this example), allowing the space to be reclaimed and reassigned between data and metadata. If the balance command ends with "Done, had to relocate 0 out of XX chunks", then you need to increase the "dusage/musage" percentage parameter until at least some chunks are relocated.
Project: Checkmk (Observability and Analysis / Observability)
File: 16337.md

key | value | date | 2024-02-12T12:30:17+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | no When multiple graphics cards were present, the command 'lscpi -s: Invalid bus number'. This left the section blank and no cards were detected in the HW/SW inventory. This fix may cause new graphics cards to appear in the HW/SW inventory. For the fix to take effect, the user will need to re-deploy the plugin.
Project: Checkmk (Observability and Analysis / Observability)
File: 16277.md

key | value | date | 2023-12-23T14:52:41+00:00 version | 2.3.0b1 class | fix edition | cre component | checks level | 1 compatible | no This affects all users that had rules for "Main memory usage of simple devices" configured. To clean up inconsistencies that the new APIs no longer tolerate, we had to split the ruleset into two. We renamed "Main memory usage of simple devices" to "Main memory usage of simple devices with multiple services" and added a new ruleset "Main memory usage of simple devices with single services". The required new rules are created automatically during upgrade, but we advise users to check if they have rules that are not needed anymore. The plugins using the new ruleset are Check Point Firewalls: Memory Usage (`checkpoint_memory`) HPE Procurve Switches: Memory Usage (`hpprocurvemem`) UCD SNMP Daemon: Memory Check (`ucd_mem`)