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

NoData using Teams as receiver with "using pod_node_graph_enricher" line #1527

Open
antikilahdjs opened this issue Aug 12, 2024 · 0 comments

Comments

@antikilahdjs
Copy link

Describe the bug
Hello, the pod_node_graph_enricher send noData to my Teams as well. The memory for Container and Pods works perfectly.

To Reproduce
Steps to reproduce the behavior:

  1. Install the Robusta using the normal way (Helm Charts)
  2. Add the custom values like
# Critical Events (Custom)
- triggers:
  - on_pod_oom_killed:
      rate_limit: 3600
  actions:
  - pod_oom_killer_enricher: {}
  - logs_enricher: {}
  - pod_node_graph_enricher:
      resource_type: Memory
      display_limits: false
  - oomkilled_container_graph_enricher:
      resource_type: Memory
      display_limits: true
  - pod_graph_enricher:
      resource_type: Memory
      display_limits: true
  sinks:
    - "main_ms_teams_sink_critical"
  stop: true
  1. Change memory_limits to false as above

Expected behavior
Do not display the Node Memory Limits or show the Memory correctly because for now always it is sent with "No Data"

Screenshots
image

Additional context
If the value is true or false the alerts sent to the Teams with No Data, does matter what you configure

@antikilahdjs antikilahdjs changed the title NoData using Teams using pod_node_graph_enricher NoData using Teams as receiver with "using pod_node_graph_enricher" line Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant