Rules tagged with: Observability
Logging, tracing, debugging and monitoring.
All 5 check SQL or PL/SQL code (G- codes). Browse the rules below for explanations, examples and recommended fixes.
All 5 Observability rules
-
G-3220 Always process saved exceptions from a FORALL statement.Critical Reliability
-
G-5010 Try to use a error/logging framework for your application.Critical Reliability
-
G-5080 Always use FORMAT_ERROR_BACKTRACE when using FORMAT_ERROR_STACK or SQLERRM.Critical Maintainability
-
G-6010 Always use a character variable to execute dynamic SQL.Major Maintainability
-
G-8510 Always use dbms_application_info to track program process transiently.Critical Reliability
5 total
Related tags
Tags that appear on the same rules as Observability:
- Exception (2 shared)
- Dynamic SQL (1 shared)
- Pattern (1 shared)
- Performance (1 shared)
- SQL (1 shared)
More ways to browse rules
- Trivadis PL/SQL & SQL guideline rules - Rules that implement the Trivadis coding guidelines.
- OWASP-related security rules - Rules that name an OWASP Top 10 risk category.
- Oracle APEX rules - Checks for APEX applications, pages, items and regions.
- PostgreSQL rules - Rules that also apply to PostgreSQL and PL/pgSQL.
- Security rules - All rules in the Security quality area.
- Reliability rules - Rules that prevent bugs and failures at run time.
- Maintainability rules - Rules for code that is easy to read and change.
- Rules by quality area - Security, reliability and maintainability.
- Rules by severity - From Blocker to Info.
- Rule profiles - Essential to Extreme: which rules are checked.
- All rules - Search and filter the complete rule set.