I am trying to set up a custom dashboard for my Compute Engine instances. One of the metrics that I want to report on is the amount of free disk space available on each VM. I noticed that "disk bytes used" is one of the available metrics but it is not actually available to me to select unless I disable the "Only Show Active" metrics.
I have the "OS Agent" (recently released) installed and running on the VMs.
I can't seem to find any documentation referencing this particular metric and how to get it working.
Has anyone tried this and figured out the magic solution?
Here is what I did in order to get the metrics working in a replicated environment:
1.-I created 2 GCE instances (Debian and RedHat).
Navigate to the Monitoring section, and select Dashboards.
3.- Select the VM Instances Dashboard from the Dashboard List.
4.- From the Instances section, I selected both instances and clicked on Install Agents; it will open the Cloud Shell VM and auto populate the command to install the Ops Agent.
5.- You might need to wait up to 10 minutes to get the agents connected to the Monitoring Dashboard.
6.- Once you see the Ops Agent running on the instances, select the Infrastructure Summary Dashboard.
7.- Scroll down the Dashboard, and you will see the Top Disk Used (Agent) section populated.
If you prefer, you can also create a custom Dashboard.
On the Left Panel, navigate to the Metrics Explorer section.
In the Resource type, select VM Instance (gce_instance), and, at the bottom, unselect the “Only show active” checkbox.
In the Metric dropdown, menu select Disk Usage, and also unselect the “Only show active” checkbox.
4.- You need to wait at least 1 minute to see the chart populated.
Here is the full list of metrics accepted for gce_compute
Related
If yes then how to use that alert? And If it is not available then How to create an custom alert for getting cluster CPU utilization through ambari?
Ambari alerts are tied to services. Many services already have alerts for CPU utilization on nodes which run certain components. For instance Yarn has a ResourceManager CPU Utilization alert. This alert will be setup for any node running the YARN/RESOURCEMANAGER component. HBase has a similar alert HBase Master CPU Utilization which would be setup on nodes running HBASE/MASTER component.
It's not clear from your question what your cluster layout is nor how many nodes your cluster consists of. So I can't give you a definitive answer for your setup.
In general, if you had a component on every node in your cluster you could set up an alert for that component that monitors CPU Utilization. If you don't have a component on every node, then you would have to set up several such alerts across components to achieve what you want.
You can add or alter alerts via the Ambari UI by clicking the Alerts tab. In that view you can adjust alert notifications and alert settings by clicking the actions button and selecting the corresponding item from the drop down.
So I am facing this problem,whereby,whenever I stop my MySql server(which is using an EC2 free-tiered micro instance), I would have my non-root users passwords changed!! by itself.
I need to reset their respective passwords everytime I stop and reboot my MySql EC2 instance.
See the following screenshot:
Perform the Image / Create Image functionality. Give it a meaningful image name and description. For description, help yourself later by being as verbose as possible like "from 20160401 build plus Scala 2.12 and vsfptd configured". The request to save the custom AMI will be received and may take a short time to complete. Typically when you are just starting with small instances, it will be completed in a few minutes. When completed, it will be visible in the left pane under Images / AMIs.
See the AWS Manual page entitled Step 3: Deploy Your App at the bottom. The section "Create a Custom AMI".
In short, without saving your work and the current state of your server, all work is lost by a stop and reboot. You need to manage, cleanup, and discard prior AMI instances that cause confusion later. That is why the description field is your best friend. Naturally only discard things not of value.
I have used Google Compute Engine for my backend (debian-lamp), suddenly it gets deleted automatically without any user interaction and also doesn't shows the operation(Deletion of VM Instance ) performed by which user. I have also attached the image of Google Compute Engine Operations for further study.
I want to know why does this happened and what are the ways to restore the deleted instance.
Note: I am using trial version of Google Compute Engine and this was my second VM Instance created in Current Project.
It looks like the instance was deleted by the Instance Group Manager after you resized the instance group (most likely to zero). To learn about why this happened, visit the docs pages for Instance Groups and the Instance Group Manager.
If you resize the Instance Group back up to 1, the Instance Group Manager will create a new VM automatically.
I attempted to start a VM instance using a predefined disk in zone europe-west1-a. I have been using the disk for a number of weeks. The VM startup never completed (the start activity did not complete and the instance never appeared in the VM list - so presumably the VM failed to startup).
When I tried to start the VM a second time, the disk was no longer available. The disk is also not listed under the "Disks" tab of compute engine.
I have bronze support package, so can't create a ticket with google.
Any suggestions on what to do?
You should send a question about this using the grey "Send feedback" link at the bottom right of Developers Console page. This may require looking at the logs for your specific project/account and is not something that we can solve here on StackOverflow.
I know is not possible with Couchbase 2.2, but is it possible to change the number of replicas on 2.5 ?
Thank you
Yes, you can change the replica count in 2.5 from the web console. The steps are listed below.
Click on the Data Buckets link.
Click the arrow to the left of the bucket name to expand the bucket details.
Click the Edit button.
The replica count appears in the Replicas section. Change the quantity there.
Click Save.
Click the Server Nodes link. After a short time (refresh if necessary), you will see a red message indicating that a rebalance is required. Rebalance your cluster from the button on that page. A rebalance is required so that Couchbase can distribute the new set of replica documents across the cluster.
You can also find info about a 'working but not officially supported' way to change the settings in 2.2 at https://groups.google.com/forum/#!topic/couchbase/ClqBDavQIkk.