Deployment process and instructions reference: pixie install
Pixie Platform Main Components Pixie Edge Module (PEM): Pixie’s agent, installed per node. PEMs use eBPF to collect data, which is stored locally on the node.
Vizier: Pixie’s collector, installed per cluster. Responsible for query execution and managing PEMs.
Pixie Cloud: Used for user management, authentication, and data proxying. Can be hosted or self-hosted.
Pixie CLI: Used to deploy Pixie. Can also be used to run queries and manage resources like API keys.
Time-Sharing Systems and Linux First, let’s review time-sharing systems. The time-sharing system is a very important operating system concept that maximizes computer utilization and is a crucial means of implementing multi-program concurrency.
The Linux kernel we use daily also adopts the time-sharing system philosophy, mainly reflected in the following aspects:
Time Slice: Linux uses a time slice mechanism to divide CPU time. Each process can only execute for one time slice before yielding the CPU to other processes. This achieves CPU time sharing and fair allocation.
This article reviews the 2022 productization evolution of a large-scale internet monitoring platform, covering the planning and implementation approach to move from large-scale coverage to productization, usability, and intelligence. The platform spans multi-cloud, multi-region, massive-metric collection and alerting; this is a record of its real evolution.
Platform Status: Large-Scale Challenges of Multi-Cloud Heterogeneity As business expands globally, the monitoring platform has entered a phase of ultra-large scale, highly distributed, and heterogeneous operation. The current status is as follows:
SRE (Site Reliability Engineering) is a core role in ensuring the availability of distributed services, and the monitoring system is the foundation of SRE work. This article focuses on SRE core principles, walking through the pain points of modern monitoring systems, technology stack selection, Prometheus core principles, and alerting best practices, offering a practical enterprise-grade monitoring construction methodology.
SRE Core Principles: Stability is the #1 Metric SRE’s core is ensuring continuous service stability through engineering practices, focusing on capacity planning, cluster maintenance, fault tolerance, load balancing, and monitoring system construction. There are only 3 core measurement metrics:
MySQL Monitoring MySQL Privilege Best Practices Privilege control is primarily for security reasons, so follow these best practices:
Grant only the minimum privileges needed to prevent users from doing harm. For example, if a user only needs to query, just grant SELECT privileges, not UPDATE, INSERT, or DELETE. Restrict the login host when creating users, typically to a specific IP or internal network IP range. Delete users without passwords after initializing the database. The installation automatically creates some users with no passwords by default. Set passwords that meet complexity requirements for each user. Periodically clean up unnecessary users. Revoke privileges or delete users. Example: