- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
The value of the log_statement
flag determines the SQL statements that are logged. Valid
values are:
none
ddl
mod
all
The value ddl
logs all data definition statements. The value mod
logs all ddl
statements, plus
data-modifying statements.
The statements are logged after a basic parsing is done and the statement type is determined,
thus log statements with errors are not logged. When using an extended query protocol,
logging occurs after an Execute
message is received and values of the bind parameters are
included.
A value of ddl
is recommended unless otherwise directed by your organization’s logging
policy.
Auditing helps with forensic analysis. If the log_statement
is not set to the correct value, too
many statements may be logged and lead to issues with finding relevant information from
the logs, or too few statements may be logged with relevant information missing from the
logs. Setting the log_statement
to align with your organization’s security and logging policies
facilitates auditing and review of database activities later on. This recommendation is
applicable to PostgreSQL database instances.
Turning on logging will increase the required storage over time. Mismanaged logs may cause your storage costs to increase. Setting custom flags using the command line on certain instances will cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended that you apply these flag changes during a period of low usage.
log_statement
from the drop-down menu and set the appropriate value.Configure the log_statement database
flag for every Cloud SQL PosgreSQL database
instance using the below command.
gcloud sql instances patch <INSTANCE_NAME> --database-flags log_statement=<ddl|mod|all|none>
Note This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all the flags that you want to set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign ("=").