With most users moving toward cloud-based deployments, will the Nagios / Ganglia plugin continue to be supported?
As of 8.12.x, support for our Nagios/Ganglia Reporting and Monitoring plugin will be deprecated. The plugin will no longer be built or distributed. The installer packages for older versions of the plugin will continue to be available on our archive page.
Standalone system monitoring via Ganglia/Nagios is not affected by this change. You can also choose to use other options, such as Prometheus, Grafana, or cloud-provided services.
Related
Hey guys I was trying out Fleet and really liked it but I had a hard time configuring it. I wanted to install a plugin but I couldn't find an option to add plugin anywhere.
Does anyone know how to install plugins in JetBrains Fleet?
I wanted to install a plugin but I couldn't find an option to add plugin anywhere.
That's because Fleet does not support custom (non-bundled) plugins yet (as of October 2022).
https://www.jetbrains.com/fleet/
Does Fleet support plugins?
Fleet will have its own extensibility model, and we are also looking into the option of re-using existing IntelliJ-platform plugins for Fleet. We will provide more information about these extensibility options at a later date.
https://blog.jetbrains.com/fleet/2022/10/introducing-the-fleet-public-preview/
At the same time, we’re working in the following areas:
API support and an SDK for plugin authors – Given that Fleet has a distributed architecture, we need to work on simplifying the approach for plugin authors. While we guarantee that we’ll be providing a platform for extending Fleet, we do ask for a bit more patience in this area.
with latest fleet preview, you could install plugins manually, e.g: use the famous vim plugin for fleet as an example:
download the latest zip from https://plugins.jetbrains.com/plugin/20568-fleetvim/versions#tabs
unzip the download file
copy the unzipped dir to the plugin dir of jetbrain fleet app, I installed the latest fleet preview by jetbrian toolbox, and the cp command would be:
cp -af ~/path/to/download/fleet.fleetVim-1.13.95 "~/Library/Application Support/JetBrains/Toolbox/apps/Fleet/ch-1/1.13.92/Fleet.app/Contents/Frameworks/FleetBackend 2023.1 EAP.app/Contents/plugins/"
restart the fleet app and choose Enable vim emulation from the General tab of the fleet app preference.
There's no information on how to install it, but I notice that the Svelte plugin claims to be Fleet compatible:
https://plugins.jetbrains.com/plugin/20504-svelte/
Fleet doesn't support plugins yet. JetBrain Fleet page
Sorry, screenshot is in French
We build our web app with Azure DevOps pipelines and deploy into Azure with an Azure DevOps release. I think today netcore got updated to netcore 3.1.4 on our build agent. But now our Azure DevOps deployment fails, because the netcore 3.1.4 runtime is not yet installed on our app service in Azure.
The error message we are getting:
Could not find 'aspnetcorev2_inprocess.dll'. Exception message:
It was not possible to find any compatible framework version
The framework 'Microsoft.AspNetCore.App', version '3.1.4' was not found.
- The following frameworks were found:
2.2.8 at [D:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
3.0.3 at [D:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
3.1.1 at [D:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
3.1.3 at [D:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
You can resolve the problem by installing the specified framework and/or SDK.
This makes sense and can happen, but what is the best way to go about fixing this?
I could fix my build to a specific netcore version. But I don't like this, because we do want to keep updating to newer versions, but we don't want a version that is not available in Azure app service.
Am I correct in thinking that we would have to install our services self contained, because otherwise we could get into this issue more often when Azure DevOps is faster with installing patches than Azure?
Or is there a way to force update Azure app service to the new netcore 3.1.4 security patch which would be ideal I think?
I just need some guidance in what is the best approach to fix this issue?
Or is there a way to force update Azure app service to the new netcore 3.1.4 security patch which would be ideal I think?
AFAIK, there is no such a way to force update Azure app service to the new netcore 3.1.4.
We could keep track on the latest releases on the https://aspnetcoreon.azurewebsites.net/, but we could not update it at this moment.
To resolve this issue, we recommend that you publish your app as self-contained produces an application, which includes the .NET Core runtime and libraries, and your application and its dependencies. Users of the application can run it on a machine that doesn't have the .NET Core runtime installed.
Publishing your app as self-contained produces a platform-specific executable. The output publishing folder contains all components of the app, including the .NET Core libraries and target runtime. The app is isolated from other .NET Core apps and doesn't use a locally installed shared runtime. The user of your app isn't required to download and install .NET Core.
You could check this document .NET Core application publishing overview for some more details.
Hope this helps.
If you want version of netcore to be automatically updated as an updated version is available, building our service as self-container seems like a good option: no need to have anything installed on the machine running (ie the version on Azure DevOps and Azure Web App don't have to match).
The main downside of this approach is that the build is going to less deterministic: running your build twice with on the same commit might create different binaries depending on what is currently install on the build agent. if you want to know more, here is an interesting post arguing about why deterministic build is important.
To keep the build determinitic, you can use the Use .Net Core task at the beginning of the build (that will make sure that the desired version of the dotnet sdk is on the agent). You could also add a global.json in your repository to lock for both the build on your dev box and in Azure Dev Ops.
This is a common topic of discussion, and you can find a lot of blogs advocating one or another side.
There were big discussions started when Microsoft released LTS net core 3.1 and it took some time before Azure start supporting the 3.1 runtime as well.
You could find a lot of blogs strongly suggesting to deploy your web apps as self-contained (runtime is ~100MB in size) and cut loose the dependency towards Microsoft supporting the latest runtime. While others advocate that the applications should remain as light weight as possible and the runtime should be set in the pipeline. But that is still up on you. I, myself prefer to deploy self-contained apps after my bad experience with net-core 3.1.
There is no established best practice.
In the past , I've run into the same situation, you can fix this by manually setting the value from RunTime Stack drop down. If you manually update the build processes .yml file
RuntimeStack: 'DOTNETCORE|3.1'
Do I miss something or there is no support for deployment of Node.js apps in Gcloud App Engine?
I found a separate plugin for php, full support for java in the plugin Google Cloud Tools but nothing on Node.js.
In java you just check a box and you got app.yaml automatically build, uploading and running and debugging tools, integration with API, everything you need.
I can't find how to enable this tools for a standard Express app so I hope I'm missing something.
Unfortunately Google Cloud Tools for IntelliJ does not currently support non-Java based App Engine runtimes. We may add support eventually but we have no concrete plans to do so at the moment.
I am planning to execute spark from KNIME analytics platform. For this I need to install KNIME spark executors in the KNIME analytics platform.
Can any one please let me know how to install KNIME spark executors in the KNIME analytics platform for hadoop distribution CDH 5.10.X.
I am referring the installation guide from the below link:
https://www.knime.org/knime-spark-executor
I could successfully configure/integrate spark in KNIME.
I did it in CDH 5.7.
I followed the following steps:
1.Downloaded knime-full_3.3.2.linux.gtk.x86_64.tar.gz.
2.Exract the above mentioned pacakge and run installation for KNIME.
3.After KNIME is installed goto File ->Install KNIME Extensions -> Install Bigdata extensions(Check all the Spark related extensions and proceed).
Follow this link:
https://tech.knime.org/installation-instructions#download
4.Till now only the Bigdata related extensions have been installed but they need license to be functional.
5.License needs to be purchased.However,free trail for 30 days can be availed after which it needs to be purchased.
Folow this link :
https://www.knime.org/knime-spark-executor
6.After plugins are installed we need to configure Spark-job-server.
For that we need to download the compatible version of spark-job-server for the hadoop version we have.
Folow this link for version of spark-job-server and its compatible version :
https://www.knime.org/knime-spark-executor
I'm pretty sure it's as easy as registering for the free trial (and buying the license for longer than 30 days) and then installing the software from the Help->Install New Software menu.
As of version KNIME 3.6 (latest), it should be possible to connect to Spark via Livy, no specific executor deployment on a KNIME Server. Still in preview, but it should do it.
https://www.knime.com/whats-new-in-knime-36
As far as I know, it is possible to have multiple Azure SDK versions (2.1, 2.2, 2.3 etc.) on a single machine, and reference specific versions of the Azure assemblies as desired (from the Visual Studio project or so).
Though, how to manage different installations of Azure Emulators (Compute, Storage)? Is it possible to install more of them, then choose a specific one - when debugging the piece of software?
Is it possible to install more of them, then choose a specific one -
when debugging the piece of software?
AFAIK, this is not possible. At any given point of time, there can be only one version of emulator installed on a machine.