uptime | Django web app for monitoring websites | Continuous Deployment library

I'm trying to install laravel/sail into an existing project, which doesn't appear to have had it installed before. This project is normally run on vagrant I believe.

I'm trying to get it running on WSL2, using Laravel Sail. I'm also not entirely sure if that's the best approach in my case.

My understanding is that I can use sail to get the project running via docker, with minimal setup and configuration.

I seem to be getting an error when I try to install sail via composer. These are the instructions I'm following: https://laravel.com/docs/9.x/sail#installing-sail-into-existing-applications

Here's the error:

I have a docker container with an XDP program loaded on it. I also have a batch file for the bpftool to run. When I run bpftool batch file tmp_bpftool.txt, I get Error: reading batch file failed: Operation not permitted. I am the root in the container. So, what could possibly be the problem?

The batch file is as below: (512 updates on map 59 and 1 update on map 58)

We have a site that has been working pretty well for the past 2 years. But we are actually seeing random peaks in the database load that make the site very slow for a few seconds.

These peaks only appear from a certain load on the server and are impossible to predict. More users = more peaks. Everything run very smoothly outside of those peaks (page load is < 300ms). CPU and RAM are not impacted by those peaks.

Spikes are especially visible in db connections were it can go from 100 connections to 1000 connections for 2 or 3 seconds. Then back to normal.

We have nothing in the PHP log, nothing in the slow query log (long_query_time = 0.1).

Server : Debian / MariaDB 10.3.31, Apache 2.4.38, PHP 7.3.31 All tables are InnoDB with primary keys. Connection by socket. Codeigniter 4.1.7. Redis cache.

What we already try :

Reboot the server / Restart Mysql

Slow query log with long_query_time = 0 for 24h then pt-query-digest on the result. Everything is ok.

General log for 3h when heavy traffic then pt-query-digest on the result. Everything is ok.

Explain on each request of the logs. Everything looks fine.

We no longer know where to look to find the source of the problem.

Additional info:

Environment : VMware virtual machine | CPU : 16x Intel(R) Xeon(R) Gold 6240R CPU @ 2.40GHz | RAM : 31.39 GiB | Disks : SSDs via SAN network

SHOW VARIABLES : https://pastebin.com/fx99mrdt

SHOW GLOBAL STATUTS : https://pastebin.com/NY1PKqpp

SHOW ENGINE INNODB STATUS : https://pastebin.com/bNcKKTYN

MYSQL TUNNER : https://pastebin.com/8gx9Qp1j

EDIT 1:

I am trying to run Oracle db in docker on M1 Mac. I have tried images from both store/oracle/database-enterprise:12.2.0.1-slim and container-registry.oracle.com/database/enterprise:12.2.0.1-slim but getting the same error.

docker run -d -it --name oracle -v $(pwd)/db/oradata:/ORCL store/oracle/database-enterprise:12.2.0.1-slim

I also tried non-slim version and by providing the --platform linux/amd64 to the docker command. Result is same.

Here's the result of docker logs -f oracle

I am working on creating monitoring based on SLO. So far I have been using Google Cloud Monitoring solutions like Dashboards, Alerting and Uptime Checks.

I have noticed GCP has now a Managed Service for Prometheus.

My question is what would be the advantage of using Prometheus(not only Google managed one)for monitoring. Is there anything that could be achieved with Prometheus that I could not achive with Google Cloud Monitoring?

I am trying to create an alias with a filter of an index pattern metrics-* . I was able to do it yesterday and the day before without any problems but I can't do it again today, even if I re-run the same queries as yesterday. I have no problem creating an alias of logs-* . But when I try to create a metrics-* alias, I get an HTTP 400 code with this as response:

Good afternoon all, I should preface this post with the statement that I am pretty new to Python and know enough to get myself into trouble, but not enough to always get out of trouble...this is one of those instances I can't get out.

I am attempting to create a Discord Bot using discord.py that has the ultimate goal of being started from a command in Discord, starts counting the days since the start command was issued, and sends a message to Discord every morning with the count. I also would have a command to reset the count and another to cancel the counter. For testing purposes, I have created code to count minutes instead of days and a task loop of only 10 seconds rather than a full day.

My problem is that I am attempting to use a discord.ext task for the loop, but I clearly don't know how to use it properly, and my research online has not made it any more clear to me. I'm hoping some folks here can steer me in the right direction. I have supplied my code below.

What I expect to happen when I execute my code:

• I issue the $start arg command and the bot sends a message of "It has been X minutes"
• Every 10 seconds the bot sends the same message until 1 minute has passed, then message reads "It has been X+1 minutes"
• Continue looping until canceled

What actually happens:

• I issue the $start arg command and the bot sends a message of "It has been X minutes"
• Nothing else. No other messages or anything happens in Discord, no errors shown in the console.

The code is currently being hosted on replit.com, hence the keep_alive function using UpTimeRobot to keep the bot alive. Something to note, I originally used asyncio.sleep() to just wait to send the new message. This worked fine for shorter periods (like a few minutes to hours) but even with UpTimeRobot doing its thing, I can't get 100% uptime of the Bot and I think whenever the bot went offline for a few minutes, it stopped my counter loop and that was that. This is what lead me to look into Tasks, as I read they can be used to continue loops on reconnection if the bot goes offline for a bit.

I am trying to execute a python script ( which is used for accessing remote machines and run commands ) from Golang, it errors with "exit status 2"

Working with GCP Monitoring, I want to set up an alert based on GCP Uptime Check metric. My alert is working with a threshold above 1 for a duration of 1min.

My problem is that I am getting spam by notifications due to the short duration when the time serie is spiky. But I do want to keep a short duration to get the first notification quickly.

i.e. In the following image:

I am getting a first alert notification at 8:21 (after 1min) over the threshold, Great! But then I will get a resolved notification at 8:22, a new alert notification at 8:23 and finally a resolved notification at 8:28.

So I am getting 4 notifications when I would like to only receive 2. I miss the option to set a threshold duration to fire an alert and another threshold duration to resolve the incident. For my case, I would set 1min duration to fire and only 10min to resolve it.

Can someone help with this issue?

Thank you for your help!