PrtgAPI VS Chocolatey

Alternatively you could check this is something that https://github.com/lordmilko/PrtgAPI can make a little bit easier since it abstracts a lot of the complexity of interacting with the API.

Not sure if there's a way to do this exactly within PRTG but I know you could write up some logic to report what you're looking for using the PrtgAPI PowerShell module, https://github.com/lordmilko/PrtgAPI

Or if you wanna script it with powershell: https://github.com/lordmilko/PrtgAPI

I don't use the built in reports from PRTG but I've written some custom reporting tools using the PowerShell module, prtgapi (https://github.com/lordmilko/PrtgAPI) which could get you what you're looking for.

If you are using a windows to manage it, you can also use the Powershell Module (https://github.com/lordmilko/PrtgAPI).

I ran across this https://github.com/lordmilko/PrtgAPI which I am trying to figure out how to leverage to create a script to run on hosts to schedule downtime for 2 hours. We use BigFix to patch Windows so I was going to try and get a script to run on each host, part of the patch deployment, to schedule 2 hours downtime which should be sufficient for patching. Our maintenance windows are constantly moving so setting up the maintenance schedules in PRTG seems to be more administration work.

I'm not sure if there is another way over the webinterface, but you can use LordMilko's PrtgAPI: https://github.com/lordmilko/PrtgAPI

You should hopefully be able to automate most (if not all) of what you're doing using PrtgAPI. While PrtgAPI's support for working with schedules is not as full featured as most other aspects, I believe you should be able to perform this migration by doing the following

You may want to look into the Powershell PrtgApi module, https://github.com/lordmilko/PrtgAPI . I have several scripts using this that allow me to update settings per sensor name/type. It's not quite officially supported by Paessler but it's well maintained and at least acknowledged by Paessler as a useful tool.

Chocolatey Windows software management solution, we use this for installing Python and Deno

Authenticating with Kyma is a (in my opinion) unnecessary challenge as it leverages the OIDC-login plugin for kubectl. You find a description of the setup here. This works fine when on a Mac but can give you some headaches on a Windows and on Linux machine especially when combined with restrictive setups in corporate environments. For Windows I can only recommend installing krew via chocolatey and then install the OIDC plugin via kubectl krew install oidc-login. At least for me that was the only way to get this working on Windows.

On a Windows machine, you can use Chocolatey by running the command.

I've used WSL2 and GHC/Nix--worked without any issues. However, there is Chocolatey: https://chocolatey.org/

For OSX there is homebrew or pyenv (pyenv is another solution on Linux). As pyenv compiles from source it will require setting up XCode (the Apple IDE) tools to support this which can be pretty bulky. Windows users have chocolatey but the issue there is it works off the binaries. That means it won't have the latest security release available since those are source only. Conda is also another solution which can be picked up by Visual Studio Code as available versions of Python making development easier. In the end it might be best to consider using WSL on Windows for installing a Linux version and using that instead.

Type the following commands on the Windows terminal to install helm. You can use either Scoop a command-line installer for Windows or Chocolatey which is a Package Manager for Windows to install helm.

Für Software ninite.com und chocolatey.org

While you can install it in many ways, the easiest is using a package manager like Homebrew for macOS or chocolatey for Windows.