Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-1957

Disallow conntrack without Loki

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • NetObserv - Sprint 265
    • None
    • None
    • Hide
      Previously, it was possible to configure a FlowCollector with "processor.logTypes" Conversations, EndedConversations or All with "loki.enable" being false, despite the conversation logs being only useful when Loki is enabled, resulting in resource usage waste. Now, this configuration is invalid and is rejected by the validation webhook.
      Show
      Previously, it was possible to configure a FlowCollector with "processor.logTypes" Conversations, EndedConversations or All with "loki.enable" being false, despite the conversation logs being only useful when Loki is enabled, resulting in resource usage waste. Now, this configuration is invalid and is rejected by the validation webhook.

      Connection tracking produces new kind of log events for Loki, but this is only for Loki: prometheus metrics, and exporters, only use the regular flows.

      So we should not allow users to configure conn-tracking when they disabled Loki: this would generate a CPU+memory cost for no benefit.

              jtakvori Joel Takvorian
              jtakvori Joel Takvorian
              None
              None
              None
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: