Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export the evaluated decision result to ES #8116

Closed
Tracked by #8083
saig0 opened this issue Nov 1, 2021 · 0 comments · Fixed by #8813
Closed
Tracked by #8083

Export the evaluated decision result to ES #8116

saig0 opened this issue Nov 1, 2021 · 0 comments · Fixed by #8813
Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog

Comments

@saig0
Copy link
Member

saig0 commented Nov 1, 2021

Description

We should export the result of a decision evaluation to Elasticsearch. The records will be consumed by Operate and Optimize.

  • create a new ES template for the evaluated decision result
  • extend the ES exporter configuration to export these records by default

blocked by #8115

@saig0 saig0 added kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog labels Nov 1, 2021
@saig0 saig0 added this to the Evaluate DMN decisions milestone Nov 1, 2021
@saig0 saig0 added this to Planned in Zeebe Nov 1, 2021
@saig0 saig0 mentioned this issue Nov 1, 2021
43 tasks
@ghost ghost closed this as completed in b7e0d45 Feb 18, 2022
Zeebe automation moved this from Planned to Done Feb 18, 2022
@KerstinHebel KerstinHebel removed this from Done in Zeebe Mar 23, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes an issue or PR as a feature, i.e. new behavior scope/broker Marks an issue or PR to appear in the broker section of the changelog
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants