I Have Build and Deploy Ignite Web Console Locally.And Start Manager Console on http://localhost:9000/ But problem is there no Monitoring Option Available.Can Anybody Explain How To Monitor Apache Ignite Locally via Web Console
This is catch monitoring tab is only available in grid gain hosted ingite web console.
so frustrating but I also got same issue.
http://apache-ignite-users.70518.x6.nabble.com/Setup-Web-agent-and-Web-console-on-locally-td8341.html
According to documentation, this is an enterprise feature and not available in the open-source version.
https://apacheignite-tools.readme.io/docs/ignite-web-console
The web console also features cluster monitoring functionality (available separately as GridGain plugin) that shows various cache and node metrics as well as CPU and heap usage.
If you have the enterprise edition, it should be possible to deploy your own instance for monitoring. The following documentation contains more details.
http://docs.gridgain.com/docs/deploy-web-console-from-docker-image
Related
Generally I've had pretty good luck with Application Insights' auto-detection of a SQL dependency. However, in a recent case where we added Application Insights to a Web API project, we are not seeing dependency tracking for SQL Server in the portal. Version info:
Application Insights 2.5.0
Entity Framework 6.x
.NET 4.5.2
The funny thing is that Azure will automatically pick up SQL calls when developers are using the debugger from Visual Studio. What do we need to do to capture timings for SQL calls on a real environment?
Thanks,
BGU
The solution was to upgrade the Web API project to a more recent version of .NET (4.6 or higher). Good luck out there.
https://learn.microsoft.com/en-us/azure/application-insights/app-insights-monitor-performance-live-website-now
Dependency diagnostics like full sql command text will be available in Application insights only at runtime. If web api project is hosted on IIS server, then try integrating your web application virtual directory to app insights resource using status monitor. Once you do that, it will push full sql command text to d app insights portal.Comparison Build time and run time integration
We have some ASP.NET web application which used in 2 ways:
enterprise solution (msi-like installer)
cloud solution (use same installer)
Currently we use home-grown installer, but consider if we can replace it with something more convenient and suitable for CI/CD development cycle.
What technologies/products can be used? Currently I think about webdeploy, but not sure how it can be applied for enterprise setup...
This is quite a broad question, but I think it deserves an answer.
1. (partially) Open source solution
One way to configure CI cycle is to use Jenkins along with MS deployment functionality. This article shows how to quickly set up a job to integrate Jenkins with msdeploy tool.
Basically it configures a job to perform the deployment using Powershell:
msdeploy.exe -allowUntrusted=true -verb:sync -source:contentpath='D:\WS\ExampleProject' -dest:contentpath=F:\webfolder,computerName=exampleproject.example.com,Username='yourdomain\username',Password='password' -skip:objectName=dirPath,absolutePath="config" -skip:objectName=filePath,absolutePath="web.config"
It also tells that the executing user should be an administrator on target server, but this can be circumvented through proper configuration of Web Deployment Handler as indicated in this article.
One intermediary step that can be done before Jenkins integration (which I recommend) is to configure Web deployment. This allows to quickly check that deployment can be performed onto target server IIS using Visual Studio and any configured user that is allowed to deploy. It also allows to quickly see the difference between current code base (web pages, JS files, binaries) and target server deployed package.
2. Visual Studio 2017 DevOps solution
Microsoft recently released VS 2017 which contains a great support for DevOps which handles most the issues related to CI/CD. I cannot find a reference, but I remember that this feature is available for Enterprise version only. Also, the good news is that it is not tightened to Microsoft technologies.
A presentation related to the subject can be found here.
I think WebDeploy can be used without significant problems. From my experience with it:
backup limitation: can be done only at Web Site level, not Web application level
deployment time: is quite small - actual files copy + Web site backup (if configured) + application pool recycle.
Recently I saw a vendor offering customers who wanted on-premises deployments the same Docker image that they use for cloud deployments. Seemed like a good, clean, solution.
Another option is nuget packages - host your own repository. Then deploy with a tool like Octopus Deploy. I'm not terribly familiar with it, but both solutions look to be easy after an initial hump in setup.
I try to monitor my jdbc requests with ApplicationInsights, already added the SDK to my Java app, works fine with request monitoring.
All I found was to "Install the Application Insights agent for Java" but how should I do this on App Services-Resource? I think I cannot change the startup script.
Regards
In an Azure Web App environment, where you don't have the ability to modify the application server's startup script, installing the Java agent isn't possible and therefore this scenario isn't supported.
There is currently no workaround for this unfortunately.
Thanks,
Harel
Can anyone provide insights of using Jenkins for automating deployment under controlled and uncontrolled enviroments. We have different environments - dev/qa/uat/prod and currently we are using batch files that call msbuild/nant scripts to deploy on web and DB servers (web farm). Developers only have access to dev/qa and production support will deploy on uat/prod. Prod. support will get the source code from SVN tag folder and run the batch file to deploy the application.
By using Jenkins, is it possible to eliminate the step of prod. support team getting the script from SVN by running the jobs using their credentials via url. And what is the general practice using source control and CI tool for deploying applications.
My recommendation is to reserve Jenkins for just building the software. That way the user of Jenkins only have access to development and perhaps QA systems.
To decouple the build system from the process that deploys the software I recommend the use of a binary repository manager like:
Nexus
Artifactory
Archiva
In that way deployment scripts could retrieve any version of a previous build. The use of a repository manager would enable your QA team to certify a release prior to it's deployment onto production.
Finally, consider one of the emerging deployment automation tools. Tools like Chef, Puppet, Rundeck can be used to further version control the configuration of your infrastructure.
I want to build a service to provide console access (eg. xm console domain) via a web browser to Xen virtual machines. Does such a program already exist? If not, where should I start?
Slicehost offers this service. I'm just wondering how to go about cloning it or using whatever software that they did.
Slicehost built their web console using AjaxTerm.