plone

grafana-alloy-devel-1.9.1-0.1.gitd3d7931.lbn36.x86_64
Development tools for Alloy; linting and component listing
Located in LBN / … / Network Monitoring / BastionLinux 36
grafana-grizzly-0.7.1-1.lbn36.x86_64
A utility for managing Jsonnet dashboards against the Grafana API.
Located in LBN / … / Network Monitoring / BastionLinux 36
grafana-image-renderer-3.12.0-1.lbn36.x86_64
Rendering images requires a lot of memory, mainly because Grafana creates browser instances in the background for the actual rendering. We recommend a minimum of 16GB of free memory on the system rendering images. Rendering multiple images in parallel requires an even bigger memory footprint. You can use the remote rendering service in order to render images on a remote system, so your local system resources are not affected. Configuration ------------- Install this package; and edit the rendering section in your grafana config: [rendering] server_url = http://localhost:8081/render callback_url = http://localhost:3000/
Located in LBN / … / Network Monitoring / BastionLinux 36
grafana-k6-0.56.0-0.1.git50afb99.lbn36.x86_64
k6 is a modern load testing tool, building on our years of experience in the load and performance testing industry. It provides a clean, approachable scripting API, local and cloud execution, and flexible configuration.
Located in LBN / … / Core Linux / BastionLinux 36
grafana-k6-1.0.0-0.1.git41b4984.lbn36.x86_64
k6 is a modern load testing tool, building on our years of experience in the load and performance testing industry. It provides a clean, approachable scripting API, local and cloud execution, and flexible configuration.
Located in LBN / … / Network Monitoring / BastionLinux 36
grafana-kiosk-1.0.8-1.lbn36.x86_64
Kiosk Utility for Grafana.
Located in LBN / … / Network Monitoring / BastionLinux 36
grafana-loki-1.2.0-0.3.gitccef3da.lbn25.x86_64
Like Prometheus, but for logs.
Located in LBN / … / Network Monitoring / BastionLinux 25
grafana-loki-3.5.0-0.1.git4b16bc4.lbn36.x86_64
Loki: like Prometheus, but for logs. Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate. It does not index the contents of the logs, but rather a set of labels for each log stream. Compared to other log aggregation systems, Loki: does not do full text indexing on logs. By storing compressed, unstructured logs and only indexing metadata, Loki is simpler to operate and cheaper to run. indexes and groups log streams using the same labels you’re already using with Prometheus, enabling you to seamlessly switch between metrics and logs using the same labels that you’re already using with Prometheus. is an especially good fit for storing Kubernetes Pod logs. Metadata such as Pod labels is automatically scraped and indexed. has native support in Grafana (needs Grafana v6.0). A Loki-based logging stack consists of 3 components: promtail is the agent, responsible for gathering logs and sending them to Loki. loki is the main server, responsible for storing logs and processing queries. Grafana for querying and displaying the logs. Loki is like Prometheus, but for logs: we prefer a multidimensional label-based approach to indexing, and want a single-binary, easy to operate system with no dependencies. Loki differs from Prometheus by focusing on logs instead of metrics, and delivering logs via push, instead of pull.
Located in LBN / … / Network Monitoring / BastionLinux 36
grafana-loki-3.5.0-0.1.git4b16bc4.lbn36.x86_64
Loki: like Prometheus, but for logs. Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate. It does not index the contents of the logs, but rather a set of labels for each log stream. Compared to other log aggregation systems, Loki: does not do full text indexing on logs. By storing compressed, unstructured logs and only indexing metadata, Loki is simpler to operate and cheaper to run. indexes and groups log streams using the same labels you’re already using with Prometheus, enabling you to seamlessly switch between metrics and logs using the same labels that you’re already using with Prometheus. is an especially good fit for storing Kubernetes Pod logs. Metadata such as Pod labels is automatically scraped and indexed. has native support in Grafana (needs Grafana v6.0). A Loki-based logging stack consists of 3 components: promtail is the agent, responsible for gathering logs and sending them to Loki. loki is the main server, responsible for storing logs and processing queries. Grafana for querying and displaying the logs. Loki is like Prometheus, but for logs: we prefer a multidimensional label-based approach to indexing, and want a single-binary, easy to operate system with no dependencies. Loki differs from Prometheus by focusing on logs instead of metrics, and delivering logs via push, instead of pull.
Located in LBN / … / Core Linux / BastionLinux 36
grafana-loki-logcli-1.2.0-0.3.gitccef3da.lbn25.x86_64
If you are running on Grafana Cloud, use: $ export GRAFANA_ADDR=https://logs-us-west1.grafana.net $ export GRAFANA_USERNAME=<username> $ export GRAFANA_PASSWORD=<password> Otherwise you can point LogCLI to a local instance directly without needing a username and password: $ export GRAFANA_ADDR=http://localhost:3100 Note: If you are running Loki behind a proxy server and you have authentication configured, you will also have to pass in GRAFANA_USERNAME and GRAFANA_PASSWORD accordingly. $ logcli labels job https://logs-dev-ops-tools1.grafana.net/api/prom/label/job/values cortex-ops/consul cortex-ops/cortex-gw
Located in LBN / … / Network Monitoring / BastionLinux 25

« Previous 10 items Next 10 items » 1 ... 830 831 832 833 834 835 836 ... 4850

Sections

Search results


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.