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

threshold alert and index connector problem #180993

Closed
benibomba opened this issue Apr 17, 2024 · 1 comment
Closed

threshold alert and index connector problem #180993

benibomba opened this issue Apr 17, 2024 · 1 comment
Labels
bug Fixes for quality problems that affect the customer experience needs-team Issues missing a team label

Comments

@benibomba
Copy link

benibomba commented Apr 17, 2024

Kibana version: 7.17.18

Elasticsearch version: 7.17.18

Server OS version: Red Hat 8

Browser version: Latest Google Chrome x64

Original install method (e.g. download page, yum, from source, etc.): download page

Describe the bug: Problem with threshold alert and index connector

Good afternoon, I am facing a problem with kibana alerts. I am using threshold alert with index connector. I'm trying to write a json like this

{
  "message": """{{{#context.alerts}}}
host.name: {{{host.name}}}
{{/context.alerts}}"""
}

But it ends up writing this host.name: to the index.
As I understand it, this is because in the original json host.name is not written as an object. How to make it write as event.k Has anyone encountered this? Is there a solution for this?

Steps to reproduce:

  1. Create index connector
  2. Create threshold alert group by host.name and action index connector with json
{
  "message": {{.}}
}
  1. In index you will see field message with json, in this you will see contex -> alerts -> host.name

Expected behavior:

contex -> alerts -> host -> name

Screenshots (if relevant):

image

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

@benibomba benibomba added the bug Fixes for quality problems that affect the customer experience label Apr 17, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 17, 2024
@jsanz
Copy link
Member

jsanz commented Apr 29, 2024

Hi, thanks for creating an issue, but this does not look like a software bug and would be better addressed in our Kibana discussion forum at:

https://discuss.elastic.co/c/elastic-stack/kibana/7

Please add the appropriate tag (dashboard, vega, map, etc) to speed up the triage.

Closing.

@jsanz jsanz closed this as not planned Won't fix, can't repro, duplicate, stale Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience needs-team Issues missing a team label
Projects
None yet
Development

No branches or pull requests

2 participants