- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
The log_min_error_statement
flag defines the minimum message severity level that is
considered an error statement. Messages for error statements are logged with the SQL
statement. Valid values include DEBUG5
, DEBUG4
, DEBUG3
, DEBUG2
, DEBUG1
, INFO
, NOTICE
,
WARNING
, ERROR
, LOG
, FATAL
, and PANIC
. Each severity level includes the subsequent levels
mentioned above. Ensure a value of ERROR
or stricter is set.
Auditing helps with troubleshooting operational problems and also permits forensic analysis.
If log_min_error_statement
is not set to the correct value, messages may not be classified
as error messages appropriately. If general log messages are considered as error messages,
it would be difficult to determine the actual errors. If only stricter severity levels are considered as
error messages, true errors might not be logged with their SQL statements. The
log_min_error_statement
flag should be set to ERROR
or stricter. 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.
Flags
section.log_min_error_statement
from the drop-down menu and set the appropriate
value.Save
to save your changes.Flags
section on the Overview page.Configure the log_min_error_statement
database flag for every Cloud SQL
PosgreSQL database instance using the below command.
gcloud sql instances patch <INSTANCE_NAME> --database-flags log_min_error_statement=<DEBUG5|DEBUG4|DEBUG3|DEBUG2|DEBUG1|INFO|NOTICE|WARNING|ERROR>
Note: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want 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 (=).
By default log_min_error_statement
is ERROR
.
WARNING: This patch modifies database flag values, which may require your instance to be restarted. Check the list of supported flags - https://cloud.google.com/sql/docs/postgres/flags - to see if your instance will be restarted when this patch is submitted.
Note: Some database flag settings can affect instance availability or stability and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines.
Note: Configuring the above flag does not require restarting the Cloud SQL instance.
Version 8, 8.5: Collect Detailed Audit Logs
Version 7, 6.3: Enable Detailed Logging