strawgate/kb-yaml-to-lens

AI Summary: This GitHub issue proposes adding a configuration option to display value labels directly on data points for XY charts. Currently, value labels are hardcoded to 'hide', limiting chart readability. The suggested solution involves introducing a `show_value_labels` boolean field to the chart configuration and updating the compilation logic to utilize this setting.

AI Summary: The task is to review all project readmes that list available OpenTelemetry (OTel) metrics and compare them against their corresponding dashboards. The objective is to identify any metrics documented in the readmes that are not currently utilized within those dashboards and then document this information back into the respective readmes.

AI Summary: The issue addresses a problem where dashboards, such as the Apache dashboard, display three side-by-side XY charts with visible legends, making them too narrow and difficult to read. Proposed solutions include moving legends to the bottom or limiting dashboards to a maximum of two side-by-side XY charts. Additionally, the team should investigate the feasibility of implementing a linting rule to enforce these design guidelines.

AI Summary: This GitHub issue requests the removal of "silly" markdown panels that are currently present across various ES|QL dashboards. The panels are described as being "all over the place" and are considered unnecessary clutter that should be eliminated.

AI Summary: This issue requests the validation of three recently merged Redis OpenTelemetry dashboards (`overview.yaml`, `instance-details.yaml`, `database-metrics.yaml`). The task involves setting up an environment to ingest Redis metrics via OpenTelemetry and verifying that these dashboards correctly display the specified key metrics using the `metrics-*` index pattern and `data_stream.dataset == "redisreceiver.otel"` filter.

AI Summary: This issue requests validation of a new Memcached OpenTelemetry dashboard bundle, specifically `01-memcached-overview.yaml`, located at `docs/content/examples/memcached_otel/`. The task involves setting up a Memcached instance via Docker, configuring an OpenTelemetry collector to gather metrics, and verifying key metrics like `memcached.bytes` are correctly displayed on the dashboard. Validation requires checking against an `metrics-*` index pattern and `data_stream.dataset == "memcachedreceiver.otel"` filter.

AI Summary: This issue calls for a comprehensive review of all existing OTel Dashboards to address recurring issues like incorrect attribute names, faulty ES|QL queries, and missing metrics. The goal is to learn from past mistakes, update ES|QL documentation with general guidelines, and potentially create a new guide for building OTel receiver dashboards to prevent future inaccuracies.

AI Summary: This issue requests the validation of an Aerospike dashboard bundle, which includes three specific dashboards (`overview.yaml`, `node-metrics.yaml`, `namespace-metrics.yaml`). The validation requires setting up an environment to ingest Aerospike metrics into Elasticsearch using specified index patterns and data streams, then verifying that all dashboards display correctly and show meaningful data for key metrics.

AI Summary: This issue requires validating the recently merged OpenTelemetry dashboard bundle for Apache HTTP Server. The task involves verifying the `01-apache-overview.yaml` dashboard, located at `docs/content/examples/apache_otel/`, ensuring it correctly displays data based on the specified index pattern (`metrics-*`), filter (`data_stream.dataset == "apachereceiver.otel"`), and key Apache metrics.

AI Summary: This issue proposes implementing snapshot tests for entire dashboards to ensure that any unintended changes in their structure or appearance are captured. The goal is to enhance the reliability of the UI by detecting regressions early. This involves setting up the necessary testing framework and defining which dashboards to include.

AI Summary: This GitHub issue proposes a change to the compilation process for an 'integrations repo,' requiring each dashboard to be compiled into a separate JSON file. The naming convention for these files should be `<id>.json`. The issue also includes a question about whether this specific output format is currently supported.

AI Summary: This issue requires reviewing and updating all existing code snippets to ensure they are accurate and reflect recent schema changes related to size, position, and other attributes. Additionally, new snippets need to be created for any recently added panels.

AI Summary: This issue requests a new option to export dashboards as individual, pretty-printed JSON files, rather than a single NDJSON. This feature is needed for Fleet integration and should include an exit code that reflects the number of files whose content changed, allowing CI to detect when YAML configurations are updated but their corresponding JSON exports are not.

AI Summary: This GitHub issue proposes standardizing all documentation examples to use `logs-*` or `metrics-*` index patterns, replacing current arbitrary ones. The goal is to make examples runnable for a broader audience, specifically by using commonly available fields that would be sent by an OpenTelemetry collector, enabling easy copy-paste functionality for users.

AI Summary: This GitHub issue addresses the need to clean up the Panel documentation, specifically for ES|QL metrics examples. Currently, many examples are either partially complete or entirely commented out, rendering them unusable. The goal is to transform these into fully runnable dashboard examples, allowing users to easily copy/paste and experiment, while also enabling automated tests to verify their syntax and validity.

AI Summary: This issue proposes a refactor of the project's CLI commands, Kibana client, and Elasticsearch client creation. The CLI has become messy and needs standardization using Click documentation. The Kibana client will be re-architected into a more maintainable class with URL builders and HTTP helpers, and an ES client builder will also be created, starting with a review of options and planning.

AI Summary: The script `gh-check-repo-activity.sh` uses the `gh` CLI without verifying its installation, which can lead to cryptic errors if the tool is missing. The issue proposes adding a `command -v gh` check early in the script to ensure the prerequisite is met, aligning with similar checks in other scripts from a related PR.

AI Summary: This GitHub issue, marked as a 'Good First Issue', aims to improve code documentation by adding missing class-level docstrings to several Pydantic view model classes. These models represent compiled output structures for Kibana dashboards. The task involves identifying relevant files, reviewing existing docstring patterns, and adding descriptive docstrings to enhance auto-generated API docs and aid new contributors.

AI Summary: This issue proposes adding two new panel types to dashboards: collapsible sections and alert panels. Collapsible sections will allow users to group and organize other panels, improving dashboard readability and navigation, while alert panels will display active alerts from Observability/Security applications.