Ongoing Maintenance, Monitoring, and Logging
    • 14 Apr 2025
    • 1 Minute to read
    • Dark
      Light
    • PDF

    Ongoing Maintenance, Monitoring, and Logging

    • Dark
      Light
    • PDF

    Article summary

    Regular maintenance and proactive monitoring are essential to ensure optimal performance, accurate access evaluations, and system reliability. The following sections provide guidance on database upkeep, responding to changes in Policies or data sources, monitoring execution jobs and PDP interactions, and analyzing log data for effective troubleshooting.

    Maintenance

    • Operational Database - The predefined Operational Postgres DB requires ongoing customer maintenance, including backups, cleanups, reindexing etc. Consult with PlainID Professional Services team for guidelines and assistance.
    • Policy Changes – Customers should be aware of any Policy changes that require access recalculation. Necessary changes should be made, and a full recalculation and generation of access files triggered as needed, at their discretion.
    • Data Source Changes – Customers should be aware of any system or data source changes/updates that may require adjustments to configuration or policies, as well as a full recalculation of access files.

    Monitoring

    • Job Monitoring – Customers should monitor job execution status using the Job Execution History API, the operational DB status table, and access decision errors to track major events and errors during execution.
    • PDP Audits and Logs – Since the PDP interacts extensively with this Authorizer, monitoring PDP audits and logs can help identify unusual system behaviors that may require administrative attention.

    Logging

    Customers should collect and monitor Authorizer logs to observe for major events as well as for troubleshooting.

    • Important log entries:
    Log Entry ExampleDescription
    received job: {"id":"jb1","trigger":"cron","mode":""}Scheduled job received
    Start Request: PUT /1.0/jobs/jb1Job started
    finished to process job: jb1Job completed
    starting to populate subjects from flows for job: jb1Fetching data from the data source
    starting to calculate access for job: jb1PDP processing access
    finished converting flow: jobID: jb1, flowID: flow1Flow conversion completed

    Was this article helpful?