I am looking to forward integrate NewRelic Agent with Existing Cloudify 2.7 Environment.
Since Cloudify apps are running in individual paths and each deployment takes to apps running on different paths, it's not possible to assign the app server to newrelic. How can I over come this?
It's not entirely clear what you are trying to accomplish.
You recipe can install the NewRelic agent and configure it to connect to NewRelic.
Alternatively, if the NewRelic agent has an API or CLI, you can add a
monitors{
}
section to your recipe. This section will collect the required stats from the local agent and publish them to the Cloudify Manager.
More information is available here: http://getcloudify.org/guide/2.7/plugins_and_probes/probes.html
The collected monitors are then available using the Manager REST API. You can then use a separate process to poll the metrics from the manager API and send them to NewRelic. Look at: http://getcloudify.org/guide/2.7/restapi/restdoclet.html
and the API at
/{version}/deployments/{appName}/service/{serviceName}/instances/{instanceId}/metrics
Related
I want to read my Msbuild path from my self hosted build agent as system defined capabilities, is there any way out to do so ?
You can get that information by leveraging the Agents - Get API call and specifying includeCapabilities=true on the parameter list.
Worth noting that if you add new capabilities (like installing nodejs for example), you will have to restart the agent for the capabilities to show available.
I had deployed the app last on friday and it got deployed successfully.But since, today morning the deployment is not happening at all.It is checking for conflicting process and failing.
I'm doing this from the webide and i'm not able to check what are the conflicting process and how to resolve it.
WebIDE lacks the ability to do proper investigation on deploying apps to SAP Cloud Foundry.
The best way to do this is to install the Cloud Foundry Multi-apps plugin (see this tutorial). This will allow you to use the local terminal to control the deployment (or alternatively use SAP Business Application Studio which already has the commands built in).
Then use the command cf mta-ops to get the list of ongoing operations and cf dmol <operation_id> to download the logs for that operation. cf deploy can be used to abort/retry operations.
We are developing an application in which we need to integrate different cloud services. We need to connect to VmWare VCenter server and should do the provisioning. Is there any Rest API calls to execute the task?
Thanks.....
Since this question was asked and answered VMware has released a vCenter REST API for version 6.5:
The VMware vSphere Automation SDKs provide support for your client application infrastructure with services to perform management operations in your vSphere environment. The vSphere Automation SDK for REST also contains samples to demonstrate how to use the new APIs.
The version 6.5 SDK enables programmatic access to the following
services:
Session management
Tagging
Content Library
Virtual Machines
vCenter Server Appliance management
Read more:
vSphere Automation SDK for REST 6.5 Release Notes
http://creativeview.co.uk/VMware-vCenter-REST-API-Part-1/
Currently, the vSphere API is largely SOAP based.
The simplest way to consume our API is via one of the existing SDKs.
For example, you can use the Python SDK (https://github.com/vmware/pyvmomi) to perform most vSphere functions via the Python library.
Alternatively, you can use a configuration management platform like Chef via the vSphere specific plugin. For Chef, there is a vSphere Knife: https://github.com/chef-partners/knife-vsphere
If you tell us more about the problem you are trying to solve and the tools you are using, we can give you a more detailed answer.
I have looked at the options in the portal and also the resource group templates, but could not find a way to customize this list.
Also, is it possible to add custom perf counters (assuming the code already creates them) for monitoring in the service fabric application?
There is no integrated way to do this today, but there are three ways to do this:
Use Application Insights to monitor your application. There are some
details of how to do this with Application Insights that are not Service
Fabric specific here. There is also a project on GitHub that shows
how to integrate Azure Service Fabric with Application Insights.
Collect performance counters using Azure Diagnostics. Service Fabric is running on VMs, configuring diagnostics to collection from
an Azure VM can be found here.
Use Operations Management Suite which can also collect standard and custom performance counters. See links in the post below (I'm not allowed to post more than 2 links)
You could also try this approach: Setting up Application Insights for your Service Fabric application
I have clusted the WSO2 API Manager 1.8 and implemented deployment synchronization according to this guide which is given in the WSO2 documentaion. Everything happens to work find except one thing.
Let's assume that we have below 2 instances running API Manager.
192.168.X.123 - API Manager 1
192.168.X.124 - API Manager 2
The problem is once I create and publish an API on API Manager 1 it does appear on API Manager 2 in the publisher. But the particular API does not appear on the API Manager 2 Store.
Also note that I'm using a shared MySQL database for the API Manager cluster(API Manager 1 and 2). I checked the logs but does not contains any error.
How can I fix this?
Please look at WSO2 Clustering and Deployment Guide. Please check the docs on Clustering API Manager and SVN-based Deployment Synchronizer
If all configurations are correct, your API should be displayed in Store once you have "Published" the API. It might take some time (may be few minutes) to appear in Store due to indexing etc.
In our situation, we defined 2 different servers with extra CPU and
memory, on these servers we have installed the full WSO2 API Manager
and defined the cluster configuration. Everything provisioned via
Puppet.
Just a straightforward install, all data-source pointing to one schema
in an Oracle database.
And...it is working; Our Developers happy, Operations happy, Architect
department happy
From WSO2 API Manager Clustering configuration