Modified items

All recently modified items, latest first.

collectd-drbd-5.8.0-10.lbn25.py37.x86_64: This plugin collects data from DRBD.

collectd-dns-5.8.0-10.lbn25.py37.x86_64: This plugin collects DNS traffic data.

collectd-disk-5.8.0-10.lbn25.py37.x86_64: This plugin collects statistics of harddisk and, where supported, partitions.

collectd-dbi-5.8.0-10.lbn25.py37.x86_64: This plugin uses the dbi library to connect to various databases, execute SQL statements and read back the results.

collectd-curl_xml-5.8.0-10.lbn25.py37.x86_64: This plugin retrieves XML data via curl.

collectd-curl_json-5.8.0-10.lbn25.py37.x86_64: This plugin retrieves JSON data via curl.

collectd-curl-5.8.0-10.lbn25.py37.x86_64: This plugin reads webpages with curl

collectd-ceph-5.8.0-10.lbn25.py37.x86_64: This plugin collects data from Ceph.

collectd-bind-5.8.0-10.lbn25.py37.x86_64: This plugin retrieves statistics from the BIND dns server.

collectd-ascent-5.8.0-10.lbn25.py37.x86_64: This plugin collects data about an Ascent server, a free server for the "World of Warcraft" game.

collectd-apache-5.8.0-10.lbn25.py37.x86_64: This plugin collects data provided by Apache's 'mod_status'.

collectd-amqp-5.8.0-10.lbn25.py37.x86_64: This plugin can be used to communicate with other instances of collectd or third party applications using an AMQP message broker.

collectd-5.8.0-10.lbn25.py37.x86_64: collectd is a daemon which collects system performance statistics periodically and provides mechanisms to store the values in a variety of ways, for example in RRD files.

rubygem-newrelic_rpm-6.7.0.359-1.lbn25.noarch: New Relic is a performance management system, developed by New Relic, Inc (http://www.newrelic.com). New Relic provides you with deep information about the performance of your web application as it runs in production. The New Relic Ruby Agent is dual-purposed as a either a Gem or plugin, hosted on https://github.com/newrelic/rpm/.

python3-newrelic-5.2.0.127-1.lbn25.x86_64: The newrelic package instruments your application for performance monitoring and advanced performance analytics with New Relic. Pinpoint and solve Python application performance issues down to the line of code. New Relic APM is the only tool you’ll need to see everything in your Python application, from the end user experience to server monitoring. Trace problems down to slow database queries, slow 3rd party APIs and web services, caching layers, and more. Monitor your app in a production environment and make sure your app can stand a big spike in traffic by running scalability reports.

python2-newrelic-5.2.0.127-1.lbn25.x86_64: The newrelic package instruments your application for performance monitoring and advanced performance analytics with New Relic. Pinpoint and solve Python application performance issues down to the line of code. New Relic APM is the only tool you’ll need to see everything in your Python application, from the end user experience to server monitoring. Trace problems down to slow database queries, slow 3rd party APIs and web services, caching layers, and more. Monitor your app in a production environment and make sure your app can stand a big spike in traffic by running scalability reports.

winlogbeat-7.4.2-1.git1507515.lbn25.x86_64: You know, for windows event logs Winlogbeat is an open-source log collector that ships Windows Event Logs to Elasticsearch or Logstash. It installs as a Windows service on all versions since Windows XP.

metricbeat-7.4.2-1.git1507515.lbn25.x86_64: Metricbeat fetches a set of metrics on a predefined interval from the operating system and services such as Apache web server, Redis, and more.

heartbeat-7.4.2-1.git1507515.lbn25.x86_64: Heartbeat is a lightweight daemon that you install on a remote server to periodically check the status of your services and determine whether they are available. Unlike Metricbeat, which only tells you if your servers are up or down, Heartbeat tells you whether your services are reachable. Heartbeat is useful when you need to verify that you’re meeting your service level agreements for service uptime. It’s also useful for other scenarios, such as security use cases, when you need to verify that no one from the outside can access services on your private enterprise server. You can configure Heartbeat to ping all DNS-resolvable IP addresses for a specified hostname. That way, you can check all services that are load-balanced to see if they are available. When you configure Heartbeat, you specify monitors that identify the hostnames that you want to check. Each monitor runs based on the schedule that you specify. For example, you can configure one monitor to run every 10 minutes, and a different monitor to run between the hours of 9:00 and 17:00. Heartbeat currently supports monitors for checking hosts via: ICMP (v4 and v6) Echo Requests. Use the icmp monitor when you simply want to check whether a service is available. This monitor requires root access. TCP. Use the tcp monitor to connect via TCP. You can optionally configure this monitor to verify the endpoint by sending and/or receiving a custom payload. HTTP. Use the http monitor to connect via HTTP. You can optionally configure this monitor to verify that the service returns the expected response, such as a specific status code, response header, or content. The tcp and http monitors both support SSL/TLS and some proxy settings.

functionbeat-7.4.2-1.git1507515.lbn25.x86_64: Functionbeat is an Elastic Beat that you deploy on your serverless environment to collect events generated by cloud services and ship the events to Elasticsearch. This version supports deploying Functionbeat as an AWS Lambda service and responds to the triggers defined for the following event sources: CloudWatch Logs Amazon Simple Queue Service (SQS) Kinesis Filebeat is an open source file harvester, mostly used to fetch logs files and feed them

« Previous 20 items Next 20 items » 1 ... 1234 1235 1236 1237 1238 1239 1240 ... 2425


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

Sections

Modified items