A central tool to monitor multiple solutions via their own API
https://lemmy.world/post/26112791
A central tool to monitor multiple solutions via their own API - Lemmy.World
cross-posted from: https://lemmy.world/post/26112762
[https://lemmy.world/post/26112762] > Hi all > > I have been searching high and
low but I think my search game is too weak. I am looking for a tool (similar to
Uptime Kuma) that can monitor multiple systems via their own APIs, to centralise
the status of these devices. Ex: > > a) I have a sensor system that monitors a
whole bunch of sensors across multiple locations. This system has an API that
uses a secret key + api key for auth, and I can get the status of the sensor via
the api. The idea is that the central dashboard shows the status, if offline,
the control room personnel can log into the sensors system itself and determine
root cause. > > b) I also have a system to which a whole bunch of A/V equipment
is connected, and via it’s API I am able to view the status of multiple devices
on the A/V equipment network. I want to also see on the status of these devices
on my central monitoring system. > > I don’t care about doing root cause
analysis via the central monitoring system, I just want the statuses which can
action a person to check via the control system of that particular service. > >
All my searches come back with hits of systems that can monitor whether my APIs
are up and running, but that is not what I want. Does anyone have any ideas?
Preferably opensource, but definitely self-hosted/on-prem hosting. > TIA
OpenAI O1 model caught in scheming
https://lemmy.world/post/23009638
OpenAI O1 model caught in scheming - Lemmy.World
cross-posted from: https://lemmy.world/post/23009603
[https://lemmy.world/post/23009603] > This is horrifying. But, also sort of
expected it. Link to the full research paper: > > Full pdf
[https://static1.squarespace.com/static/6593e7097565990e65c886fd/t/6751eb240ed3821a0161b45b/1733421863119/in_context_scheming_reasoning_paper.pdf]
OpenAI O1 model caught in scheming
https://lemmy.world/post/23009603
OpenAI O1 model caught in scheming - Lemmy.World
This is horrifying. But, also sort of expected it. Link to the full research
paper: Full pdf
[https://static1.squarespace.com/static/6593e7097565990e65c886fd/t/6751eb240ed3821a0161b45b/1733421863119/in_context_scheming_reasoning_paper.pdf]
Microsoft Outlook can see your SMTP credentials
https://lemmy.world/post/8258754
Microsoft Outlook can see your SMTP credentials - Lemmy.World
Sorry I don’t have an english version of this article, this is the best source I
could find for it.
https://www-heise-de.translate.goog/news/Microsoft-krallt-sich-Zugangsdaten-Achtung-vorm-neuen-Outlook-9357691.html?_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=de
[https://www-heise-de.translate.goog/news/Microsoft-krallt-sich-Zugangsdaten-Achtung-vorm-neuen-Outlook-9357691.html?_x_tr_sl=de&_x_tr_tl=en&_x_tr_hl=de]
Clarity on environments - Lemmy.World
Hi everyone I have read through the documentation now several times, and I just
want to soundboard something with someone. Regarding the environments we can set
up. Is this meant for example as a production cluster and a dev cluster? And if
so, is it possible to put a docker swarm cluster in there? I don’t see how
gitlab will ‘know’ how to deploy an application to docker swarm? What am I
missing? Or am I better off just deploying “manually” via the CI/CD pipeline
like I am doing now? TIA
SOLVED: Using CI/CD Variables in project files
https://lemmy.world/post/2962049
SOLVED: Using CI/CD Variables in project files - Lemmy.World
Hi community I have a pipeline where a stack (service) is deployed to my docker
swarm. I want to use $CI_PROJECT_NAME in my docker service definition file to
define the docker service name. But it seems the variable is not being expanded,
or something else is wrong. I need to have a generic yml so I can distribute
this to all devs and they don’t have to change anything. Example of what I am
trying to achieve: version: '3.9' services: $CI_PROJECT_NAME: image:
myregistry/devops1/$CI_PROJECT_NAME/$CI_PROJECT_NAME:latest deploy: replicas: 3
endpoint_mode: dnsrr update_config: parallelism: 1 delay: 3s order: start-first
failure_action: rollback monitor: 1m restart_policy: max_attempts: 3 placement:
max_replicas_per_node: 1 networks: - microservices volumes: -
apache-logs:/var/log/ networks: microservices: external: true volumes:
apache-logs: driver: local driver_opts: o: bind device:
/mnt/swarm_shared/services/$CI_PROJECT_NAME type: none I know this is not a
docker forum, but was thinking the issue is with my pipeline rather than my
docker compose file. I would appreciate any help I can get. TIA EDIT: As per
this community post
[https://forum.gitlab.com/t/use-ci-variables-in-other-files/72548/2] I used a
sed replacement command to solve my problem. Ugly, but functional. Thanks for
the input!
