uptime-kuma | A fancy self-hosted monitoring tool | Monitoring library

by louislam JavaScript Version: 1.14.1 License: MIT

Download this library from

kandi X-RAY | uptime-kuma Summary

uptime-kuma is a JavaScript library typically used in Performance Management, Monitoring, Docker applications. uptime-kuma has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

It is a self-hosted monitoring tool like "Uptime Robot".

Support

Quality

Security

License

Reuse

kandi-support Support

uptime-kuma has a medium active ecosystem.
It has 16089 star(s) with 1180 fork(s). There are 115 watchers for this library.
There were 7 major release(s) in the last 6 months.
There are 435 open issues and 550 have been closed. On average issues are closed in 29 days. There are 41 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of uptime-kuma is 1.14.1

uptime-kuma Support

Best in #Monitoring

Average in #Monitoring

uptime-kuma Support

Best in #Monitoring

Average in #Monitoring

quality kandi Quality

uptime-kuma has 0 bugs and 0 code smells.

uptime-kuma Quality

Best in #Monitoring

Average in #Monitoring

uptime-kuma Quality

Best in #Monitoring

Average in #Monitoring

security Security

uptime-kuma has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
uptime-kuma code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.

uptime-kuma Security

Best in #Monitoring

Average in #Monitoring

uptime-kuma Security

Best in #Monitoring

Average in #Monitoring

license License

uptime-kuma is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.

uptime-kuma License

Best in #Monitoring

Average in #Monitoring

uptime-kuma License

Best in #Monitoring

Average in #Monitoring

build Reuse

uptime-kuma releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
It has 432 lines of code, 0 functions and 193 files.
It has low code complexity. Code complexity directly impacts maintainability of the code.

uptime-kuma Reuse

Best in #Monitoring

Average in #Monitoring

uptime-kuma Reuse

Best in #Monitoring

Average in #Monitoring

Top functions reviewed by kandi - BETA

kandi has reviewed uptime-kuma and discovered the below as its top functions. This is intended to give you an instant insight into uptime-kuma implemented functionality, and help decide if they suit your requirements.

Creates a new ApiCache instance .
Encapsulates the cache statistics .
Create a response object for the response
Ping .
Downloads the tar .
Send an API response .
Initialize the database .
List of timezones .
Generate a random 32 - bit number
Updates the wiki with the new version

uptime-kuma Key Features

Monitoring uptime for HTTP(s) / TCP / HTTP(s) Keyword / Ping / DNS Record / Push / Steam Game Server.

Fancy, Reactive, Fast UI/UX.

Notifications via Telegram, Discord, Gotify, Slack, Pushover, Email (SMTP), and 70+ notification services, click here for the full list.

20 second intervals.

Multi Languages

Simple Status Page

Ping Chart

Certificate Info

uptime-kuma Examples and Code Snippets

See all related Code Snippets

🐳 Docker

Copy

Download

docker volume create uptime-kuma
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1

💪🏻 Non-Docker

Copy

Download

# Update your npm to the latest version
npm install npm -g

git clone https://github.com/louislam/uptime-kuma.git
cd uptime-kuma
npm run setup

# Option 1. Try it
node server/server.js

# (Recommended) Option 2. Run in background using PM2
# Install PM2 if you don't have it: npm install pm2 -g
pm2 start server/server.js --name uptime-kuma

See all related Code Snippets

Community Discussions

Trending Discussions on Monitoring

Linux IP monitoring tool
how to check service running on other server with python
Differentiate databricks streaming queries in datadog
Ignore specific set of labels on prometheus query
Prometheus remote write mTLS
Prometheus service discovery with docker-compose
Where can I get node exporter metrics description?
Prometheus: find max RPS
Integrate GCP with OpsGenie for Alerts
Kubernetes pvc in rwx monitoring

Trending Discussions on Monitoring

QUESTION

Linux IP monitoring tool

Asked 2022-Apr-08 at 16:12

I need to get the IP numbers that are connecting to the EC2 instance then add them to AWS security group as a security group rule. So only those machines will have the permission to connect to instance. I don't need the port number that they're connecting to instance.

I installed iptraf-ng but app is very slow on the instance. Any other suggestions to capture the connecting IP's to instance so I can add them faster to security group rule?

ANSWER

Answered 2022-Apr-08 at 16:12

You can use VPC Flow logs to monitor the traffic to the VPC (which will include the traffic that is going to the EC2 instance).

Source https://stackoverflow.com/questions/71800154

QUESTION

how to check service running on other server with python

Asked 2022-Mar-14 at 13:12

I have a problem with checking my service on other windows or Linux servers.

My problem is that I have to make a request from one server to the other servers and check if the vital services of those servers are active or disabled.

I wrote Python code to check for services, which only works on a local system.

import psutil
 
def getService(name):

    service = None
    try:
        service = psutil.win_service_get(name)
        service = service.as_dict()
    except Exception as ex:
        print(str(ex))
    return service

service = getService('LanmanServer')
if service:
    print("service found")
else:
    print("service not found")

if service and service['status'] == 'running':
    print("service is running")
else:
    print("service is not running")

Does this code have this feature? Or suggest another code؟

I have reviewed suggestions such as using server agents (influx, ...), which are not working for my needs.

ANSWER

Answered 2022-Mar-08 at 17:46

As far as I know, psutil can only be used for gathering information about local processes, and is not suitable for retrieving information about processes running on other hosts. If you want to check whether or not a process is running on another host, there are many ways to approach this problem, and the solution depends on how deep you want to go (or need to go), and what your local situation is. From the top of my head, here are some ideas:

If you are only dealing with network services with exposed ports:

A very simple solution would involve using a script and a port scanner (nmap); if a port that a service is listening behind, is open, then we can assume that the service is running. Run the script every once in a while to check up on the services, and do your thing.
If you want to stay in Python, you can achieve the same end result by using Python's socket module to try and connect to a given host and port to determine whether or not the port that a service is listening behind, is open.
A Python package or tool for monitoring network services on other hosts like this probably already exists.

If you want more information and need to go deeper, or you want to check up on local services, your solution will have to involve a local monitor process on each host, and connecting to that process to gather information.

You can use your code to implement a server that lets clients connect to it, to check up on the services running on that host. (Check the socket module's official documentation for examples on how to implement clients and servers.)

Here's the big thing though. Based on your question and how it was asked, I would assume that you do not have the experience nor the insight to implement this in a secure way yet. If you're using this for a simple hobby/student project, roll out your own solution, and learn. Otherwise, I would recommend that you check out an existing solution like Nagios, and follow the security recommendations very closely.

Source https://stackoverflow.com/questions/71393915

QUESTION

Prometheus service discovery with docker-compose

Asked 2022-Feb-19 at 17:59

I have the following docker-compose file:

version: '3.4'

services:
    serviceA:
        image: <image>
        command: <command>
        labels:
           servicename: "service-A"
        ports:
         - "8080:8080"

    serviceB:
        image: <image>
        command: <command>
        labels:
           servicename: "service-B"
        ports:
         - "8081:8081"

    prometheus:
        image: prom/prometheus:v2.32.1
        container_name: prometheus
        volumes:
          - ./prometheus:/etc/prometheus
          - prometheus_data:/prometheus
        command:
          - '--config.file=/etc/prometheus/prometheus.yml'
          - '--storage.tsdb.path=/prometheus'
          - '--web.console.libraries=/etc/prometheus/console_libraries'
          - '--web.console.templates=/etc/prometheus/consoles'
          - '--storage.tsdb.retention.time=200h'
          - '--web.enable-lifecycle'
        restart: unless-stopped
        expose:
          - 9090

        labels:
          org.label-schema.group: "monitoring"

volumes:
    prometheus_data: {}

The docker-compose contain also Prometheus instance with the following configuration:

global:
  scrape_interval:     15s # By default, scrape targets every 15 seconds.


scrape_configs:
  - job_name: 'prometheus'
    scrape_interval: 5s
    static_configs:
      - targets: ['localhost:9090', 'serviceA:8080', 'serviceB:8081']

ServiceA and ServiceB exposing prometheus metrics(each one on it's own port).

When there is one instance from each service everything works fine but when i want to scale the services and run more than one instance the prometheus metrics collection started to messed up the metrics collection and the data is corrupted.

I looked for docker-compose service discovery for this issue but didn't found suitable one. How can I solve this?

ANSWER

Answered 2022-Feb-19 at 17:59

The solution to this problem is to use an actual service discovery instead of static targets. This way Prometheus will scrape each replica during each iteration.

If it is just docker-compose (I mean, not Swarm), you can use DNS service discovery (dns_sd_config) to obtain all IPs belonging to a service:

# docker-compose.yml
version: "3"
services:
  prometheus:
    image: prom/prometheus

  test-service:  # <- this
    image: nginx
    deploy:
      replicas: 3
---
# prometheus.yml
scrape_configs:
  - job_name: test
    dns_sd_configs:
      - names:
          - test-service  # goes here
        type: A
        port: 80

This is the simplest way to get things up and running.

Moving next, you can use the dedicated Docker service discovery: docker_sd_config. Apart from the target list, it gives you more data in labels (e.g. container name, image version, etc) but it also requires a connection to the Docker daemon to get this data. In my opinion, this is an overkill for a development environment, but it might be essential in production. Here is an example configuration, boldly copy-pasted from https://github.com/prometheus/prometheus/blob/release-2.33/documentation/examples/prometheus-docker.yml :

# A example scrape configuration for running Prometheus with Docker.

scrape_configs:
  # Make Prometheus scrape itself for metrics.
  - job_name: "prometheus"
    static_configs:
      - targets: ["localhost:9090"]

  # Create a job for Docker daemon.
  #
  # This example requires Docker daemon to be configured to expose
  # Prometheus metrics, as documented here:
  # https://docs.docker.com/config/daemon/prometheus/
  - job_name: "docker"
    static_configs:
      - targets: ["localhost:9323"]

  # Create a job for Docker Swarm containers.
  #
  # This example works with cadvisor running using:
  # docker run --detach --name cadvisor -l prometheus-job=cadvisor
  #     --mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock,ro
  #     --mount type=bind,src=/,dst=/rootfs,ro
  #     --mount type=bind,src=/var/run,dst=/var/run
  #     --mount type=bind,src=/sys,dst=/sys,ro
  #     --mount type=bind,src=/var/lib/docker,dst=/var/lib/docker,ro
  #     google/cadvisor -docker_only
  - job_name: "docker-containers"
    docker_sd_configs:
      - host: unix:///var/run/docker.sock # You can also use http/https to connect to the Docker daemon.
    relabel_configs:
      # Only keep containers that have a `prometheus-job` label.
      - source_labels: [__meta_docker_container_label_prometheus_job]
        regex: .+
        action: keep
      # Use the task labels that are prefixed by `prometheus-`.
      - regex: __meta_docker_container_label_prometheus_(.+)
        action: labelmap
        replacement: $1

At last, there is the dockerswarm_sd_config which is to be used, obviously, with Docker Swarm. This is the most complex thing of the trio and thus, there is a comprehensive official setup guide. Like the docker_sd_config it has additional information about containers in labels and even more than that (for example, it can tell on which node the container is). An example configuration is available here: https://github.com/prometheus/prometheus/blob/release-2.33/documentation/examples/prometheus-dockerswarm.yml , but you should really read the docs to be able to understand it and tune for yourself.

Source https://stackoverflow.com/questions/70803245

QUESTION

Where can I get node exporter metrics description?

Asked 2022-Feb-10 at 08:34

I'm new to monitoring the k8s cluster with prometheus, node exporter and so on.

I want to know that what the metrics exactly mean for though the name of metrics are self descriptive.

I already checked the github of node exporter, but I got not useful information.

Where can I get the descriptions of node exporter metrics?

Thanks

ANSWER

Answered 2022-Feb-10 at 08:34

There is a short description along with each of the metrics. You can see them if you open node exporter in browser or just curl http://my-node-exporter:9100/metrics. You will see all the exported metrics and lines with # HELP are the description ones:

# HELP node_cpu_seconds_total Seconds the cpus spent in each mode.
# TYPE node_cpu_seconds_total counter
node_cpu_seconds_total{cpu="0",mode="idle"} 2.59840376e+07

Grafana can show this help message in the editor: Prometheus (with recent experimental editor) can show it too: And this works for all metrics, not just node exporter's. If you need more technical details about those values, I recommend searching for the information in Google and man pages (if you're on Linux). Node exporter takes most of the metrics from /proc almost as-is and it is not difficult to find the details. Take for example node_memory_KReclaimable_bytes. 'Bytes' suffix is obviously the unit, node_memory is just a namespace prefix, and KReclaimable is the actual metric name. Using man -K KReclaimable will bring you to the proc(5) man page, where you can find that:

           KReclaimable %lu (since Linux 4.20)
                 Kernel allocations that the kernel will attempt to
                 reclaim under memory pressure.  Includes
                 SReclaimable (below), and other direct allocations
                 with a shrinker.

Finally, if this intention to learn more about the metrics is inspired by the desire to configure alerts for your hardware, you can skip to the last part and grab some alerts shared by the community from here: https://awesome-prometheus-alerts.grep.to/rules#host-and-hardware

Source https://stackoverflow.com/questions/70300286

QUESTION

Prometheus: find max RPS

Asked 2022-Feb-10 at 08:11

Say I have two metrics in Prometheus, both counters:

Ok:

nginx_ingress_controller_requests{prometheus_from="$cluster", ingress="brand-safety-phoenix-service", status="200"}

Failure:

nginx_ingress_controller_requests{prometheus_from="$cluster", ingress="brand-safety-phoenix-service", status!="200"}

Total:

nginx_ingress_controller_requests{prometheus_from="$cluster", ingress="brand-safety-phoenix-service"}

My question is how to find on which RPS failures occurred as promQL query

I'm expecting the following response:

Means, that if pod receives > 400 RPS, Failure metric begin to happen

full query (after got answered)

sum((sum(rate(nginx_ingress_controller_requests{prometheus_from="$cluster", ingress="brand-safety-phoenix-service"}[$__rate_interval])) without (status))
  and
  (sum(rate(nginx_ingress_controller_requests{prometheus_from="$cluster", ingress="brand-safety-phoenix-service", status !="200"}[$__rate_interval])) without (status) > 0))

ANSWER

Answered 2022-Feb-08 at 18:32

You need the following query:

rps_total and (rps_failure > 0)

The and binary operation is used for matching right-hand time series to the left-hand series with the same set of labels. See these docs for details on matching rules.

Let's substitute rps_total and rps_failure with the actual time series given matching rules mentioned above.

The rps_total is substituted with sum(nginx_ingress_controller_requests{prometheus_from="$cluster", ingress="brand-safety-phoenix-service"}) without (status) . The sum(...) without (status) is needed in order to sum metrics across all the status labels grouped by the remaining labels.
The rps_failure is substituted with sum(nginx_ingress_controller_requests{prometheus_from="$cluster", ingress="brand-safety-phoenix-service", status!="200"}) without (status)

Then the final PromQL query will look like:

(
  sum(nginx_ingress_controller_requests{prometheus_from="$cluster", ingress="brand-safety-phoenix-service"}) without (status)
  and
  (sum(nginx_ingress_controller_requests{prometheus_from="$cluster", ingress="brand-safety-phoenix-service", status!="200"}) without (status) > 0)
)

Source https://stackoverflow.com/questions/71021126

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install uptime-kuma

If you need more options or need to browse via a reverse proxy, please read:.

Support

If you want to report a bug or request a new feature. Free feel to open a new issue. If you want to translate Uptime Kuma into your language, please read: https://github.com/louislam/uptime-kuma/tree/master/src/languages. If you want to modify Uptime Kuma, this guideline may be useful for you: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md. English proofreading is needed too because my grammar is not that great, sadly. Feel free to correct my grammar in this README, source code, or wiki.