cwielenb/CNCF-Dataset huggingface dataset:
Project: Grafana (Observability and Analysis / Observability)
File: release-notes-8-1-0.md

_build: list: false labels: products: cloud enterprise oss title: Release notes for Grafana 8.1.0 <!-- Auto generated by update changelog github action --> Alerting: Deduplicate receivers during migration. , ColorPicker: Display colors as RGBA. , Encryption: Add support for multiple encryption algorithms (aes-gcm). (Enterprise) Select: Make portalling the menu opt-in, but opt-in everywhere. , TeamSync: Batch team synchronization. (Enterprise) TimeRangePicker: Improve accessibility. , Annotations: Correct annotations that are displayed upon page refresh. , Annotations: Fix Enabled button that disappeared from Grafana v8.0.6. , Annotations: Fix data source template variable that was not available for annotations. , AzureMonitor: Fix annotations query editor that does not load. , Geomap: Fix scale calculations. , GraphNG: Fix y-axis autosizing. , Live: Display stream rate and fix duplicate channels in list response. , Loki: Update labels in log browser when time range changes. , Loki: Update labels in log browser when time range changes in dashboard. , NGAlert: Send resolve signal to alertmanager on alerting -> Normal. , PasswordField: Prevent a password from being displayed when you click the Enter button. , Renderer: Remove debug.log file when Grafana is stopped. , Security: Update dependencies to fix CVE-2021-36222. ,
Project: Weave Scope (Observability and Analysis / Observability)
File: RELEASE.md

The `yaml` Project is released on an as-needed basis. The process is as follows: An issue is proposing a new release with a changelog since the last release All must LGTM this release An OWNER runs `git tag -s $VERSION` and inserts the changelog and pushes the tag with `git push $VERSION` The release issue is closed An announcement email is sent to `kubernetes-dev@googlegroups.com` with the subject `[ANNOUNCE] kubernetes-template-project $VERSION is released`
Project: Grafana Loki (Observability and Analysis / Observability)
File: v2-6.md

title: V2.6 description: Version 2.6 release notes weight: 66 Grafana Labs is excited to announce the release of Loki 2.6. Here's a summary of new enhancements and important fixes. Query multiple tenants at once. We've introduced cross-tenant query federation, which allows you to issue one query to multiple tenants and get a single, consolidated result. This is great for scenarios where you need a global view of logs within your multi-tenant cluster. For more information on how to enable this feature, see . Filter out and delete certain log lines from query results. This is particularly useful in cases where users may accidentally write sensitive information to Loki that they do not want exposed. Users craft a LogQL query that selects the specific lines they're interested in, and then can choose to either filter out those lines from query results, or permanently delete them from Loki's storage. For more information, see . Improved query performance on instant queries. Loki now splits instant queries with a large time range (for example, `sum(rate({app="foo"}[6h]))`) into several smaller sub-queries and executes them in parallel. Users don't need to take any action to enjoy this performance improvement; however, they can adjust the number of sub-queries generated by modifying the `splitqueriesby_interval` configuration parameter, which currently defaults to `30m`. Support Baidu AI Cloud as a storage backend. Loki users can now use Baidu Object Storage (BOS) as their storage backend. See for details. For a full list of all changes, look at the . As always, please read the before upgrading Loki. v2.6.1 includes following fixes: JordanRushing: Updated the versions of and to allow configuring cluster labels for memberlist. Cluster labels prevent mixing the members between two consistent hash rings of separate applications that are run on the same Kubernetes cluster. MasslessParticle Fixed an HTTP connection leak between the querier and the compactor when the log entry deletion feature is enabled. MasslessParticle Fixed noisy error messages when the log entry deletion feature is disabled for a tenant V2.6.0 fixes numerous bugs. The has the complete list. A summary of some of the more important fixes: Fixed a scenario where live tailing of logs could cause unbounded ingester memory growth. Fixed a bug in Loki's push request parser that allowed users to send arbitrary non-string data as a log line. We now test that the pushed values are valid strings and return an error if values are not valid strings. Fixed incorrect deduplication logic for cases where multiple log entries with the same timestamp exist. Fixed a bug in the where the `instanceinterfacenames` setting was getting overwritten by the default ring configuration.
Project: Grafana (Observability and Analysis / Observability)
File: release-notes-9-0-9.md

aliases: [] hide_menu: true labels: products: cloud enterprise oss title: Release notes for Grafana 9.0.9 <!-- Auto generated by update changelog github action --> AngularPanels: Fixing changing angular panel options not taking having affect when coming back from panel edit. , AuthNZ: Security fixes for CVE-2022-35957 and CVE-2022-36062. , FIX: RBAC prevents deleting empty snapshots (#54385). ,
Project: Netdata (Observability and Analysis / Observability)
File: megacli_bbu_cycle_count.md

The `megaclibbucycle_count` alert is related to the battery backup unit (BBU) of your MegaCLI controller. This alert is triggered when the average number of full recharge cycles during the BBU's lifetime exceeds a predefined threshold. High numbers of charge cycles can affect the battery's relative capacity. A warning state is triggered when the number of charge cycles is greater than 100, and a critical state is triggered when the number of charge cycles is greater than 500. Caution: Before performing any troubleshooting steps, ensure that you have taken the necessary backup measures to protect your data. Netdata is not liable for any data loss or corruption. Gather information about the battery units for all of your adapters: ``` megacli -AdpBbuCmd -GetBbuStatus -aALL ``` Perform a battery check on the BBU with a low relative charge. Before taking any action, consult the manual's: ``` megacli -AdpBbuCmd -BbuLearn -aX // X is the adapter's number ``` If necessary, replace the battery in question.
Project: SkyWalking (Observability and Analysis / Observability)
File: changes-8.0.0.md

v3 protocol is added and implemented. All previous releases are incompatible with 8.x releases. Service, Instance, Endpoint register mechanism and inventory storage entities are removed. New GraphQL query protocol is provided, the legacy protocol is still supported(plan to remove at the end of this year). Support Prometheus network protocol. Metrics in Prometheus format could be transferred into SkyWalking. Python agent provided. All inventory caches have been removed. Apache ShardingSphere(4.1.0, 4.1.1) agent plugin provided. Add MariaDB plugin. Vert.x plugin enhancement. More cases are covered. Support v3 extension header. Fix ElasticSearch 5.x plugin TransportClient error. Support Correlation protocol v1. Fix Finagle plugin bug, in processing Noop Span. Make `CommandService` daemon to avoid blocking target application shutting down gracefully. Refactor spring cloud gateway plugin and support tracing spring cloud gateway 2.2.x Support meter system for Prometheus adoption. In future releases, we will add native meter APIs and MicroMeter(Sleuth) system. Support endpoint grouping. Add SuperDataSet* annotation for storage entity. Add superDatasetIndexShardsFactor* in the ElasticSearch storage, to provide more shards for @SuperDataSet annotated entites. Typically TraceSegment. Support alarm settings for relationship of service, instance, and endpoint level metrics. Support alarm settings for database(conjecture node in tracing scenario). Data Model could be added in the runtime, don't depend on the bootstrap sequence anymore. Reduce the memory cost, due to no inventory caches. No buffer files in tracing and service mesh cases. New ReadWriteSafe cache implementation. Simplify codes. Provide default way for metrics query, even the metrics doesn't exist. New GraphQL query protocol is provided. Support the metrics type query. Set up length rule of service, instance, and endpoint. Adjust the default jks for ElasticSearch to empty. Fix Apdex function integer overflow issue. Fix profile storage issue. Fix TTL issue. Fix H2 column type bug. Add JRE 8-14 test for the backend. UI dashboard is 100% configurable to adopt new metrics definited in the backend. Add v8 upgrade document. Make the coverage accurate including UT and e2e tests. Add miss doc about collecting parameters in the profiled traces. Fix SQL Injection vulnerability in H2/MySQL implementation. Upgrade Nacos to avoid the FastJson CVE in high frequency. Upgrade jasckson-databind to 2.9.10. All issues and pull requests are
Project: Checkmk (Observability and Analysis / Observability)
File: 16375.md

key | value | date | 2024-01-15T13:59:03+00:00 version | 2.3.0b1 class | fix edition | cre component | checks level | 1 compatible | yes The ruleset "Check Email" recently featured stricter validation. As a result, macros (like `$HOSTNAME$`) could not be used anymore. This was partially compensated for in , but this was still too restrictive. Users can now configure validated host adresses or unvalidated strings containing macros.
Project: Grafana (Observability and Analysis / Observability)
File: other.md

aliases: ../../http_api/other/ canonical: /docs/grafana/latest/developers/http_api/other/ description: Grafana Other HTTP API keywords: grafana http documentation api other labels: products: enterprise oss title: 'Other HTTP API ' `GET /api/frontend/settings` Example Request: ```http GET /api/frontend/settings HTTP/1.1 Accept: application/json Content-Type: application/json Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk ``` Example Response: ```http HTTP/1.1 200 Content-Type: application/json { "allowOrgCreate":true, "appSubUrl":"", "buildInfo":{ "buildstamp":xxxxxx, "commit":"vyyyy", "version":"zzzzz" }, "datasources":{ "datasourcename":{ "index":"grafana-dash", "meta":{ "annotations":true, "module":"plugins/datasource/grafana/datasource", "name":"Grafana", "partials":{ "annotations":"app/plugins/datasource/grafana/partials/annotations.editor.html", "config":"app/plugins/datasource/grafana/partials/config.html" }, "pluginType":"datasource", "serviceName":"Grafana", "type":"grafanasearch" } } }, "defaultDatasource": "Grafana" } ``` `GET /api/login/ping` Example Request: ```http GET /api/login/ping HTTP/1.1 Accept: application/json Content-Type: application/json Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk ``` Example Response: ```http HTTP/1.1 200 Content-Type: application/json {"message": "Logged in"} ``` `GET /api/health` Example Request ```http GET /api/health Accept: application/json ``` Example Response: ```http HTTP/1.1 200 OK { "commit": "087143285", "database": "ok", "version": "5.1.3" } ```
Project: VictoriaMetrics (Observability and Analysis / Observability)
File: vmstaticscrape.md

sort: 14 weight: 14 title: VMStaticScrape menu: docs: parent: "operator-custom-resources" weight: 14 aliases: /operator/resources/vmstaticscrape.html The `VMStaticScrape` CRD provides mechanism for scraping metrics from static targets, configured by CRD targets. `VMStaticScrape` object generates part of configuration with . It has various options for scraping configuration of target (with basic auth,tls access, by specific port name etc.). By specifying configuration at CRD, operator generates config for and syncs it. It's useful for external targets management, when service-discovery is not available. `VMAgent` `staticScrapeSelector` must match `VMStaticScrape` labels. More information about selectors you can find in . You can see the full actual specification of the `VMStaticScrape` resource in the . Also, you can check out the section. ```yaml apiVersion: operator.victoriametrics.com/v1beta1 kind: VMStaticScrape metadata: name: vmstaticscrape-sample spec: jobName: static targetEndpoints: targets: ["192.168.0.1:9100", "196.168.0.50:9100"] labels: env: dev project: operator ```
Project: Vector (Observability and Analysis / Observability)
File: CODE_OF_CONDUCT.md

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at . All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: Checkmk (Observability and Analysis / Observability)
File: 16386.md

key | value | date | 2024-01-19T11:43:30+00:00 version | 2.3.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes Previously when creating or updating an notification rule via the rest-api, the matching conditions for service levels and time periods were being saved to file with an incorrect key. This werk addresses this issue by correcting the keys being saved.
Project: Logging Operator (Kube Logging) (Observability and Analysis / Observability)
File: auth.md

title: Authentication config for syslog-ng outputs weight: 200 generated_file: true GRPC-based outputs use this configuration instead of the simple `tls` field found at most HTTP based destinations. For details, see the documentation of a related syslog-ng destination, for example, . Authentication settings. Only one authentication method can be set. Default: Insecure Application Default Credentials (ADC). Application Layer Transport Security (ALTS) is a simple to use authentication, only available within Googles infrastructure. This is the default method, authentication is disabled (`auth(insecure())`). This option sets various options related to TLS encryption, for example, key/certificate files and trusted CA locations. TLS can be used only with tcp-based transport protocols. For details, see and the .
Project: Grafana Tempo (Observability and Analysis / Observability)
File: consistent_hash_ring.md

title: Tune the consistent hash rings menuTitle: Tune the consistent hash rings description: Optimize the consistent hash rings for Tempo. weight: 40 Tempo uses the implementation from Cortex. By default, the ring is gossiped between all Tempo components. However, it can be configured to use or , if desired. There are four consistent hash rings: distributor, ingester, metrics-generator, and compactor. Each hash ring exists for a distinct reason. Participants: Distributors Used by: Distributors Unless you are running with limits, this ring does not impact Tempo operation. This ring is only used when `global` rate limits are used. The distributors use it to count the other active distributors. Incoming traffic is assumed to be evenly spread across all distributors and (globalratelimit / # of distributors) is used to rate limit locally. Participants: Ingesters Used by: Distributors, Queriers This ring is used by the distributors to load balance traffic into the ingesters. When spans are received the trace id is hashed and they are sent to the appropriate ingesters based on token ownership in the ring. Queriers also use this ring to find the ingesters for querying recent traces. Participants: Metrics-generators Used by: Distributors This ring is used by distributors to load balance traffic to the metrics-generators. When spans are received, the trace ID is hashed, and the traces are sent to the appropriate metrics-generators based on token ownership in the ring. Participants: Compactors Used by: Compactors This ring is used by the compactors to shard compaction jobs. Jobs are hashed into the ring and the owning compactor is the only one allowed to compact a specific set of blocks to prevent race conditions on compaction. Web pages are available at the following endpoints. They show every ring member, their tokens and includes the ability to "Forget" a ring member. "Forgetting" is useful when a ring member leaves the ring without properly shutting down (and therefore leaves its tokens in the ring). Available on: Distributors Path: `/distributor/ring` Unhealthy distributors have little impact but should be forgotten to reduce cost of maintaining the ring . Available on: Distributors Path: `/ingester/ring` Unhealthy ingesters will cause writes to fail. If the ingester is really gone, forget it immediately. Available on: Distributors Path: `/metrics-generator/ring` Unhealthy metrics-generators will cause writes to fail. If the metrics-generator is really gone, forget it immediately. Available on: Compactors Path: `/compactor/ring` Unhealthy compactors will allow the blocklist to grow significantly. If the compactor is really gone, forget it immediately. Ring/Lifecycler configuration control how a component interacts with the ring. Refer to the topic for more details.
Project: Checkmk (Observability and Analysis / Observability)
File: 16341.md

key | value | date | 2024-03-21T15:36:04+00:00 version | 2.3.0b4 class | fix edition | cee component | checks level | 1 compatible | yes When the Robotmk Core MKP is installed, RCC Suites configuration and RCC Profile configuration are not available as they are Enterprise features. Previously, there were scenarios where RCC suites were running even though the Robotmk Core MKP was installed. The Agent Bakery would use previously saved Enterprise configurations without first migrating them to their CoreMode counterparts. This has now been fixed and the licensing mode is checked when the agent is baked. This means the RCC Suites/RCC Profile configuration will be ignored during the bake process. This prevents users from inadvertently relying on a paid feature when CoreMode is enabled.
Project: Grafana Mimir (Observability and Analysis / Observability)
File: about-exemplars.md

aliases: ../../operators-guide/using-exemplars/about-exemplars/ ../../operators-guide/use-exemplars/about-exemplars/ description: Learn about using exemplars in Grafana Mimir to identify high cardinality in time series events. menuTitle: About exemplars title: About Grafana Mimir exemplars weight: 10 An exemplar is a specific trace representative of a repeated pattern of data in a given time interval. It helps you identify higher cardinality metadata from specific events within time series data. To learn more about exemplars and how they can help you isolate and troubleshoot problems with your systems, see . Grafana Mimir includes the ability to store exemplars in-memory. Exemplar storage in Grafana Mimir is implemented similarly to how it is in Prometheus. Exemplars are stored as a fixed size circular buffer that stores exemplars in memory for all series. The property can be used to control the size of the circular buffer by the number of exemplars. For reference, an exemplar with just a `traceID=<jaeger-trace-id>` uses roughly 100 bytes of memory via the in-memory exemplar storage. If the exemplar storage is enabled, Grafana Mimir will also append the exemplars to WAL for local persistence (for WAL duration).
Project: Vector (Observability and Analysis / Observability)
File: apache_metrics.md

title: Apache HTTP server (HTTPD) metrics description: Collect metrics from Apache's server short: Apache Metrics component_kind: source layout: component tags: ["apache", "http", "component", "source", "metrics"] {{/* This doc is generated using: The template in layouts/docs/component.html The relevant CUE data in cue/reference/components/... */}}