Meta tags:

Headings (most frequently used words):

health, state, vm, of, changes, viewing, logs, console, gcloud, rest, for, mig, and, pricing, change, log, monitoring, vms, checking, autohealing, monitor, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, before, you, begin, use, cases, project, or, specific, format, entries, all, in, identifying, that, frequently, go, unhealthy, what, caused, an, attempt, if, succeeded, determining, initial, delay, value, products, support, resources, engage, entry, example,

Text of the page (most frequently used words):
the (290), and (188), for (132), create (128), vms (109), instance (108), logs (86), with (81), #health (73), troubleshoot (63), compute (62), about (61), state (60), view (58), mig (55), cloud (49), use (49), you (47), manage (46), set (45), using (45), google (44), type (43), disk (43), query (39), server (39), instances (35), disks (35), resource (34), googleapis (33), com (33), configure (33), windows (33), change (32), following (32), overview (32), projects (31), managed (31), performance (30), project (29), metric (29), changes (28), from (28), monitor (28), that (27), log (27), engine (27), reservation (27), project_id (26), your (25), name (25), network (25), explorer (23), access (23), click (22), hyperdisk (21), machine (21), sql (21), jsonpayload (20), instancehealthstatechange (20), group (20), images (20), logname (19), based (19), instance_name (18), console (18), gcloud (18), gpu (18), resources (17), labels (17), can (17), add (17), entries (17), image (17), linux (17), policies (16), time (16), 2finstance_group_manager_events (16), autohealing (16), configuration (16), application (16), reservations (16), all (15), gce_instance_group_manager (15), snapshots (15), groups (15), ssh (15), recommendations (15), logging (14), workload (14), creation (14), host (14), load (14), virtual (14), apply (14), custom (14), connect (14), metrics (13), label (13), specific (13), storage (13), management (13), bulk (13), microsoft (13), cluster (13), enter (12), zones (12), sole (12), availability (12), persistent (12), best (12), regional (12), information (11), this (11), boot (11), run (11), operations (11), command (11), delete (11), practices (11), workloads (11), stateful (11), see (10), healthy (10), request (10), between (10), repair (10), example (10), list (10), install (10), metadata (10), migs (10), machines (10), attached (10), migrate (10), page (9), operation (9), which (9), monitoring (9), cli (9), update (9), licenses (9), tenant (9), multiple (9), openshift (9), shutdown (9), start (9), hpc (9), samples (8), more (8), license (8), builder (8), how (8), find (8), unhealthy (8), field (8), local (8), read (8), authentication (8), service (8), import (8), cpu (8), login (8), optimize (8), internal (8), choose (8), disaster (8), recovery (8), high (8), agent (8), existing (8), guest (8), keys (8), h4d (8), flexibility (8), dns (8), optimized (8), tpu (8), thumb (7), timestamp (7), insert (7), detailedhealthstate (7), results (7), protopayload (7), when (7), displays (7), filter (7), mig_name (7), states (7), rest (7), applications (7), data (7), networking (7), commitments (7), startup (7), balancing (7), benchmark (7), enable (7), manually (7), idle (7), addresses (7), scale (7), deploy (7), back (7), mysql (7), zonal (7), remove (7), maintenance (7), templates (7), snapshot (7), backup (7), events (6), code (6), content (6), are (6), send (6), after (6), attempt (6), out (6), will (6), number (6), instance_group_manager_name (6), creating (6), build (6), check (6), types (6), token (6), json (6), manager (6), identity (6), options (6), default (6), usage (6), security (6), migration (6), updates (6), instant (6), files (6), nested (6), gpus (6), across (6), mode (6), demand (6), pools (6), failover (6), extension (6), new (6), transfer (6), customized (6), spot (6), understand (5), down (5), under (5), details (5), get (5), value (5), initial (5), delay (5), first (5), make (5), created (5), string (5), location (5), global (5), entry (5), url (5), issues (5), want (5), testing (5), oauth2_token (5), post (5), limit (5), uses (5), environment (5), region (5), zone (5), review (5), databases (5), accounts (5), errors (5), future (5), drivers (5), virtualization (5), nvidia (5), placement (5), node (5), highly (5), available (5), multi (5), modify (5), capacity (5), schedules (5), audit (5), symphony (5), email (5), scripts (5), operating (5), systems (5), enhanced (5), capabilities (5), stop (5), tenancy (5), restore (5), regions (5), control (5), workstation (5), faq (5), flex (5), português (4), español (4), sign (4), support (4), pricing (4), other (4), its (4), event (4), part (4), shows (4), policy (4), checking (4), frequently (4), each (4), select (4), allow (4), different (4), section (4), then (4), account (4), europe (4), west3 (4), platform (4), help (4), format (4), generate (4), replace (4), https (4), method (4), copy (4), viewing (4), disable (4), services (4), apis (4), development (4), authenticate (4), external (4), provider (4), running (4), plan (4), tools (4), distributed (4), ubuntu (4), bandwidth (4), tcp (4), pmu (4), ssd (4), share (4), upgrade (4), live (4), autoscaling (4), cross (4), requests (4), calendar (4), single (4), active (4), clusters (4), containers (4), container (4), database (4), postgresql (4), extensions (4), work (4), suspend (4), resize (4), graceful (4), locations (4), plans (4), replication (4), bound (4), terms (3), need (3), last (3), apache (3), steps (3), second (3), gce_instance (3), cloudaudit (3), resourcename (3), determining (3), was (3), whether (3), succeeded (3), what (3), caused (3), most (3), menu (3), row (3), opens (3), graph (3), represents (3), specified (3), more_vert (3), newly (3), done (3), distinguish (3), health_state (3), xyzq (3), counter (3), actions (3), tracks (3), only (3), such (3), severity (3), often (3), 2019 (3), 19t15 (3), networks (3), fields (3), have (3), configured (3), general (3), curl (3), authorization (3), bearer (3), orderby (3), desc (3), pagesize (3), resourcenames (3), alt (3), export (3), costs (3), documentation (3), api (3), credentials (3), setting (3), guides (3), infrastructure (3), observability (3), analytics (3), automatic (3), troubleshooting (3), encryption (3), pro (3), serial (3), configurations (3), patterns (3), higher (3), discounts (3), cuds (3), manual (3), scalable (3), resilient (3), autoscale (3), balancer (3), prevent (3), ibm (3), spectrum (3), perform (3), deploying (3), during (3), prepare (3), deployment (3), rhel (3), protect (3), certificates (3), properties (3), increase (3), schedule (3), lifecycle (3), design (3), size (3), non (3), pool (3), move (3), workstations (3), series (3), tpus (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), site (2), youtube (2), center (2), started (2), system (2), status (2), products (2), updated (2), 2026 (2), utc (2), licensed (2), feedback (2), shortly (2), reveals (2), true (2), initialization (2), follow (2), appropriate (2), observe (2), some (2), others (2), adding (2), 2fsystem_event (2), methodname (2), recreateinstance (2), filtering (2), changed (2), aggregate (2), identify (2), problematic (2), particular (2), over (2), debugging (2), scenarios (2), cases (2), 6498902454451155884 (2), info (2), instancewithid (2), 123456 (2), ipaddress (2), net (2), networkwithid (2), healthcheck (2), previousdetailedhealthstate (2), notificationtime (2), characters (2), utf (2), boolean (2), has (2), possible (2), numeric (2), address (2), within (2), contain (2), debug (2), instance_group_manager_events (2), auth (2), print (2), exporting (2), writes (2), whenever (2), these (2), enabled (2), provides (2), free (2), per (2), one (2), idp (2), must (2), federated (2), sdk (2), languages (2), frameworks (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), quota (2), commitment (2), consumption (2), standard (2), full (2), registration (2), sles (2), port (2), collecting (2), nodes (2), report (2), arm (2), core (2), rdp (2), app (2), latency (2), analyze (2), visible (2), cores (2), automatically (2), committed (2), generation (2), underutilized (2), insights (2), utilization (2), globally (2), web (2), iis (2), shared (2), reserve (2), autoscaler (2), autoscalers (2), activity (2), kubernetes (2), place (2), directory (2), redis (2), cloning (2), writer (2), always (2), alwayson (2), file (2), volumes (2), synchronization (2), switch (2), byol (2), payg (2), byos (2), families (2), guide (2), securing (2), simulate (2), topology (2), together (2), repairs (2), failures (2), template (2), suspended (2), stopped (2), target (2), distribution (2), physical (2), cancel (2), once (2), interfaces (2), ipv6 (2), static (2), decrease (2), basic (2), consistent (2), scoped (2), appliances (2), asynchronous (2), throughput (2), encrypt (2), names (2), mount (2), memory (2), extreme (2), balanced (2), organization (2), user (2), through (2), advanced (2), rdma (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), accelerator (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, action, join, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, getting, github, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, java, registered, trademark, oracle, affiliates, developers, creative, commons, attribution, repeat, few, better, approximate, parameter, needed, completion, 2factivity, measure, becoming, timestamps, both, calculate, easier, finished, signal, received, interval, long, take, fully, might, slower, than, recommends, margin, observed, specifying, successful, indicate, recreation, triggered, again, corresponding, show, attempts, reason, message, given, ones, similarly, grouping, identifying, also, disruptive, warning, timeout, fine, tune, assess, experienced, instance_group_manager_id, 3138236342290985981, instance_id, instance_location, 127z, instancegroupmanagerevent, 456, healthchecks, 444z, receivetimestamp, 296439184z, encoding, enforced, not, replaced, question, marks, typically, appear, they, omitted, false, occurred, current, previous, probed, description, contains, shown, written, useful, depending, archive, analysis, stream, function, destinations, bigquery, pub, sub, exports, trigger, display, narrow, search, alternatively, gce, parameters, provided, remain, avoid, allotment, month, priced, volume, summary, haven, already, verifies, selecting, provide, installed, previously, sure, latest, version, components, note, init, installation, initialize, don, tab, before, begin, goes, well, overall, document, describes, save, categorize, preferences, stay, organized, collections, home, concurrent, renewal, nvme, resizing, common, pay, output, diagnostic, sudoers, screenshots, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, kernel, panic, fstab, unresponsive, suspension, reboots, shutdowns, connectivity, tips, nics, dpdk, improve, resiliency, communication, reduce, compact, idpf, interface, irdma, driver, nic, customize, threads, sustained, merge, split, extend, renew, without, purchase, cost, savings, next, dynamic, overcommit, cpus, floating, reliable, udp, backends, routing, scaling, consuming, consume, combine, cud, sharing, decisions, signals, serving, predictions, organize, replica, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, spark, forwarding, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, built, integrations, validation, were, deployed, transition, test, hammerdb, bucket, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, architectures, client, private, mailjet, mailgun, sendgrid, sending, blue, green, deployments, lamp, joomla, asp, interactive, mongodb, flask, terraform, servers, mtls, random, generator, virtio, rng, accurate, protocol, ntp, append, els, restrictions, packages, deprecate, versions, family, trusted, red, hat, knowledgebase, functionality, risks, vpc, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, process, faulty, unmanaged, affect, preserved, turn, off, alternate, fails, repairing, maintain, upgrades, override, selectively, applying, accelerate, outage, rebalance, reenable, proactive, redistribution, shape, distribute, define, accidental, deletion, spread, edit, rename, reset, resume, restart, referrers, source, uuid, recover, corrupted, duplicate, clones, alerts, backups, vss, regionally, protection, considerations, synchronous, consistency, failback, replicate, provisioned, iops, limits, evaluate, settings, kms, customer, supplied, symbolic, links, practice, device, ram, attach, additional, exapools, verify, ptr, record, failure, rates, tags, restrict, automate, password, require, powershell, sac, securely, apps, root, vpn, bastion, iap, connection, browser, connections, iso, imported, prerequisites, importing, bring, own, path, detach, reattach, constraint, accounting, provision, examples, slurm, reserved, team, slice, slices, adds, deterministic, base, requirements, ready, aci, preempted, historical, alternative, similar, ops, subnet, public, gpudirect, ultra, specify, minimum, hostname, quickstarts, iam, roles, permissions, office, licensing, premium, strategy, gemini, bare, metal, accelerators, platforms, scores, purpose, discover, skip, main,

Text of the page (random words):
d to view and read the log entries to view the health state change logs of a managed instance use the following command gcloud logging read resource type gce_instance_group_manager and logname projects project_id logs compute googleapis com 2finstance_group_manager_events and jsonpayload instancehealthstatechange and labels compute googleapis com instance_name instance_name limit 10 replace the following project_id your project id instance_name the managed instance for which you want to view the health state change logs rest to view the health state change logs of a managed instance make a post request to the entries list method curl h content type application json h authorization bearer oauth2_token x post d filter resource type gce_instance_group_manager and logname projects project_id logs compute googleapis com 2finstance_group_manager_events and jsonpayload instancehealthstatechange and labels compute googleapis com instance_name instance_name orderby timestamp desc pagesize 10 resourcenames projects project_id https logging googleapis com v2 entries list alt json replace the following oauth2_token your application s access token for local testing you can use the gcloud auth print access token command to generate a token project_id your project id instance_name the managed instance for which you want to view the health state change logs format of log entries instance health state change log entries contain information useful for monitoring and debugging the state of your managed instances the logs are written to platform logs with the log name instance_group_manager_events the platform logs help you to debug and troubleshoot issues logname projects project_id logs compute googleapis com 2finstance_group_manager_events health state change log entries contain the following types of information general information shown in most logs such as severity project id mig name and id project number timestamp and so on fields specific to the instance s health state within each health state change log entry the jsonpayload instancehealthstatechange field contains the following information field description instance url for the instance based on string project id and instance name instancewithid url for the instance based on its numeric project id and instance id ipaddress ip address of the instance as probed by the health check network url of the network resource for this instance based on string project id and network name networkwithid url of the network resource for this instance based on its numeric project id and network id healthcheck url for the health check that s configured for the managed instance group previousdetailedhealthstate previous health state of the instance for the list of possible states see health states detailedhealthstate current health state of the instance for the list of possible states see health states notificationtime timestamp of when the health state change occurred log fields of type boolean typically only appear if they have a value of true if a boolean field has a value of false that field is omitted from the log utf 8 encoding is enforced for log fields characters that are not utf 8 characters are replaced with question marks log entry example the following example shows a vm instance s health state change from healthy to unhealthy logname projects my project logs compute googleapis com 2finstance_group_manager_events resource type gce_instance_group_manager labels instance_group_manager_id 3138236342290985981 instance_group_manager_name my mig project_id my project location europe west3 labels compute googleapis com instance_id 6498902454451155884 compute googleapis com instance_location europe west3 a compute googleapis com instance_name my mig a timestamp 2019 11 19t15 47 57 127z severity info jsonpayload type type googleapis com compute instancegroupmanagerevent instancehealthstatechange instance projects my project zones europe west3 a instances my mig a instancewithid projects 123456 zones europe west3 a instances 6498902454451155884 ipaddress 10 0 0 4 network projects my project global networks net 1 networkwithid projects 123456 global networks 456 healthcheck projects my project global healthchecks my mig health check previousdetailedhealthstate healthy detailedhealthstate unhealthy notificationtime 2019 11 19t15 47 56 444z receivetimestamp 2019 11 19t15 47 57 296439184z use cases you can use the health state change logs in the following monitoring or debugging scenarios find out how often a particular vm instance changed health states over time assess how often a mig experienced health state changes of its instances identify problematic vm instances that frequently go unhealthy find out what caused an autohealing attempt find out whether an autohealing attempt succeeded for a specific vm instance fine tune health check configuration for an application by determining an appropriate initial delay for autohealing monitoring health state changes of a vm you can monitor how often a vm instance s health state changes by creating a metric that tracks the health state changes of that particular vm to create the metric and monitor the changes do the following go to the logs explorer in the google cloud console go to logs explorer enter the following query in the query builder using your project id and instance name resource type gce_instance_group_manager and logname projects project_id logs compute googleapis com 2finstance_group_manager_events and jsonpayload instancehealthstatechange and labels compute googleapis com instance_name instance_name in the query results section click actions and then click create metric on the create logs metric page do the following set the metric type as counter enter a log metric name for example health mig xyzq the build filter section displays the log query from the logs explorer you can also configure the metric s filter to account for only disruptive states such as unhealthy and timeout by adding severity warning to the filter under labels click add label enter a label name for example health_state set the label type as string set the field name to jsonpayload instancehealthstatechange detailedhealthstate this will allow you to distinguish between different health state changes click done to add the label click create metric go to the logs based metrics page and find the newly created metric click the menu more_vert in the metric s row and select view in metrics explorer the metrics explorer opens and displays the graph that represents the health state changes of the vm instance which you specified in the query monitoring health state changes of all vms in a mig you can monitor the health state changes of all managed instances by creating a metric that tracks the health state changes of the managed instances to create the metric and monitor the changes do the following go to the logs explorer in the google cloud console go to logs explorer enter the following query in the query builder using your project id and managed instance group s name resource type gce_instance_group_manager and logname projects project_id logs compute googleapis com 2finstance_group_manager_events and jsonpayload instancehealthstatechange and resource labels instance_group_manager_name mig_name in the query results section click actions and then click create metric on the create logs metric page do the following set the metric type as counter enter a log metric name for example health mig xyzq under labels click add label enter a label name for example health_state set the label type as string set the field name to jsonpayload instancehealthstatechange detailedhealthstate this will allow you to distinguish between different health state changes click done to add the label click create metric go to the logs based metrics page and find the newly created metric click the menu more_vert in the metric s row and select view in metrics explorer the metrics explorer opens and displays the graph that represents the health state changes of all the vm instances in the managed instance group which you specified in the query identifying vms that frequently go unhealthy you can identify problematic vms that frequently go unhealthy by creating a metric that tracks the health state changes of all vm instances in your mig and grouping the metric by instances to create the metric and group by instances do the following go to the logs explorer in the google cloud console go to logs explorer enter the following query in the query builder using your project id and managed instance group s name resource type gce_instance_group_manager and logname projects project_id logs compute googleapis com 2finstance_group_manager_events and jsonpayload instancehealthstatechange and resource labels instance_group_manager_name mig_name in the query results section click actions and then click create metric on the create logs metric page do the following set the metric type as counter enter a log metric name for example health mig xyzq under labels click add label enter a label name for example health_state set the label type as string set the field name to jsonpayload instancehealthstatechange detailedhealthstate this will allow you to distinguish between different health state changes click done to add the label similarly add a second label for example instance with the field name set to jsonpayload instancehealthstatechange instance click create metric go to the logs based metrics page and find the newly created metric click the menu more_vert in the metric s row and select view in metrics explorer the metrics explorer opens and displays the graph that represents the health state changes of all the vm instances in the managed instance group which you specified in the query set the group by to instance to see the aggregate number of health state changes for each instance the instances with the most health state changes in aggregate are the ones that most frequently go unhealthy checking what caused an autohealing attempt you can find out what caused an autohealing attempt by filtering logs for repair operations for given vm instance to filter the repair operations do the following go to the logs explorer in the google cloud console go to logs explorer enter the following query in the query builder using your project id and the instance s name resource type gce_instance and logname projects project_id logs cloudaudit googleapis com 2fsystem_event and protopayload methodname compute instances repair recreateinstance and protopayload resourcename instance_name click run query the query results will show all autohealing attempts on the vm with the reason of autohealing in protopayload status message checking if autohealing succeeded for a vm you can find out whether an autohealing attempt succeeded for a vm instance by filtering logs for repair operations and health changes by vm instance name if the instance s health state changed to healthy after a repair operation you will see a corresponding health state change log follow the steps go to the logs explorer in the google cloud console go to logs explorer enter the following query in the query builder using your project id and the instance s name resource type gce_instance and logname projects project_id logs cloudaudit googleapis com 2fsystem_event and protopayload methodname compute instances repair recreateinstance and protopayload resourcename instance_name or resource type gce_instance_group_manager and logname projects project_id logs compute googleapis com 2finstance_group_manager_events and jsonpayload instancehealthstatechange and labels compute googleapis com instance_name instance_name the first part of the query displays the instance repair operations which indicate that recreation was triggered by mig autohealing to make the instance healthy again the second part of the query displays all health state changes of the vm instance in the query results the health state change event with detailedhealthstate set to healthy shortly after a repair operation shows that the autohealing attempt was successful determining initial delay value of a mig determining an appropriate initial delay value for mig autohealing is easier with vm instance health state logging you can use logs to observe the time between when the instances insert operation finished and when the first healthy signal was received for a set of instances in a group this time interval reveals how long instances take to fully boot up as some vms might boot up slower than others google recommends adding some margin to the observed initialization time from insert operation to healthy state when specifying the initial delay in the autohealing policy to measure the time between the instance insert operation and the instance becoming healthy run a query for insert operations and health change logs by vm instance name use timestamps from both operations to calculate the instance s initialization time follow the steps go to the logs explorer in the google cloud console go to logs explorer enter the following query in the query builder using your project id and the instance s name resource type gce_instance and logname projects project_id logs cloudaudit googleapis com 2factivity and protopayload request type type googleapis com compute instances insert and operation last true and protopayload resourcename instance_name or resource type gce_instance_group_manager and logname projects project_id logs compute googleapis com 2finstance_group_manager_events and jsonpayload instancehealthstatechange and labels compute googleapis com instance_name instance_name the first part of the query shows the completion of the vm insert operation the second part shows all health state changes for the vm in the query results the timestamp of the health state change event with detailedhealthstate set to healthy shortly after the insert operation reveals the time needed for this vm to boot up repeat the steps for a few more vms to get a better approximate value of the initial delay parameter send feedback except as otherwise noted the content of this page is licensed under the creative commons attribution 4 0 license and code samples are licensed under the apache 2 0 license for details see the google developers site policies java is a registered trademark of oracle and or its affiliates last updated 2026 07 17 utc need to tell us more easy to understand easytounderstand thumb up solved my problem solvedmyproblem thumb up other otherup thumb up hard to understand hardtounderstand thumb down incorrect information or sample code incorrectinformationorsamplecode thumb down missing the information samples i need missingtheinformationsamplesineed thumb down other otherdown thumb down last updated 2026 07 17 utc products and pricing see all products google cloud pricing google cloud marketplace contact sales support community forums support release notes system status resources github getting started with google cloud code sa...