Better handling for decision logs with vector

Open
#733 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kubernetes, rust
Domain
authorization, observability

Research direction

Start by locating the OPA decision-log handling and tracing where returned decision-log values are added to the message field. Determine how to expose the logs as structured JSON while preserving their contents, then verify that the resulting records can be indexed and used for authorization-event dashboards in OpenSearch.

Written by the indexing model from the issue text.

Description

Currently OPA decision logs are treated in the same way as all other logs, by taking the values returned by OPA and adding it to the message field. The decision log is already a JSON document and flattening it into a string makes it harder to use. We should provide a way to log the decision logs as JSON so that it can be indexed better by OpenSearch. This would make building dashboards based of the authorisation events easier to build and more performant.

Dominant language
Rust
Stars
21
Forks
5
Avg merge
12h 44m
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/opa-operator

All issues in stackabletech/opa-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.