guillotina-audit 2.0.5

elasticsearch audit support for guillotina

Contents

• Guillotina_audit: ElasticSearch Logging for Audit Trail in Guillotina Framework

  • Aim of the package?

  • Installation

  • Configuration

  • Installation on a site

  • Uninstall on a site

  • 2.0.5 (2024-10-22)

  • 2.0.4 (2024-08-02)

  • 2.0.3 (2024-03-06)

  • 2.0.2 (2024-03-06)

  • 2.0.1 (2024-03-05)

  • 2.0.0 (2024-01-23)

  • 1.0.6 (2023-12-19)

  • 1.0.5 (2023-12-12)

  • 1.0.4 (2023-11-16)

  • 1.0.3 (2023-11-16)

  • 1.0.2 (2023-11-15)

  • 1.0.1 (2023-11-15)

  • 1.0.0 (2023-11-15)

Guillotina_audit: ElasticSearch Logging for Audit Trail in Guillotina Framework

Aim of the package?

The main purpose of this package is to enable auditing and monitoring of changes made to Guillotina objects. By integrating Elasticsearch as the logging backend, it allows for efficient indexing and searching of the audit logs.

When an object is created, modified, or deleted within the Guillotina system, the guillotina_audit package captures relevant information about the event, such as the object ID, the timestamp of the action, the type of action (create, update, delete), and any additional relevant data.

This information is then sent to Elasticsearch, which stores it in a structured format. Elasticsearch provides powerful search capabilities, allowing you to query and analyze the audit logs based on various criteria, such as object ID, timestamps, action types, and more.

By logging changes and events in Elasticsearch, guillotina_audit facilitates monitoring and tracking of object activities in the Guillotina system. It helps in ensuring data integrity, tracking user actions, investigating issues, and maintaining a historical record of object modifications.

The package provides an essential auditing layer for transparency and accountability, helping users gain insights into the changes happening within the Guillotina system and enabling effective monitoring and analysis of object-level activities.

Installation

pip install guillotina-audit

Configuration

config.yaml can include elasticsearch section. Add this to your guillotina config file

audit:
  index_name: "audit"
  connection_settings:
    hosts:
      - "http://127.0.0.1:9200"
    sniffer_timeout: 0.5
    sniff_on_start: true

Installation on a site

Guillotina_audit comes as an addon for guillotina. To install it in your site:

“POST”, “/db/guillotina/@addons”, data=json.dumps({“id”: “audit”})

Uninstall on a site

“DELETE”, “/db/guillotina/@addons”, data=json.dumps({“id”: “audit”})

Uninstalling will not delete the log entries created in ES.

2.0.5 (2024-10-22)

• Adding metadata field as an object

• Adding command audit-update-mappings to update mappings

• Adding command audit-update-settings to update settings [nilbacardit26]

2.0.4 (2024-08-02)

• Removing zope.interface dependency in setup.py

• Removing docker dependency

2.0.3 (2024-03-06)

• Adding permissions_changed action when permissions are changed

2.0.2 (2024-03-06)

• Being able to setting up index_permission_changes in settings. If defined as True, it will index all changes in permissions.

2.0.1 (2024-03-05)

• Being able to decode dates and datetimes when indexing custom payloads from events.

2.0.0 (2024-01-23)

• Supporting ES version 7 and 8

• By default the async elasticsearch version is 8.12

1.0.6 (2023-12-19)

• Changing date by datetime in models.

• Fixing creation_date was not indexed when login wildcards

1.0.5 (2023-12-12)

• Adding log_entry method to the utility. Now customized documents can be indexed

1.0.4 (2023-11-16)

• Changing requirement of guillotina

1.0.3 (2023-11-16)

• Adding try except clause in subscribers

1.0.2 (2023-11-15)

• Adding save_payload parameter in the settings of the utility

1.0.1 (2023-11-15)

• Solving bugs

1.0.0 (2023-11-15)

• Initial release [nilbacardit26]