We created an uptime check for our website in Google Cloud Platform:
We don't need the uptime check at the moment, but we might need it again in the future. We saw that there is an option to delete it. However, then we will need to re-create it in the future. Does there exist an option to disable uptime check temporarily and then enable it again when needed?
No.
It's a reasonable need.
There's seemingly no way to "hack" an equivalent to disabled either i.e. by having a zero (never) period or no selectedRegions see UptimeCheckConfig.
Consider filing a feature request on Google's public issue tracker for Monitoring.
The list of issues including uptime
Related
I'm trying to temporarily disable performance insights for an RDS MySQL t4g instance (which is using the latest MySQL version and has performance insights already enabled and in effect). The RDS documentation describes a "Performance Insights" section where this can be toggled, which I remember using when setting up the instance:
But this section is entirely missing when I go to the "Modify" view from the instance page. This is true even when I click on the option to "Modify retention tier" from the performance insights page directly:
Also (and I'm only mentioning this as possibly another effect of the same underlying issue), when I've visited the insights page for this instance in the past couple days, about 2 out of 3 times all the performance insight data over any timespan just appears as NaN, even after a system update and multiple reboots.
I do get these metrics to appear if I hard refresh enough times, but for another instance it always shows up right away.
I have combed over the entire performance insights documentation and have not found any reason why this section wouldn't appear, but I feel like I'm missing something that would be causing this to happen. Is there anywhere else I should be looking?
EDIT: I just tried to change a different (unrelated) setting on the same instance and got this message that my instance with already-enabled performance insights doesn't support performance insights, so I have to disable it...when I don't even have the option!
there are some metrics in GCP's Stackdriver like f.e. serviceruntime.googleapis.com/quota/exceeded that appear when there is a problem and are absent (not 0) if there is no more problem.
The problem is I cannot set up alerting to auto-resolve, because when the problem is resolved data for this metric is absent.
How can I set up alerts to auto-resolve with these types of metrics?
Unfortunately, there's no solution at the moment. Google Engineers are aware about this problem. You can join (use +1 mark), comment and follow the feature request at the Google Public Issue Tracker to be updated of any changes.
The title pretty much says it all, but just to clarify:
Redis afaik has a performance metric mem_fragmentation_ratio, giving the ratio of memory used as seen by the OS (used_memory_rss) to memory allocated by Redis (used_memory).
Is it possible to find this metric (or calculate it using other existing metrics) in Cloud Monitoring?
Unfortunately the answer is no. Only the GCP support team is able to verify this metric with their internal tools :(, nevertheless, I found this Public Issue tracker that is requesting to add this metric to monitor the instance. I suggest you do a comment and start the issue so you can get notifications about this :)
on the other hand, about the calculation, I found this link. It seems that the formula is:
MemoryFragmentationRatio= Used_Memory_RSS / Used_Memory
With the command "info all" you can get these values.
I really hope that the aforementioned information helps you.
Today (15/06/2018) we found two reserved addresses were disassociated from two GCE instances.
Nobody ordered this disassociation, in fact in the activity logs we do not found any activity on this two reserved addresses.
We manually re-associate the two reserved addresses to our machines to solve the problem.
Is it possible to know what happened?
Good sources to see what happened are the "Activity" tab in the Cloud Console as well as the AuditLog entries in Stackdriver Logging. If it is still not clear what happened based on that, please file a support case for further investigation.
If your instances were in the stopped state at the time it may be related to this incident:
https://status.cloud.google.com/incident/compute/18005
By reading this link I ran the following advanced filter from Stackdriver:
resource.type="gce_instance"
jsonPayload.event_subtype="compute.instances.deleteAccessConfig"
This filter shows the actor (user or a service account) and the event type (how it happened).
If you need further information, I would suggest filling an issue here.
We run only a small handful of instances on Google Cloud Platform and we don't run them all the time. Generally we just fire one up, do what we need to do then shut it down... which is great, except when "we" forget to shut them down.
I've been able to track down the relevant REST APIs and the gcloud sdk but I don't see anything that says who started the instance. Actually it also doesn't have a timestamp on when it was started.
I did find this python app engine script that I might be able to rewrite to stop the instances after X amount of time, but I'd rather find a way to notify the user who started it and let them know the instance is still running.
Has anyone tried to do something similar or seen a way to get the "starter" of the instance in GCP?
You can look into the Audit Logs to determine who did what, where, and when. Further, you can use the Stackdriver Logging API method entries.list to retrieve audit log entries for your use case.
Also you can choose use the Activity Logs to know the details such as the authorized user who made the API request.
With the new API you have to filter on the following:
resource.type="gce_instance"
resource.labels.instance_id="ID"
protoPayload.methodName="v1.compute.instances.start"