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

Teletrace natively supports the standard for incoming traces which allows users to instrument their application in an open-source, community driven and non-vendor locked way, as well as to provide our users a wide range of high-quality instrumentation libraries that should cover most if not all of the tech stack used. Teletrace can be easily installed using our or by using our . Teletrace is using an advanced and modern UI to allow for easy querying and visualization of your traces. Teletrace was designed from the ground up to be extensible through the use of plugins, to avoid coupling our users with a specific storage solution for traces. From our experience we know that managing and scaling database solutions is an extremely hard task, and we want to provide an option to use existing knowledge to manage the storage solution for any given installation. Currently the supported backends are: Elasticsearch (version 8+) SQLite We are working on adding more storage plugins and would happily accept contributions from the community.
Project: Grafana Tempo (Observability and Analysis / Observability)
File: v1-3.md

title: Version 1.3 release notes menuTitle: V1.3 description: Release notes for Grafana Tempo 1.3 weight: 90 The Tempo team is excited to announce the release of Tempo 1.3. Search In addition to the existing search of recent traces, support has been added to search traces in the backend store. Refer to for details. Improve ring functionality The compactor ring automatically forgets about unhealthy ring members. Protect instances from very large traces The ingester keeps track of traces that exceed the configured maximum size, extending protection from very large traces to after the traces are flushed to disk. Expose additional metrics These new metrics are exposed: `tempolimitsoverrides` `tempolimitsdefaults` `tempoingesterlive_traces` `tempodbcompactionoutstanding_blocks` Azure credentials may be set in the environment Instead of setting values in the configuration, environment variables may specify `AZURESTORAGEACCOUNT` and `AZURESTORAGEKEY`. When upgrading to Tempo v1.3, be aware of these breaking changes: : The OpenTelemetry Collector's GRPC receiver's default port changed from 55680 to 4317. : Configuration option `querier.searchmaxresultlimit` is renamed to `queryfrontend.search.maxresultlimit`. Configuration option `querier.searchdefaultresultlimit` is renamed to `queryfrontend.search.defaultresultlimit`. : Removed the deprecated `Push` method from `tempopb.Pusher`. Grafana does not yet support the `tempoBackendSearch` feature toggle to enable searches in the backend datastore. mapno: Fixed a panic that occurred when using etcd as the ring's backend storage. joe-elliott: Fixed an issue which corrupted the start/end time ranges of Tempo searches that targeted ingesters.
Project: Grafana (Observability and Analysis / Observability)
File: release-notes-8-5-6.md

aliases: [] hide_menu: true labels: products: cloud enterprise oss title: Release notes for Grafana 8.5.6 <!-- Auto generated by update changelog github action --> Dashboard: Fixes random scrolling on time range change. , Security: Fixes minor code scanning security warnings in old vendored javascript libs. ,
Project: OpenTelemetry (Observability and Analysis / Observability)
File: config.md

OpenTelemetry specifies code that can operate in a variety of ways based on the end-users desired mode of operation. This requires a configuration interface be provided to the user so they are able to communicate this information. Currently, OpenTelemetry specifies this interface in the form of environment variables. This environment variable interface is limited in the structure of information it can communicate and the primitives it can support. The configuration project intends to produce the specification around the data model for language-agnostic configuration that provides additional flexibility for the end users. https://github.com/orgs/open-telemetry/projects/38 An OTEP Prototypes in Java, Python, Go, Erlang The specification of the configuration data model A repository containing the schema and schema validation tooling End users of OpenTelemetry to help validate the usage and configuration scenarios would be great to have participate in the discussions. Project lead @MrAlias @jack-berg Sponsoring TC members @carlosalberto @jack-berg Engineers contributing to the working group @MrAlias @jack-berg @tsloughter @MikeGoldsmith @codeboten Maintainers and approvers @srikanthccv (python) @CodeBlanch (.net) @lalitb (c++) Every 2 weeks, on Fridays at 10:30AM PT 3-6 months
Project: Vector (Observability and Analysis / Observability)
File: 2020-06-27-add-sasl-to-kafka.md

date: "2020-07-15" title: "Kafka components support SASL" description: "Vector has a new way to authenticate with Kafka!" authors: ["hoverbear"] hideonrelease_notes: false pr_numbers: [2897] release: "0.10.0" badges: type: "new feature" domains: ["sinks"] sinks: ["kafka"] The Kafka source and sink now support . You can review the option in the . ```diff title="vector.toml" [sources.source0] type = "kafka" # required inputs = ["..."] # required bootstrap_servers = "10.14.22.123:9092,10.14.23.332:9092" # required group_id = "consumer-group-name" # required keyfield = "messagekey" # optional, no default topics = ["^(prefix1|prefix2)-.+", "topic-1", "topic-2"] # required sasl.enabled = true # optional, default false sasl.mechanism = "SCRAM-SHA-512" # optional, no default sasl.password = "password" # optional, no default sasl.username = "username" # optional, no default ``` {{< warning >}} This feature isn't yet supported on Windows. {{< /warning >}}
Project: Checkmk (Observability and Analysis / Observability)
File: 16691.md

key | value | date | 2024-04-17T20:21:00+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | no This change is only incompatible for users monitoring hosts with a FreeIPMI version of 0.8.0 or earlier. FreeIPMI 0.8.1 was released in December 2009.
Project: SkyWalking (Observability and Analysis / Observability)
File: dynamic-config-configmap.md

is also supported as a Dynamic Configuration Center (DCC). To use it, please configure it as follows: ```yaml configuration: selector: ${SW_CONFIGURATION:k8s-configmap} k8s-configmap: period: ${SWCONFIGCONFIGMAP_PERIOD:60} namespace: ${SWCLUSTERK8S_NAMESPACE:default} labelSelector: ${SWCLUSTERK8S_LABEL:app=collector,release=skywalking} ``` `{namespace}` is the k8s namespace to which the configmap belongs. `{labelSelector}` is used to identify which configmaps would be selected. e.g. These 2 configmaps would be selected by the above config: ``` apiVersion: v1 kind: ConfigMap metadata: name: skywalking-dynamic-config namespace: default labels: app: collector release: skywalking data: configKey1: configValue1 configKey2: configValue2 ... ``` ``` apiVersion: v1 kind: ConfigMap metadata: name: skywalking-dynamic-config2 namespace: default labels: app: collector release: skywalking data: configKey3: configValue3 ... ``` The configs are configmap data items, as the above example shows. we can organize the configs in 1 or more configmap files. Under configmap.data: ``` configKey: configValue ``` e.g. The config is: ``` {agent-analyzer.default.slowDBAccessThreshold}:{default:200,mongodb:50} ``` The config in configmap is: ``` apiVersion: v1 kind: ConfigMap metadata: name: skywalking-dynamic-config namespace: default labels: app: collector release: skywalking data: agent-analyzer.default.slowDBAccessThreshold: default:200,mongodb:50 ``` The `data key` is composited by configKey and subItemKey to identify it is a group config: ``` configKey.subItemKey1: subItemValue1 configKey.subItemKey2: subItemValue2 ... ``` e.g. The config is: ``` {core.default.endpoint-name-grouping-openapi}:|{customerAPI-v1}:{value of customerAPI-v1} |{productAPI-v1}:{value of productAPI-v1} |{productAPI-v2}:{value of productAPI-v2} ``` The config can separate into 2 configmaps is: ``` apiVersion: v1 kind: ConfigMap metadata: name: skywalking-dynamic-config namespace: default labels: app: collector release: skywalking data: core.default.endpoint-name-grouping-openapi.customerAPI-v1: value of customerAPI-v1 core.default.endpoint-name-grouping-openapi.productAPI-v1: value of productAPI-v1 ``` ``` apiVersion: v1 kind: ConfigMap metadata: name: skywalking-dynamic-config2 namespace: default labels: app: collector release: skywalking data: core.default.endpoint-name-grouping-openapi.productAPI-v2: value of productAPI-v2 ```
Project: Checkmk (Observability and Analysis / Observability)
File: 16500.md

key | value | compatible | yes version | 2.4.0b1 date | 2024-02-22T16:55:08+00:00 level | 1 class | fix component | rest-api edition | cre The werk 16465 addressed a problem that prevented fetching information about the service discovery background job on a remote site. However, this solution introduced a new limitation, disallowing the execution of discovery in 'refresh' and 'tabula_rasa' modes for newly created hosts on remote sites. This werk successfully resolves this subsequent issue.
Project: Vector (Observability and Analysis / Observability)
File: 2020-02-27-nixos-support.md

date: "2020-04-13" title: "NixOS Support" description: "Bringing Vector to NixOS" authors: ["binarylogic"] pr_numbers: [1946] release: "0.9.0" hideonrelease_notes: true badges: type: "new feature" domains: ["platforms"] platforms: ["nixos"] Vector is , and we've now officially adopted it as a supported platform. This means we'll produce and help ensure it stays up to date. We .
Project: Checkmk (Observability and Analysis / Observability)
File: 16551.md

key | value | date | 2024-03-22T09:13:48+00:00 version | 2.4.0b1 class | fix edition | cee component | agents level | 1 compatible | yes After cloning a site with `omd cp` or renaming it with `omd mv`, opening the agent bakery GUI did result in a crash, showing a message like ``` Internal error: '/omd/sites/SITE/share/checkmk/agents/checkmkagent.linux' is not in the subpath of '/omd/sites/SITECOPY/share/check_mk/agents' OR one path is relative and the other is absolute. ``` As a workaround, you can delete the file `~/var/checkmk/wato/bakeryfile_status.mk` on the site.
Project: OpenFeature (Observability and Analysis / Feature Flagging)
File: test_specification.md

Some content. This MUST be done. This MUST NOT be done. This SHOULD be done in a certain way. This is a condition. #### Condition 1.1 > This is a condition. > > #### Condition 1.1.1 > > > This is a condition. > > > > ##### Conditional Requirement Conditional requirement name > > > > > This MAY be done. > > > > ##### Conditional Requirement Other name > > > > > This SHOULD NOT be done. > > > > ##### Conditional Requirement Another name here > > > > > This MAY be done. #### Condition 1.2 > This is a condition. > > ##### Conditional Requirement And another-name > > > This MUST be done. Some content. This MUST NOT be done. This is a condition. ##### Condition 2.1 > This is a condition. > > ##### Condition 2.2 > > > This is a condition. > > > > ##### Conditional Requirement The name here > > > > > This MAY be done. Some content.
Project: M3 (Observability and Analysis / Observability)
File: _index.md

title: "M3 Coordinator, API for reading/writing metrics and management" menuTitle: "M3 Coordinator" weight: 5 chapter: true M3 Coordinator is a service that coordinates reads and writes between upstream systems, such as Prometheus, and downstream systems, such as M3DB. It also provides management APIs to setup and configure different parts of M3. The coordinator is generally a bridge for read and writing different types of metrics formats and a management layer for M3. Note: M3DB by default includes the M3 Coordinator accessible on port 7201. For production deployments it is recommended to deploy it as a dedicated service to ensure you can scale the write coordination role separately and independently to database nodes as an isolated application separate from the M3DB database role.
Project: Vector (Observability and Analysis / Observability)
File: 2020-02-24-swimlanes-transform.md

date: "2020-04-13" title: "New Swimlanes Transform" description: "Split log streams with ease" authors: ["binarylogic"] pr_numbers: [1785] release: "0.8.0" hideonrelease_notes: false badges: type: "new feature" domains: ["transforms"] transforms: ["swimlanes"] The new makes it much easier to configure conditional branches of transforms and sinks. For example, you can easily create . ```toml title="vector.toml" [transforms.lanes] types = "swimlanes" [transforms.mytransformid.lanes.errors] "level.eq" = "error" [transforms.mytransformid.lanes.not_errors] "level.neq" = "error" ``` Remember to occasionally let your branches mingle so that they don't completely lose touch.
Project: Netdata (Observability and Analysis / Observability)
File: cgroup_10min_cpu_usage.md

The Netdata Agent calculates the average CPU utilization over the last 10 minutes. This alert indicates that your system is in high cgroup CPU utilization. The system will throttle the group CPU usage when the usage is over the limit. To fix this issue, try to increase the cgroup CPU limit. This alert is triggered in warning state when the average CPU utilization is between 75-80% and in critical state when it is between 85-95%.
Project: Netdata (Observability and Analysis / Observability)
File: vernemq_cluster_dropped.md

This alert indicates that VerneMQ, an MQTT broker, is experiencing issues with inter-node message delivery within a clustered environment. The Netdata agent calculates the amount of traffic dropped during communication with cluster nodes in the last minute. If you receive this alert, it means that the outgoing cluster buffer is full and some messages cannot be delivered. Dropped messages occur when the outgoing cluster buffer becomes full, and VerneMQ cannot deliver messages between its nodes. This can happen due to a remote node being down or unreachable, causing the buffer to fill up and preventing efficient message delivery. Check the connectivity and status of cluster nodes Verify that all cluster nodes are up, running and reachable. Use `vmq-admin cluster show` to get an overview of the cluster nodes and their connectivity status. ``` vmq-admin cluster show ``` Investigate logs for any errors or warnings Inspect the logs of the VerneMQ node(s) for any errors or warning messages. This can provide insight into any potential problems related to the cluster or network. ``` sudo journalctl -u vernemq ``` Increase the buffer size If the issue persists, consider increasing the buffer size. Adjust the `outgoingclusteringbuffer_size` value in the `vernemq.conf` file. ``` outgoingclusteringbuffersize = <newbuffer_size> ``` Replace `<newbuffersize>` with a larger value, for example, doubling the current buffer size. After updating the configuration, restart the VerneMQ service to apply the changes. ``` sudo systemctl restart vernemq ``` Monitor the dropped messages Continue to monitor the dropped messages using Netdata, and check if the issue is resolved after increasing the buffer size.
Project: Checkmk (Observability and Analysis / Observability)
File: 16411.md

key | value | date | 2024-03-13T10:26:52+00:00 version | 2.4.0b1 class | feature edition | cee component | checks level | 1 compatible | yes This Werks adds a HW/SW inventory for Robotmk. The content is under active development.
Project: Checkmk (Observability and Analysis / Observability)
File: 16780.md

key | value | date | 2024-04-24T14:41:14+00:00 version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes The following endpoints did not show that they returned an ETag header as part of their 200 OK response. Show all pending changes Show password This werk addresses this issue. Both now show the correct headers in their responses.
Project: Checkmk (Observability and Analysis / Observability)
File: 16487.md

key | value | date | 2024-03-19T14:31:54+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes If the age reported by a Fortigate signature is in the future, the service would crash when rendering the age of the signature. If this is the case, the service will now display a hint to check your system time.
Project: EaseAgent (Observability and Analysis / Observability)
File: bug_report.md

name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' name: Bug report about: Create a report to help us improve title: '' labels: '' assignees: '' Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: Execute '...' Send a request to '....' See error Expected behavior A clear and concise description of what you expected to happen. Version The version number of Easegress. Configuration EaseAgent Configuration ``` ``` Logs ``` EaseAgent logs, if applicable. ``` OS and Hardware OS: [e.g. Ubuntu 20.04] CPU:[e.g. Intel(R) Core(TM) i5-8265U] Memory: [e.g. 16GB] Additional context Add any other context about the problem here. Thanks for contributing !
Project: SkyWalking (Observability and Analysis / Observability)
File: Hour-Day-Metrics-Stopping.md

This issue is to be expected with an upgrade from 6.x to 7.x. See the of the ElasticSearch storage. You may simply delete all expired `-day_xxxxx` and `-hour_xxxxx`(`xxxxx` is a timestamp) indexes. Currently, SkyWalking uses the `metrics name-xxxxx` and `metrics name-month_xxxxx` indexes only.
Project: Checkmk (Observability and Analysis / Observability)
File: 16656.md

key | value | date | 2024-03-26T09:56:52+00:00 version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes This werk improves upon the validation of host names in the REST API, so that it is in line with the GUI. In some cases the REST API will still be more restrictive, but invalid host names will no longer be allowed.
Project: Logging Operator (Kube Logging) (Observability and Analysis / Observability)
File: splunk_hec.md

title: SplunkHEC weight: 200 generated_file: true Based on the . Available in Logging operator version 4.4 and later. {{< highlight yaml >}} apiVersion: logging.banzaicloud.io/v1beta1 kind: SyslogNGOutput metadata: name: splunkhec spec: splunkhecevent: url: "https://splunk-endpoint" token: valueFrom: secretKeyRef: name: splunk-hec key: token {{</ highlight >}} Additional HTTP request content-type option. Fallback option for index field. For details, see the . Fallback option for source field. Fallback option for sourcetype field. This option enables putting outgoing messages into the disk buffer of the destination to avoid message loss in case of a system failure on the destination side. For details, see the . Default: false event() accepts a template, which declares the content of the log message sent to Splunk. Default value: `${MSG}` Additional HTTP request headers. Additional HTTP request query options. Additional indexing metadata for Splunk. Sets the host field. Splunk index where the messages will be stored. Sets the source field. Sets the sourcetype field. Sets the time field. The token that syslog-ng OSE uses to authenticate on the event collector.
Project: Netdata (Observability and Analysis / Observability)
File: kern.ipc.shm.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/freebsd.plugin/integrations/kern.ipc.shm.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/freebsd.plugin/metadata.yaml" sidebar_label: "kern.ipc.shm" 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/memory.svg" width="150"/> Plugin: freebsd.plugin Module: kern.ipc.shm <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> Collect shared memory information. 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 give status about current shared memory segments. This scope has no labels. Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | system.ipcsharedmem_segs | segments | segments | | system.ipcsharedmem_size | allocated | KiB | 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 options</summary> | Name | Description | Default | Required | |:-|:--|:-|:--:| | kern.ipc.shm | Enable or disable shared memory metric. | yes | no | </details> There are no configuration examples.
Project: OpenTracing (Observability and Analysis / Observability)
File: CHANGELOG.md

Changes by Version ================== 1.2.0 (2020-07-01) Restore the ability to reset the current span in context to nil (#231) -- Yuri Shkuro Use error.object per OpenTracing Semantic Conventions (#179) -- Rahman Syed Convert nil pointer log field value to string "nil" (#230) -- Cyril Tovena Add Go module support (#215) -- Zaba505 Make SetTag helper types in ext public (#229) -- Blake Edwards Add log/fields helpers for keys from specification (#226) -- Dmitry Monakhov Improve noop impementation (#223) -- chanxuehong Add an extension to Tracer interface for custom go context creation (#220) -- Krzesimir Nowak Fix typo in comments (#222) -- meteorlxy Improve documentation for log.Object() to emphasize the requirement to pass immutable arguments (#219) -- [mock] Return ErrInvalidSpanContext if span context is not MockSpanContext (#216) -- Milad Irannejad 1.1.0 (2019-03-23) Notable changes: The library is now released under Apache 2.0 license Use Set() instead of Add() in HTTPHeadersCarrier is functionally a breaking change (fixes issue ) 'golang.org/x/net/context' is replaced with 'context' from the standard library List of all changes: Export StartSpanFromContextWithTracer (#214) <Aaron Delaney> Add IsGlobalTracerRegistered() to indicate if a tracer has been registered (#201) <Mike Goldsmith> Use Set() instead of Add() in HTTPHeadersCarrier (#191) <jeremyxu2010> Update license to Apache 2.0 (#181) <Andrea Kao> Replace 'golang.org/x/net/context' with 'context' (#176) <Tony Ghita> Port of Python opentracing/harness/api_check.py to Go (#146) <chris erway> Fix race condition in MockSpan.Context() (#170) <Brad> Add PeerHostIPv4.SetString() (#155) <NeoCN> Add a Noop log field type to log to allow for optional fields (#150) <Matt Ho> 1.0.2 (2017-04-26) Add more semantic tags (#139) <Rustam Zagirov> 1.0.1 (2017-02-06) Correct spelling in comments <Ben Sigelman> Address race in nextMockID() (#123) <bill fumerola> log: avoid panic marshaling nil error (#131) <Anthony Voutas> Deprecate InitGlobalTracer in favor of SetGlobalTracer (#128) <Yuri Shkuro> Drop Go 1.5 that fails in Travis (#129) <Yuri Shkuro> Add convenience methods Key() and Value() to log.Field <Ben Sigelman> Add convenience methods to log.Field (2 years, 6 months ago) <Radu Berinde> 1.0.0 (2016-09-26) This release implements OpenTracing Specification 1.0 (https://opentracing.io/spec)