[cilium] Cilium Operator metrics are not collected by default

And configuring the integration throws errors
Output of the info page
root@datadog-c7rmp:/# agent status
Getting the status from the agent.

2021-09-16 14:33:33 UTC | CORE | WARN | (pkg/util/log/log.go:611 in func1) | Deactivating Autoconfig will disable most components. It's recommended to use autoconfig_exclude_features and autoconfig_include_features to activate/deactivate features selectively
===============
Agent (v7.31.0)
===============

  Status date: 2021-09-16 14:33:33.296 UTC<PHONE_NUMBER>296)
  Agent start: 2021-09-16 14:32:48.846 UTC<PHONE_NUMBER>846)
  Pid: 1
  Go Version: go1.15.13
  Python Version: 3.8.11
  Build arch: amd64
  Agent flavor: agent
  Check Runners: 4
  Log Level: INFO

  Paths
  =====
    Config File: /etc/datadog-agent/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

  Clocks
  ======
    NTP offset: 26µs
    System time: 2021-09-16 14:33:33.296 UTC<PHONE_NUMBER>296)

  Host Info
  =========
    bootTime: 2021-09-16 11:03:22 UTC<PHONE_NUMBER>000)
    kernelArch: x86_64
    kernelVersion: 5.4.117-58.216.amzn2.x86_64
    os: linux
    platform: ubuntu
    platformFamily: debian
    platformVersion: 21.04
    procs: 146
    uptime: 3h29m37s

  Hostnames
  =========
    ec2-hostname: ip-10-0-67-197.eu-west-2.compute.internal
    host_aliases: [ip-10-0-67-197.eu-west-2.compute.internal-sandbox-infra-2036]
    hostname: i-07f24cfb6cb2e6b70
    instance-id: i-07f24cfb6cb2e6b70
    socket-fqdn: datadog-c7rmp
    socket-hostname: datadog-c7rmp
    host tags:
      cluster_name:sandbox-infra-2036
      env:sandbox-infra-2036
      kube_cluster_name:sandbox-infra-2036
      project:sandbox-infra-2036
      sla_agreement:false
      stack_name:sandbox-infra-2036
      stack_type:sandbox
    hostname provider: aws
    unused hostname providers:
      azure: azure_hostname_style is set to 'os'
      configuration/environment: hostname is empty
      gce: unable to retrieve hostname from GCE: status code 404 trying to GET http://<IP_ADDRESS>/computeMetadata/v1/instance/hostname

  Metadata
  ========
    cloud_provider: AWS
    hostname_source: aws

=========
Collector
=========

  Running Checks
  ==============

    cilium (1.7.2)
    --------------
      Instance ID: cilium:8f735fdfa8bcd6cb [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/cilium.d/auto_conf.yaml
      Total Runs: 3
      Metric Samples: Last Run: 969, Total: 2,907
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 3
      Average Execution Time : 261ms
      Last Execution Date : 2021-09-16 14:33:29 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:29 UTC<PHONE_NUMBER>000)
      metadata:
        version.major: 1
        version.minor: 10
        version.patch: 4
        version.raw: 1.10.4
        version.scheme: semver

    cpu
    ---
      Instance ID: cpu [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/cpu.d/conf.yaml.default
      Total Runs: 3
      Metric Samples: Last Run: 9, Total: 20
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-09-16 14:33:26 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:26 UTC<PHONE_NUMBER>000)

    disk (4.4.0)
    ------------
      Instance ID: disk:e5dffb8bef24336f [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/disk.d/conf.yaml.default
      Total Runs: 2
      Metric Samples: Last Run: 204, Total: 408
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 23ms
      Last Execution Date : 2021-09-16 14:33:18 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:18 UTC<PHONE_NUMBER>000)

    docker
    ------
      Instance ID: docker [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/docker.d/conf.yaml.default
      Total Runs: 2
      Metric Samples: Last Run: 248, Total: 496
      Events: Last Run: 2, Total: 2
      Service Checks: Last Run: 1, Total: 2
      Average Execution Time : 66ms
      Last Execution Date : 2021-09-16 14:33:25 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:25 UTC<PHONE_NUMBER>000)

    file_handle
    -----------
      Instance ID: file_handle [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/file_handle.d/conf.yaml.default
      Total Runs: 3
      Metric Samples: Last Run: 5, Total: 15
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-09-16 14:33:32 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:32 UTC<PHONE_NUMBER>000)

    io
    --
      Instance ID: io [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/io.d/conf.yaml.default
      Total Runs: 2
      Metric Samples: Last Run: 39, Total: 51
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-09-16 14:33:24 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:24 UTC<PHONE_NUMBER>000)

    kubelet (7.0.0)
    ---------------
      Instance ID: kubelet:5bbc63f3938c02f4 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/kubelet.d/conf.yaml.default
      Total Runs: 2
      Metric Samples: Last Run: 958, Total: 1,901
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 4, Total: 8
      Average Execution Time : 463ms
      Last Execution Date : 2021-09-16 14:33:15 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:15 UTC<PHONE_NUMBER>000)

    load
    ----
      Instance ID: load [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/load.d/conf.yaml.default
      Total Runs: 3
      Metric Samples: Last Run: 6, Total: 18
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-09-16 14:33:31 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:31 UTC<PHONE_NUMBER>000)

    memory
    ------
      Instance ID: memory [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/memory.d/conf.yaml.default
      Total Runs: 2
      Metric Samples: Last Run: 18, Total: 36
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-09-16 14:33:23 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:23 UTC<PHONE_NUMBER>000)

    network (2.3.0)
    ---------------
      Instance ID: network:d884b5186b651429 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/network.d/conf.yaml.default
      Total Runs: 3
      Metric Samples: Last Run: 73, Total: 219
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 10ms
      Last Execution Date : 2021-09-16 14:33:30 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:30 UTC<PHONE_NUMBER>000)

    ntp
    ---
      Instance ID: ntp:d884b5186b651429 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/ntp.d/conf.yaml.default
      Total Runs: 1
      Metric Samples: Last Run: 1, Total: 1
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 1
      Average Execution Time : 0s
      Last Execution Date : 2021-09-16 14:32:56 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:32:56 UTC<PHONE_NUMBER>000)

    uptime
    ------
      Instance ID: uptime [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/uptime.d/conf.yaml.default
      Total Runs: 2
      Metric Samples: Last Run: 1, Total: 2
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-09-16 14:33:22 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:33:22 UTC<PHONE_NUMBER>000)

========
JMXFetch
========

  Information
  ==================
  Initialized checks
  ==================
    no checks

  Failed checks
  =============
    no checks

=========
Forwarder
=========

  Transactions
  ============
    Cluster: 0
    CronJob: 0
    DaemonSet: 0
    Deployment: 0
    Dropped: 0
    DroppedOnInput: 0
    Job: 0
    Node: 0
    PersistentVolume: 0
    PersistentVolumeClaim: 0
    Pod: 0
    ReplicaSet: 0
    Requeued: 0
    Retried: 0
    RetryQueueSize: 0
    Service: 0
    StatefulSet: 0

  Transaction Successes
  =====================
    Total number: 7
    Successes By Endpoint:
      check_run_v1: 2
      intake: 3
      series_v1: 2

  API Keys status
  ===============
    API key ending with 330c5: API Key valid

==========
Endpoints
==========
  https://app.datadoghq.com - API Key ending with:
      - 330c5

==========
Logs Agent
==========

  Logs Agent is not running

=========
APM Agent
=========
  Status: Running
  Pid: 1
  Uptime: 44 seconds
  Mem alloc: 10,581,840 bytes
  Hostname: i-07f24cfb6cb2e6b70
  Receiver: <IP_ADDRESS>:8126
  Endpoints:
    https://trace.agent.datadoghq.com

  Receiver (previous minute)
  ==========================
    No traces received in the previous minute.
    Default priority sampling rate: 100.0%

  Writer (previous minute)
  ========================
    Traces: 0 payloads, 0 traces, 0 events, 0 bytes
    Stats: 0 payloads, 0 stats buckets, 0 bytes

=========
Aggregator
=========
  Checks Metric Sample: 6,130
  Dogstatsd Metric Sample: 276
  Event: 3
  Events Flushed: 3
  Number Of Flushes: 2
  Series Flushed: 4,125
  Service Check: 42
  Service Checks Flushed: 33
=========
DogStatsD
=========
  Event Packets: 0
  Event Parse Errors: 0
  Metric Packets: 275
  Metric Parse Errors: 0
  Service Check Packets: 0
  Service Check Parse Errors: 0
  Udp Bytes: 21,072
  Udp Packet Reading Errors: 0
  Udp Packets: 215
  Uds Bytes: 0
  Uds Origin Detection Errors: 0
  Uds Packet Reading Errors: 0
  Uds Packets: 1
  Unterminated Metric Errors: 0

=====================
Datadog Cluster Agent
=====================

  - Datadog Cluster Agent endpoint detected: https://<IP_ADDRESS>:5005
  Successfully connected to the Datadog Cluster Agent.
  - Running: 1.15.0+commit.6781e85

Additional environment details (Operating System, Cloud provider, etc):
Datadog Helm chart 2.22.2
EKS 1.21
Cilium 1.10.4
Steps to reproduce the issue:

Create an EKS cluster
Deploy Datadog with network policies flavour cilium and custom agent.confd: to collect Cilium operator metrics

  confd:
    cilium.yaml: |-
      instances:
        - agent_endpoint: http://localhost:9090/metrics
          tags:
            - cilium-pod:%%host%%
        - operator_endpoint: http://localhost:6942/metrics
          tags:
            - cilium-pod:%%host%%

Replace AWS CNI with Cilium

Describe the results you received:
$ agent check cilium
...
=== Service Checks ===
[
  {
    "check": "cilium.prometheus.health",
    "host_name": "i-07f24cfb6cb2e6b70",
    "timestamp":<PHONE_NUMBER>,
    "status": 0,
    "message": "",
    "tags": [
      "cilium-pod:<IP_ADDRESS>",
      "docker_image:quay.io/cilium/cilium",
      "endpoint:http://<IP_ADDRESS>:9090/metrics",
      "image_name:quay.io/cilium/cilium",
      "image_tag:v1.10.4",
      "kube_container_name:cilium-agent",
      "kube_daemon_set:cilium",
      "kube_namespace:kube-system",
      "kube_ownerref_kind:daemonset",
      "pod_phase:running",
      "short_image:cilium"
    ]
  }
]
2021-09-16 14:50:44 UTC | CORE | INFO | (pkg/util/kubernetes/clustername/clustername.go:98 in getClusterName) | Using cluster name sandbox-infra-2036 auto discovered from the ec2 API
2021-09-16 14:50:44 UTC | CORE | INFO | (pkg/metadata/host/host_tags.go:88 in GetHostTags) | Adding both tags cluster_name and kube_cluster_name. You can use 'disable_cluster_name_tag_key' in the Agent config to keep the kube_cluster_name tag only
2021-09-16 14:50:44 UTC | CORE | WARN | (pkg/util/gce/gce_tags.go:49 in getCachedTags) | unable to get tags from gce and cache is empty: status code 404 trying to GET http://<IP_ADDRESS>/computeMetadata/v1/?recursive=true
2021-09-16 14:50:44 UTC | CORE | INFO | (pkg/metadata/host/host.go:170 in getPublicIPv4) | No public IPv4 address found
=========
Collector
=========

  Running Checks
  ==============

    cilium (1.7.2)
    --------------
      Instance ID: cilium:50ebf894b0a553d7 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/cilium.d/auto_conf.yaml
      Total Runs: 1
      Metric Samples: Last Run: 971, Total: 971
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 1
      Average Execution Time : 295ms
      Last Execution Date : 2021-09-16 14:50:41 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-09-16 14:50:41 UTC<PHONE_NUMBER>000)
      metadata:
        version.major: 1
        version.minor: 10
        version.patch: 4
        version.raw: 1.10.4
        version.scheme: semver

=== Service Checks ===
[
  {
    "check": "cilium.prometheus.health",
    "host_name": "i-07f24cfb6cb2e6b70",
    "timestamp":<PHONE_NUMBER>,
    "status": 2,
    "message": "",
    "tags": [
      "cilium-pod:%%host%%",
      "endpoint:http://localhost:9090/metrics"
    ]
  }
]
=========
Collector
=========

  Running Checks
  ==============

    cilium (1.7.2)
    --------------
      Instance ID: cilium:8eb256ce5f51f2ec [ERROR]
      Configuration Source: file:/etc/datadog-agent/conf.d/cilium.yaml
      Total Runs: 1
      Metric Samples: Last Run: 0, Total: 0
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 1
      Average Execution Time : 8ms
      Last Execution Date : 2021-09-16 14:50:44 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : Never
      Error: HTTPConnectionPool(host='localhost', port=9090): Max retries exceeded with url: /metrics (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f785920e910>: Failed to establish a new connection: [Errno 111] Connection refused'))
      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py", line 169, in _new_conn
          conn = connection.create_connection(
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/util/connection.py", line 96, in create_connection
          raise err
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/util/connection.py", line 86, in create_connection
          sock.connect(sa)
      ConnectionRefusedError: [Errno 111] Connection refused

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connectionpool.py", line 699, in urlopen
          httplib_response = self._make_request(
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connectionpool.py", line 394, in _make_request
          conn.request(method, url, **httplib_request_kw)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py", line 234, in request
          super(HTTPConnection, self).request(method, url, body=body, headers=headers)
        File "/opt/datadog-agent/embedded/lib/python3.8/http/client.py", line 1256, in request
          self._send_request(method, url, body, headers, encode_chunked)
        File "/opt/datadog-agent/embedded/lib/python3.8/http/client.py", line 1302, in _send_request
          self.endheaders(body, encode_chunked=encode_chunked)
        File "/opt/datadog-agent/embedded/lib/python3.8/http/client.py", line 1251, in endheaders
          self._send_output(message_body, encode_chunked=encode_chunked)
        File "/opt/datadog-agent/embedded/lib/python3.8/http/client.py", line 1011, in _send_output
          self.send(msg)
        File "/opt/datadog-agent/embedded/lib/python3.8/http/client.py", line 951, in send
          self.connect()
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py", line 200, in connect
          conn = self._new_conn()
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py", line 181, in _new_conn
          raise NewConnectionError(
      urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f785920e910>: Failed to establish a new connection: [Errno 111] Connection refused

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
          resp = conn.urlopen(
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connectionpool.py", line 755, in urlopen
          retries = retries.increment(
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/util/retry.py", line 574, in increment
          raise MaxRetryError(_pool, url, error or ResponseError(cause))
      urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='localhost', port=9090): Max retries exceeded with url: /metrics (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f785920e910>: Failed to establish a new connection: [Errno 111] Connection refused'))

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py", line 1006, in run
          self.check(instance)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/openmetrics/base_check.py", line 135, in check
          self.process(scraper_config)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/openmetrics/mixins.py", line 533, in process
          for metric in self.scrape_metrics(scraper_config):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/openmetrics/mixins.py", line 470, in scrape_metrics
          response = self.poll(scraper_config)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/openmetrics/mixins.py", line 780, in poll
          response = self.send_request(endpoint, scraper_config, headers)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/openmetrics/mixins.py", line 806, in send_request
          return http_handler.get(endpoint, stream=True, **kwargs)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/utils/http.py", line 304, in get
          return self._request('get', url, options)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/utils/http.py", line 368, in _request
          response = self.make_request_aia_chasing(request_method, method, url, new_options, persist)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/utils/http.py", line 373, in make_request_aia_chasing
          response = request_method(url, **new_options)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/api.py", line 76, in get
          return request('get', url, params=params, **kwargs)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/api.py", line 61, in request
          return session.request(method=method, url=url, **kwargs)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/sessions.py", line 542, in request
          resp = self.send(prep, **send_kwargs)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/sessions.py", line 655, in send
          r = adapter.send(request, **kwargs)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/adapters.py", line 516, in send
          raise ConnectionError(e, request=request)
      requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=9090): Max retries exceeded with url: /metrics (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f785920e910>: Failed to establish a new connection: [Errno 111] Connection refused'))

=== Service Checks ===
[
  {
    "check": "cilium.prometheus.health",
    "host_name": "i-07f24cfb6cb2e6b70",
    "timestamp":<PHONE_NUMBER>,
    "status": 2,
    "message": "",
    "tags": [
      "cilium-pod:%%host%%",
      "endpoint:http://localhost:6942/metrics"
    ]
  }
]
=========
Collector
=========

  Running Checks
  ==============

    cilium (1.7.2)
    --------------
      Instance ID: cilium:10d6f36b45683928 [ERROR]
      Configuration Source: file:/etc/datadog-agent/conf.d/cilium.yaml
      Total Runs: 1
      Metric Samples: Last Run: 0, Total: 0
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 1
      Average Execution Time : 3ms
      Last Execution Date : 2021-09-16 14:50:44 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : Never
      Error: HTTPConnectionPool(host='localhost', port=6942): Max retries exceeded with url: /metrics (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f785899a6d0>: Failed to establish a new connection: [Errno 111] Connection refused'))
      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py", line 169, in _new_conn
          conn = connection.create_connection(
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/util/connection.py", line 96, in create_connection
          raise err
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/util/connection.py", line 86, in create_connection
          sock.connect(sa)
      ConnectionRefusedError: [Errno 111] Connection refused

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connectionpool.py", line 699, in urlopen
          httplib_response = self._make_request(
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connectionpool.py", line 394, in _make_request
          conn.request(method, url, **httplib_request_kw)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py", line 234, in request
          super(HTTPConnection, self).request(method, url, body=body, headers=headers)
        File "/opt/datadog-agent/embedded/lib/python3.8/http/client.py", line 1256, in request
          self._send_request(method, url, body, headers, encode_chunked)
        File "/opt/datadog-agent/embedded/lib/python3.8/http/client.py", line 1302, in _send_request
          self.endheaders(body, encode_chunked=encode_chunked)
        File "/opt/datadog-agent/embedded/lib/python3.8/http/client.py", line 1251, in endheaders
          self._send_output(message_body, encode_chunked=encode_chunked)
        File "/opt/datadog-agent/embedded/lib/python3.8/http/client.py", line 1011, in _send_output
          self.send(msg)
        File "/opt/datadog-agent/embedded/lib/python3.8/http/client.py", line 951, in send
          self.connect()
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py", line 200, in connect
          conn = self._new_conn()
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py", line 181, in _new_conn
          raise NewConnectionError(
      urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f785899a6d0>: Failed to establish a new connection: [Errno 111] Connection refused

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
          resp = conn.urlopen(
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connectionpool.py", line 755, in urlopen
          retries = retries.increment(
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/util/retry.py", line 574, in increment
          raise MaxRetryError(_pool, url, error or ResponseError(cause))
      urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='localhost', port=6942): Max retries exceeded with url: /metrics (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f785899a6d0>: Failed to establish a new connection: [Errno 111] Connection refused'))

      During handling of the above exception, another exception occurred:

      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py", line 1006, in run
          self.check(instance)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/openmetrics/base_check.py", line 135, in check
          self.process(scraper_config)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/openmetrics/mixins.py", line 533, in process
          for metric in self.scrape_metrics(scraper_config):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/openmetrics/mixins.py", line 470, in scrape_metrics
          response = self.poll(scraper_config)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/openmetrics/mixins.py", line 780, in poll
          response = self.send_request(endpoint, scraper_config, headers)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/openmetrics/mixins.py", line 806, in send_request
          return http_handler.get(endpoint, stream=True, **kwargs)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/utils/http.py", line 304, in get
          return self._request('get', url, options)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/utils/http.py", line 368, in _request
          response = self.make_request_aia_chasing(request_method, method, url, new_options, persist)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/utils/http.py", line 373, in make_request_aia_chasing
          response = request_method(url, **new_options)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/api.py", line 76, in get
          return request('get', url, params=params, **kwargs)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/api.py", line 61, in request
          return session.request(method=method, url=url, **kwargs)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/sessions.py", line 542, in request
          resp = self.send(prep, **send_kwargs)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/sessions.py", line 655, in send
          r = adapter.send(request, **kwargs)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/adapters.py", line 516, in send
          raise ConnectionError(e, request=request)
      requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=6942): Max retries exceeded with url: /metrics (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f785899a6d0>: Failed to establish a new connection: [Errno 111] Connection refused'))

Check has run only once, if some metrics are missing you can try again with --check-rate to see any other metric if available.

Describe the results you expected:
Datadog agent to see that the operator PODs do not run in all the nodes but in the ones it does it should collect the metrics from localhost because Cilium operator container runs with hostNetwork: true
Additional information you deem important (e.g. issue happens only occasionally):

Open ticket with Support
https://help.datadoghq.com/hc/en-us/requests/561708

I tried to add the following configuration to the Cilium deployment to get around this
  podAnnotations:
    ad.datadoghq.com/cilium-operator.check_names: |
      ["prometheus"]
    ad.datadoghq.com/cilium-operator.init_configs: |
      [{}]
    ad.datadoghq.com/cilium-operator.instances: |
      [{
        "prometheus_url": "http://localhost:6942/metrics",
        "namespace": "cilium.operator",
        "prometheus_metrics_prefix": "cilium_operator_",
        "metrics": [
          "cilium_operator*"
        ]
      }]

but I get this error
2021-09-16 15:53:35 UTC | CORE | DEBUG | (pkg/collector/python/check.go:81 in runCheck) | Running python check prometheus prometheus:cilium.operator:b5985cb3036a54d4
2021-09-16 15:53:47 UTC | CORE | DEBUG | (pkg/util/docker/containers.go:319 in parseContainerNetworkAddresses) | No IP found for container /k8s_POD_cilium-operator-df89ff7bb-5dhbn_kube-system_4edbb29a-f410-4264-ac23-888d274a6d3b_0 in network 4581bdee8dbc413226f52a5a08e1924fd7f7020ac74ec9bcf6e235907c756031
2021-09-16 15:53:50 UTC | CORE | DEBUG | (pkg/collector/python/check.go:81 in runCheck) | Running python check prometheus prometheus:cilium.operator:b5985cb3036a54d4
2021-09-16 15:54:02 UTC | CORE | DEBUG | (pkg/util/docker/containers.go:319 in parseContainerNetworkAddresses) | No IP found for container /k8s_POD_cilium-operator-df89ff7bb-5dhbn_kube-system_4edbb29a-f410-4264-ac23-888d274a6d3b_0 in network 4581bdee8dbc413226f52a5a08e1924fd7f7020ac74ec9bcf6e235907c756031
2021-09-16 15:54:05 UTC | CORE | DEBUG | (pkg/collector/python/check.go:81 in runCheck) | Running python check prometheus prometheus:cilium.operator:b5985cb3036a54d4
2021-09-16 15:54:06 UTC | CORE | DEBUG | (pkg/serializer/serializer.go:361 in sendMetadata) | Sending metadata payload, content: {"apiKey":"***************************330c5","agentVersion":"7.31.0","uuid":"ec2be081-c98f-5000-f84d-2953aee1555d","internalHostname":"i-0f34ff17ca274440a","meta":{"socket-hostname":"datadog-55lsc","timezones":["UTC"],"socket-fqdn":"datadog-55lsc","ec2-hostname":"ip-10-0-138-2.eu-west-2.compute.internal","hostname":"i-0f34ff17ca274440a","host_aliases":["ip-10-0-138-2.eu-west-2.compute.internal-sandbox-infra-2036"],"instance-id":"i-0f34ff17ca274440a"},"agent_checks":[["uptime","uptime","uptime","OK","",""],["io","io","io","OK","",""],["docker","docker","docker","OK","",""],["network","network","network:d884b5186b651429","OK","",""],["file_handle","file_handle","file_handle","OK","",""],["disk","disk","disk:e5dffb8bef24336f","OK","",""],["load","load","load","OK","",""],["ntp","ntp","ntp:d884b5186b651429","OK","",""],["cpu","cpu","cpu","OK","",""],["prometheus","prometheus","prometheus:cilium.operator:b5985cb3036a54d4","ERROR","[{\"message\": \"HTTPConnectionPool(host='localhost', port=6942): Max retries exceeded with url: /metrics (Caused by NewConnectionError('\u003curllib3.connection.HTTPConnection object at 0x7f55a706cbe0\u003e: Failed to establish a new connection: [Errno 111] Connection refused'))\", \"traceback\": \"Traceback (most recent call last):\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py\\\", line 169, in _new_conn\\n    conn = connection.create_connection(\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/util/connection.py\\\", line 96, in create_connection\\n    raise err\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/util/connection.py\\\", line 86, in create_connection\\n    sock.connect(sa)\\nConnectionRefusedError: [Errno 111] Connection refused\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connectionpool.py\\\", line 699, in urlopen\\n    httplib_response = self._make_request(\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connectionpool.py\\\", line 394, in _make_request\\n    conn.request(method, url, **httplib_request_kw)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py\\\", line 234, in request\\n    super(HTTPConnection, self).request(method, url, body=body, headers=headers)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/http/client.py\\\", line 1256, in request\\n    self._send_request(method, url, body, headers, encode_chunked)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/http/client.py\\\", line 1302, in _send_request\\n    self.endheaders(body, encode_chunked=encode_chunked)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/http/client.py\\\", line 1251, in endheaders\\n    self._send_output(message_body, encode_chunked=encode_chunked)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/http/client.py\\\", line 1011, in _send_output\\n    self.send(msg)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/http/client.py\\\", line 951, in send\\n    self.connect()\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py\\\", line 200, in connect\\n    conn = self._new_conn()\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connection.py\\\", line 181, in _new_conn\\n    raise NewConnectionError(\\nurllib3.exceptions.NewConnectionError: \u003curllib3.connection.HTTPConnection object at 0x7f55a706cbe0\u003e: Failed to establish a new connection: [Errno 111] Connection refused\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/adapters.py\\\", line 439, in send\\n    resp = conn.urlopen(\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/connectionpool.py\\\", line 755, in urlopen\\n    retries = retries.increment(\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/urllib3/util/retry.py\\\", line 574, in increment\\n    raise MaxRetryError(_pool, url, error or ResponseError(cause))\\nurllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='localhost', port=6942): Max retries exceeded with url: /metrics (Caused by NewConnectionError('\u003curllib3.connection.HTTPConnection object at 0x7f55a706cbe0\u003e: Failed to establish a new connection: [Errno 111] Connection refused'))\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py\\\", line 1006, in run\\n    self.check(instance)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/prometheus/base_check.py\\\", line 106, in check\\n    scraper.process(\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/prometheus/mixins.py\\\", line 408, in process\\n    for metric in self.scrape_metrics(endpoint, instance=instance):\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/prometheus/mixins.py\\\", line 370, in scrape_metrics\\n    response = self.poll(endpoint, instance=instance)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/prometheus/mixins.py\\\", line 579, in poll\\n    response = handler.get(endpoint, extra_headers=headers, stream=False)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/utils/http.py\\\", line 304, in get\\n    return self._request('get', url, options)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/utils/http.py\\\", line 368, in _request\\n    response = self.make_request_aia_chasing(request_method, method, url, new_options, persist)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/utils/http.py\\\", line 373, in make_request_aia_chasing\\n    response = request_method(url, **new_options)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/api.py\\\", line 76, in get\\n    return request('get', url, params=params, **kwargs)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/api.py\\\", line 61, in request\\n    return session.request(method=method, url=url, **kwargs)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/sessions.py\\\", line 542, in request\\n    resp = self.send(prep, **send_kwargs)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/sessions.py\\\", line 655, in send\\n    r = adapter.send(request, **kwargs)\\n  File \\\"/opt/datadog-agent/embedded/lib/python3.8/site-packages/requests/adapters.py\\\", line 516, in send\\n    raise ConnectionError(e, request=request)\\nrequests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=6942): Max retries exceeded with url: /metrics (Caused by NewConnectionError('\u003curllib3.connection.HTTPConnection object at 0x7f55a706cbe0\u003e: Failed to establish a new connection: [Errno 111] Connection refused'))\\n\"}]",""],["cilium","cilium","cilium:27817d543812944b","OK","",""],["memory","memory","memory","OK","",""],["kubelet","kubelet","kubelet:5bbc63f3938c02f4","OK","",""]],"external_host_tags":[]}
2021-09-16 15:54:06 UTC | CORE | DEBUG | (pkg/serializer/serializer.go:396 in SendProcessesMetadata) | Sent processes metadata payload, content: {"resources":{"processes":{"snaps":[[1631807646,[["root",0,1.9401227606177893,1693675520,159879168,"agent",1],["root",0,1.6291702847531393,867598336,134254592,"cilium-agent",1],["root",0,1.5459646510259295,1442926592,127397888,"dockerd",1],["root",0,1.4956635152242947,1940283392,123252736,"kubelet",1],["root",0,1.390587822452896,11619074048,114593792,"containerd-shim",16],["root",0,1.1055811893633973,1420955648,91107328,"process-agent",1],["root",0,1.0159139472822227,727703552,83718144,"fluent-bit",1],["root",0,0.8097389361110959,791531520,66727936,"cilium-operator-aws",1],["root",0,0.795573102412019,789254144,65560576,"amazon-cloudwatch-agent",1],["root",0,0.6422341657044669,2049032192,52924416,"containerd",1],["root",0,0.6085840975842035,1234808832,50151424,"trace-agent",1],["root",0,0.5132505220233979,765571072,42295296,"kube-proxy",1],["root",0,0.42109804595992906,746876928,34701312,"ssm-agent-worker",1],["root",0,0.2841616535355187,706072576,23416832,"journald-cloudwatch-logs",1],["root",0,0.21323307568084227,733892608,17571840,"amazon-ssm-agent",1],["root",0,0.1461317581588989,48701440,12042240,"systemd-journald",1],["root",0,0.11968886858728862,232226816,9863168,"rsyslogd",1],["root",0,0.10865442970590238,206159872,8953856,"dhclient",2],["root",0,0.10542362552891993,198672384,8687616,"systemd",1],["root",0,0.08827551105108995,113426432,7274496,"sshd",1]]]]},"meta":{"host":"i-0f34ff17ca274440a"}}}
2021-09-16 15:54:17 UTC | CORE | DEBUG | (pkg/util/docker/containers.go:319 in parseContainerNetworkAddresses) | No IP found for container /k8s_POD_cilium-operator-df89ff7bb-5dhbn_kube-system_4edbb29a-f410-4264-ac23-888d274a6d3b_0 in network 4581bdee8dbc413226f52a5a08e1924fd7f7020ac74ec9bcf6e235907c756031
2021-09-16 15:54:20 UTC | CORE | DEBUG | (pkg/collector/python/check.go:81 in runCheck) | Running python check prometheus prometheus:cilium.operator:b5985cb3036a54d4
2021-09-16 15:54:32 UTC | CORE | DEBUG | (pkg/util/docker/containers.go:319 in parseContainerNetworkAddresses) | No IP found for container /k8s_POD_cilium-operator-df89ff7bb-5dhbn_kube-system_4edbb29a-f410-4264-ac23-888d274a6d3b_0 in network 4581bdee8dbc413226f52a5a08e1924fd7f7020ac74ec9bcf6e235907c756031

Hi @carlosjgp ,

Datadog agent to see that the operator PODs do not run in all the nodes but in the ones it does it should collect the metrics from localhost because Cilium operator container runs with hostNetwork: true

Are you able to see the cilium operator's prometheus metrics by running curl localhost:6942/metrics from any pod?
The best way to monitor the cilium operator would be to utilize the Cluster Agent and endpointchecks. Currently if you're using just the Daemonset Agent, autodiscovery is going to attempt to search for cilium container image names and running the check on them.
You can set annotations in the service pointing to your resource or mount a conf.yaml file in the Cluster Agent, and the Cluster Agent will schedule the configuration to be run on one of the node agents.
I'll also follow up on the support case with this information, and if you need help configuring Cluster Agent/endpoint checks, it'll be easiest to communicate via your support ticket.

Thanks for your response @ChristineTChen,
The metrics are available
$ kubectl -n kube-system port-forward cilium-operator-6fc456995d-xt4wm 6942 &
$ curl localhost:6942/metrics
# HELP cilium_operator_ec2_api_duration_seconds Duration of interactions with API
# TYPE cilium_operator_ec2_api_duration_seconds histogram
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.05"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.1"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.25"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.5"} 1
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="1"} 2
....

$ kubectl -n kube-system get deployment -oyaml cilium-operator
apiVersion: apps/v1
kind: Deployment
metadata:
  name: cilium-operator
  namespace: kube-system
spec:
  template:
    metadata:
      annotations:
        ad.datadoghq.com/cilium-operator.check_names: |
          ["prometheus"]
        ad.datadoghq.com/cilium-operator.init_configs: |
          [{}]
        ad.datadoghq.com/cilium-operator.instances: |
          [{
            "prometheus_url": "http://localhost:6942/metrics",
            "namespace": "cilium.operator",
            "prometheus_metrics_prefix": "cilium_operator_",
            "metrics": [
              "cilium_operator*"
            ]
          }]
        cilium.io/cilium-configmap-checksum: b32ad69321e1446475065fc81465e4dbb1e63282c84262b7bc2cb3b2a12e065d
        prometheus.io/port: "6942"
        prometheus.io/scrape: "true"
    spec:
      <...>
      containers:
      - name: cilium-operator
        <...>
      hostNetwork: true
      <...>

My NetworkPolicy since I'm running Cilium on "strict" mode. Everything block by default.
apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
  name: datadog-agent
  namespace: datadog
spec:
  description: "datadog agent can retrieve metrics from cilium"
  endpointSelector:
    matchLabels:
      app.kubernetes.io/component: agent
      app.kubernetes.io/name: datadog
  egress:
    - toEntities:
        - host
      toPorts:
        - ports:
            - port: "9090" # Cilium daemonset prometheus
              protocol: TCP
            - port: "6942" # Cilium operator prometheus
              protocol: TCP
            - port: "51678" # ECS docker daemonset
              protocol: TCP

Cilium does not create a Service by default. Only does it when using Prometheus Operator and it does not accept annotations
https://github.com/cilium/cilium/blob/2a46fd67267716efd58311064e4a91abfa2a0a1c/install/kubernetes/cilium/templates/cilium-operator-service.yaml#L1
So I guess I'll need to create the service manually and create a PR for Cilium
I'll try that now
Could you please, in the meanwhile update the integration documentation to reflect this... It's a requirement since there is no other way to make it work.

The cilium-operator endpoint option is not enabled by default in the conf.d/cilium.d/auto-conf.yaml because the operator should be monitored at the cluster level.
The best way to monitor the cilium operator would be to utilize the Cluster Agent and endpointchecks. Currently if you're using just the Daemonset Agent, autodiscovery is going to attempt to search for cilium container image names and running the check on them.

Thanks

I created this Kubernetes service
apiVersion: v1
kind: Service
metadata:
  annotations:
    ad.datadoghq.com/endpoints.check_names: |2
        ["cilium"]
    ad.datadoghq.com/endpoints.init_configs: '[{}]'
    ad.datadoghq.com/endpoints.instances: |2
        [{
          "operator_endpoint": "http://localhost:6942/metrics"
        }]
  creationTimestamp: "2021-09-17T10:57:09Z"
  labels:
    io.cilium/app: operator
    name: cilium-operator
  name: cilium-operator
  namespace: kube-system
  resourceVersion: "4387361"
  uid: dee39aa2-8dfd-4abc-af4c-96eb32c4c6d1
spec:
  clusterIP: None
  clusterIPs:
  - None
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - name: metrics
    port: 6942
    protocol: TCP
    targetPort: prometheus
  selector:
    io.cilium/app: operator
    name: cilium-operator
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

Run the checks on the cluster agent
agent clusterchecks kube_endpoints
2021-09-17 11:28:34 UTC | CLUSTER | WARN | (pkg/util/log/log.go:611 in func1) | Agent configuration relax permissions constraint on the secret backend cmd, Group can read and exec
2021-09-17 11:28:34 UTC | CLUSTER | INFO | (pkg/util/log/log.go:596 in func1) | Features detected from environment: kubernetes,orchestratorexplorer
=== 4 agents reporting ===

Name                  Running checks
i-01908335e2f43641d   0
i-05aff1351566e52e9   0
i-07f24cfb6cb2e6b70   0
i-0f34ff17ca274440a   0

===== 2 Pod-backed Endpoints-Checks scheduled =====

=== cilium check ===
Configuration provider: kubernetes-endpoints
Configuration source: kube_endpoints:kube_endpoint_uid://kube-system/cilium-operator/
Instance ID: cilium:97a5afed876a46b8
operator_endpoint: http://localhost:6942/metrics
tags:
- kube_namespace:kube-system
- kube_endpoint_ip:<IP_ADDRESS>
- cluster_name:sandbox-infra-2036
- kube_cluster_name:sandbox-infra-2036
- kube_service:cilium-operator
~
Init Config:
{}
Auto-discovery IDs:
* kube_endpoint_uid://kube-system/cilium-operator/<IP_ADDRESS>
* kubernetes_pod://cd84bd19-218b-4800-bff1-fe89c8e2f6d9
State: dispatched to ip-10-0-67-197.eu-west-2.compute.internal
===

=== cilium check ===
Configuration provider: kubernetes-endpoints
Configuration source: kube_endpoints:kube_endpoint_uid://kube-system/cilium-operator/
Instance ID: cilium:32167634ae367f86
operator_endpoint: http://localhost:6942/metrics
tags:
- kube_endpoint_ip:<IP_ADDRESS>
- cluster_name:sandbox-infra-2036
- kube_cluster_name:sandbox-infra-2036
- kube_service:cilium-operator
- kube_namespace:kube-system
~
Init Config:
{}
Auto-discovery IDs:
* kube_endpoint_uid://kube-system/cilium-operator/<IP_ADDRESS>
* kubernetes_pod://7d7d97b8-8da6-418d-b61c-5ed2bb5c2dd0
State: dispatched to ip-10-0-80-150.eu-west-2.compute.internal
===

But I'm still not seeing the cilium.operator metrics in the dashboard... is there something I'm missing out?
Regards

Hey @carlosjgp ,
I noticed that you port-forwarded the port in your earlier comment. The curl to localhost only works here because you forwarded the port of the cilium-operator.
$ kubectl -n kube-system port-forward cilium-operator-6fc456995d-xt4wm 6942 &
$ curl localhost:6942/metrics

I don't think localhost:6942/metrics is going to yield the same output in the Datadog agent container. You test this out by running the curl from an Agent pod.

All the changes distracted me from changing the address. Now that we are using the Kubernetes Endpoints provided by the headless Kubernetes service the autodiscovery configuration should use %%host%% instead of localhost
I'll test the changes next week and confirm this
Thanks!

@ChristineTChen I've changed the Kubernetes Service to
apiVersion: v1
kind: Service
metadata:
  annotations:
    ad.datadoghq.com/endpoints.check_names: |2
        ["cilium"]
    ad.datadoghq.com/endpoints.init_configs: '[{}]'
    ad.datadoghq.com/endpoints.instances: |2
        [{
          "operator_endpoint": "http://%%host%%:6942/metrics"
        }]
  creationTimestamp: "2021-09-23T11:48:11Z"
  labels:
    io.cilium/app: operator
    name: cilium-operator
  name: cilium-operator
  namespace: kube-system
  resourceVersion: "889"
  uid: 4695103a-fd48-4dee-ad55-630aff7b8a1a
spec:
  clusterIP: None
  clusterIPs:
  - None
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - name: metrics
    port: 6942
    protocol: TCP
    targetPort: prometheus
  selector:
    io.cilium/app: operator
    name: cilium-operator
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

and some metrics are coming through but the eni metrics are missing
https://github.com/DataDog/integrations-core/blob/3bf453a3a3021a3561bb469e2bdc53345c74ed08/cilium/metadata.csv#L86
these are the metrics reported by the endpoints... not sure if the integration is not aligned with the latest version
$ http :6942/metrics
HTTP/1.1 200 OK
Content-Encoding: gzip
Content-Type: text/plain; version=0.0.4; charset=utf-8
Date: Thu, 23 Sep 2021 14:10:12 GMT
Transfer-Encoding: chunked

# HELP cilium_operator_ec2_api_duration_seconds Duration of interactions with API
# TYPE cilium_operator_ec2_api_duration_seconds histogram
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="0.05"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="0.1"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="0.25"} 1
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="0.5"} 1
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="1"} 1
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="2.5"} 1
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="5"} 1
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="10"} 1
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="400 Bad Request",le="+Inf"} 1
cilium_operator_ec2_api_duration_seconds_sum{operation="AssignPrivateIpAddresses",response_code="400 Bad Request"} 0.23135696
cilium_operator_ec2_api_duration_seconds_count{operation="AssignPrivateIpAddresses",response_code="400 Bad Request"} 1
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="0.05"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="0.1"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="0.25"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="0.5"} 27
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="1"} 31
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="2.5"} 31
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="5"} 31
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="10"} 31
cilium_operator_ec2_api_duration_seconds_bucket{operation="AssignPrivateIpAddresses",response_code="OK",le="+Inf"} 31
cilium_operator_ec2_api_duration_seconds_sum{operation="AssignPrivateIpAddresses",response_code="OK"} 12.696850304000002
cilium_operator_ec2_api_duration_seconds_count{operation="AssignPrivateIpAddresses",response_code="OK"} 31
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="0.05"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="0.1"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="0.25"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="0.5"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="1"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="2.5"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="5"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="10"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="AttachNetworkInterface",response_code="OK",le="+Inf"} 6
cilium_operator_ec2_api_duration_seconds_sum{operation="AttachNetworkInterface",response_code="OK"} 4.438756557
cilium_operator_ec2_api_duration_seconds_count{operation="AttachNetworkInterface",response_code="OK"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="0.05"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="0.1"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="0.25"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="0.5"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="1"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="2.5"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="5"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="10"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="CreateNetworkInterface",response_code="OK",le="+Inf"} 6
cilium_operator_ec2_api_duration_seconds_sum{operation="CreateNetworkInterface",response_code="OK"} 2.150708164
cilium_operator_ec2_api_duration_seconds_count{operation="CreateNetworkInterface",response_code="OK"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.05"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.1"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.25"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="0.5"} 1
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="1"} 2
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="2.5"} 3
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="5"} 3
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="10"} 3
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeInstanceTypes",response_code="OK",le="+Inf"} 3
cilium_operator_ec2_api_duration_seconds_sum{operation="DescribeInstanceTypes",response_code="OK"} 3.101410602
cilium_operator_ec2_api_duration_seconds_count{operation="DescribeInstanceTypes",response_code="OK"} 3
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="0.05"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="0.1"} 53
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="0.25"} 165
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="0.5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="1"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="2.5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="10"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeNetworkInterfaces",response_code="OK",le="+Inf"} 187
cilium_operator_ec2_api_duration_seconds_sum{operation="DescribeNetworkInterfaces",response_code="OK"} 28.074180134999985
cilium_operator_ec2_api_duration_seconds_count{operation="DescribeNetworkInterfaces",response_code="OK"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="0.05"} 62
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="0.1"} 147
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="0.25"} 183
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="0.5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="1"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="2.5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="10"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSecurityGroups",response_code="OK",le="+Inf"} 187
cilium_operator_ec2_api_duration_seconds_sum{operation="DescribeSecurityGroups",response_code="OK"} 15.041272080000004
cilium_operator_ec2_api_duration_seconds_count{operation="DescribeSecurityGroups",response_code="OK"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="0.05"} 50
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="0.1"} 165
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="0.25"} 186
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="0.5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="1"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="2.5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="10"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeSubnets",response_code="OK",le="+Inf"} 187
cilium_operator_ec2_api_duration_seconds_sum{operation="DescribeSubnets",response_code="OK"} 13.831217826
cilium_operator_ec2_api_duration_seconds_count{operation="DescribeSubnets",response_code="OK"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="0.05"} 36
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="0.1"} 174
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="0.25"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="0.5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="1"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="2.5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="5"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="10"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="DescribeVpcs",response_code="OK",le="+Inf"} 187
cilium_operator_ec2_api_duration_seconds_sum{operation="DescribeVpcs",response_code="OK"} 12.977870312
cilium_operator_ec2_api_duration_seconds_count{operation="DescribeVpcs",response_code="OK"} 187
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="0.05"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="0.1"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="0.25"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="0.5"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="1"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="2.5"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="5"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="10"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="ModifyNetworkInterface",response_code="OK",le="+Inf"} 6
cilium_operator_ec2_api_duration_seconds_sum{operation="ModifyNetworkInterface",response_code="OK"} 2.041397425
cilium_operator_ec2_api_duration_seconds_count{operation="ModifyNetworkInterface",response_code="OK"} 6
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="0.005"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="0.01"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="0.025"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="0.05"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="0.1"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="0.25"} 0
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="0.5"} 10
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="1"} 11
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="2.5"} 11
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="5"} 11
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="10"} 11
cilium_operator_ec2_api_duration_seconds_bucket{operation="UnassignPrivateIpAddresses",response_code="OK",le="+Inf"} 11
cilium_operator_ec2_api_duration_seconds_sum{operation="UnassignPrivateIpAddresses",response_code="OK"} 4.651491499
cilium_operator_ec2_api_duration_seconds_count{operation="UnassignPrivateIpAddresses",response_code="OK"} 11
# HELP cilium_operator_ipam_allocation_ops Number of IP allocation operations
# TYPE cilium_operator_ipam_allocation_ops counter
cilium_operator_ipam_allocation_ops{subnet_id=""} 8
cilium_operator_ipam_allocation_ops{subnet_id="subnet-050ab937fc1ba4722"} 25
cilium_operator_ipam_allocation_ops{subnet_id="subnet-093cfaadcf479e274"} 45
cilium_operator_ipam_allocation_ops{subnet_id="subnet-0cc1b55b90a1d2c1e"} 33
# HELP cilium_operator_ipam_available Number of interfaces with addresses available
# TYPE cilium_operator_ipam_available gauge
cilium_operator_ipam_available 8
# HELP cilium_operator_ipam_available_ips_per_subnet Number of available IPs per subnet ID
# TYPE cilium_operator_ipam_available_ips_per_subnet gauge
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2a",subnet_id="subnet-03e72a9bc01bce4c6"} 4089
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2a",subnet_id="subnet-04186dc8ef5d4e794"} 2043
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2a",subnet_id="subnet-0538f25a008a3cef1"} 4090
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2a",subnet_id="subnet-06dc2975ecfaac653"} 8162
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2a",subnet_id="subnet-081d8446c51b8aa91"} 8165
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2a",subnet_id="subnet-0b060ec0685577f53"} 2043
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2a",subnet_id="subnet-0bf434aad9bfb54e4"} 2043
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2a",subnet_id="subnet-0cc1b55b90a1d2c1e"} 8162
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2a",subnet_id="subnet-0fff7033462214d3a"} 4090
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2b",subnet_id="subnet-04e046eb66e981a4b"} 4090
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2b",subnet_id="subnet-05b040db4850f7a94"} 4089
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2b",subnet_id="subnet-0645b722f52d106b3"} 8171
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2b",subnet_id="subnet-08082fa995b360737"} 2043
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2b",subnet_id="subnet-093cfaadcf479e274"} 8170
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2b",subnet_id="subnet-0aa5b807d89329147"} 8162
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2b",subnet_id="subnet-0d77ef0f555dbf8f6"} 4090
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2b",subnet_id="subnet-0d9ffbcf0d29d208e"} 2042
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2b",subnet_id="subnet-0fb8f775d578f0390"} 2043
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2c",subnet_id="subnet-00f0ba4a69f7776b7"} 4089
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2c",subnet_id="subnet-050ab937fc1ba4722"} 8171
cilium_operator_ipam_available_ips_per_subnet{availability_zone="eu-west-2c",subnet_id="subnet-050c8ac0920277789"} 2043
# HELP cilium_operator_ipam_deficit_resolver_duration_seconds Duration of trigger runs
# TYPE cilium_operator_ipam_deficit_resolver_duration_seconds histogram
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="0.005"} 1
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="0.01"} 1
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="0.025"} 1
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="0.05"} 1
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="0.1"} 1
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="0.25"} 1
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="0.5"} 37
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="1"} 43
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="2.5"} 49
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="5"} 49
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="10"} 49
cilium_operator_ipam_deficit_resolver_duration_seconds_bucket{le="+Inf"} 49
cilium_operator_ipam_deficit_resolver_duration_seconds_sum 26.325254403
cilium_operator_ipam_deficit_resolver_duration_seconds_count 49
# HELP cilium_operator_ipam_deficit_resolver_folds Current level of folding
# TYPE cilium_operator_ipam_deficit_resolver_folds gauge
cilium_operator_ipam_deficit_resolver_folds 1
# HELP cilium_operator_ipam_deficit_resolver_latency_seconds Latency between queue and trigger run
# TYPE cilium_operator_ipam_deficit_resolver_latency_seconds histogram
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="0.005"} 48
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="0.01"} 48
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="0.025"} 48
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="0.05"} 48
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="0.1"} 49
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="0.25"} 49
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="0.5"} 49
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="1"} 49
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="2.5"} 49
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="5"} 49
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="10"} 49
cilium_operator_ipam_deficit_resolver_latency_seconds_bucket{le="+Inf"} 49
cilium_operator_ipam_deficit_resolver_latency_seconds_sum 0.096260007
cilium_operator_ipam_deficit_resolver_latency_seconds_count 49
# HELP cilium_operator_ipam_deficit_resolver_queued_total Number of queued triggers
# TYPE cilium_operator_ipam_deficit_resolver_queued_total counter
cilium_operator_ipam_deficit_resolver_queued_total 49
# HELP cilium_operator_ipam_interface_creation_ops Number of interfaces allocated
# TYPE cilium_operator_ipam_interface_creation_ops counter
cilium_operator_ipam_interface_creation_ops{status="ip assignment failed",subnet_id="subnet-0cc1b55b90a1d2c1e"} 1
cilium_operator_ipam_interface_creation_ops{status="success",subnet_id=""} 5
cilium_operator_ipam_interface_creation_ops{status="success",subnet_id="subnet-050ab937fc1ba4722"} 8
cilium_operator_ipam_interface_creation_ops{status="success",subnet_id="subnet-093cfaadcf479e274"} 14
cilium_operator_ipam_interface_creation_ops{status="success",subnet_id="subnet-0cc1b55b90a1d2c1e"} 10
# HELP cilium_operator_ipam_ips Number of IPs allocated
# TYPE cilium_operator_ipam_ips gauge
cilium_operator_ipam_ips{type="available"} 24
cilium_operator_ipam_ips{type="needed"} 0
cilium_operator_ipam_ips{type="used"} 26
# HELP cilium_operator_ipam_k8s_sync_duration_seconds Duration of trigger runs
# TYPE cilium_operator_ipam_k8s_sync_duration_seconds histogram
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="0.005"} 406
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="0.01"} 406
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="0.025"} 408
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="0.05"} 421
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="0.1"} 436
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="0.25"} 455
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="0.5"} 459
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="1"} 459
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="2.5"} 459
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="5"} 459
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="10"} 459
cilium_operator_ipam_k8s_sync_duration_seconds_bucket{le="+Inf"} 459
cilium_operator_ipam_k8s_sync_duration_seconds_sum 5.935880092000001
cilium_operator_ipam_k8s_sync_duration_seconds_count 459
# HELP cilium_operator_ipam_k8s_sync_folds Current level of folding
# TYPE cilium_operator_ipam_k8s_sync_folds gauge
cilium_operator_ipam_k8s_sync_folds 1
# HELP cilium_operator_ipam_k8s_sync_latency_seconds Latency between queue and trigger run
# TYPE cilium_operator_ipam_k8s_sync_latency_seconds histogram
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="0.005"} 450
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="0.01"} 450
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="0.025"} 451
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="0.05"} 451
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="0.1"} 459
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="0.25"} 459
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="0.5"} 459
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="1"} 459
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="2.5"} 459
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="5"} 459
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="10"} 459
cilium_operator_ipam_k8s_sync_latency_seconds_bucket{le="+Inf"} 459
cilium_operator_ipam_k8s_sync_latency_seconds_sum 0.7804985829999991
cilium_operator_ipam_k8s_sync_latency_seconds_count 459
# HELP cilium_operator_ipam_k8s_sync_queued_total Number of queued triggers
# TYPE cilium_operator_ipam_k8s_sync_queued_total counter
cilium_operator_ipam_k8s_sync_queued_total 459
# HELP cilium_operator_ipam_nodes Number of nodes by category { total | in-deficit | at-capacity }
# TYPE cilium_operator_ipam_nodes gauge
cilium_operator_ipam_nodes{category="at-capacity"} 0
cilium_operator_ipam_nodes{category="in-deficit"} 0
cilium_operator_ipam_nodes{category="total"} 3
# HELP cilium_operator_ipam_release_ops Number of IP release operations
# TYPE cilium_operator_ipam_release_ops counter
cilium_operator_ipam_release_ops{subnet_id="subnet-050ab937fc1ba4722"} 3
cilium_operator_ipam_release_ops{subnet_id="subnet-093cfaadcf479e274"} 13
cilium_operator_ipam_release_ops{subnet_id="subnet-0cc1b55b90a1d2c1e"} 11
# HELP cilium_operator_ipam_resync_duration_seconds Duration of trigger runs
# TYPE cilium_operator_ipam_resync_duration_seconds histogram
cilium_operator_ipam_resync_duration_seconds_bucket{le="0.005"} 0
cilium_operator_ipam_resync_duration_seconds_bucket{le="0.01"} 0
cilium_operator_ipam_resync_duration_seconds_bucket{le="0.025"} 0
cilium_operator_ipam_resync_duration_seconds_bucket{le="0.05"} 0
cilium_operator_ipam_resync_duration_seconds_bucket{le="0.1"} 0
cilium_operator_ipam_resync_duration_seconds_bucket{le="0.25"} 0
cilium_operator_ipam_resync_duration_seconds_bucket{le="0.5"} 30
cilium_operator_ipam_resync_duration_seconds_bucket{le="1"} 47
cilium_operator_ipam_resync_duration_seconds_bucket{le="2.5"} 47
cilium_operator_ipam_resync_duration_seconds_bucket{le="5"} 47
cilium_operator_ipam_resync_duration_seconds_bucket{le="10"} 47
cilium_operator_ipam_resync_duration_seconds_bucket{le="+Inf"} 47
cilium_operator_ipam_resync_duration_seconds_sum 22.617617665999997
cilium_operator_ipam_resync_duration_seconds_count 47
# HELP cilium_operator_ipam_resync_folds Current level of folding
# TYPE cilium_operator_ipam_resync_folds gauge
cilium_operator_ipam_resync_folds 1
# HELP cilium_operator_ipam_resync_latency_seconds Latency between queue and trigger run
# TYPE cilium_operator_ipam_resync_latency_seconds histogram
cilium_operator_ipam_resync_latency_seconds_bucket{le="0.005"} 42
cilium_operator_ipam_resync_latency_seconds_bucket{le="0.01"} 42
cilium_operator_ipam_resync_latency_seconds_bucket{le="0.025"} 42
cilium_operator_ipam_resync_latency_seconds_bucket{le="0.05"} 42
cilium_operator_ipam_resync_latency_seconds_bucket{le="0.1"} 42
cilium_operator_ipam_resync_latency_seconds_bucket{le="0.25"} 43
cilium_operator_ipam_resync_latency_seconds_bucket{le="0.5"} 46
cilium_operator_ipam_resync_latency_seconds_bucket{le="1"} 47
cilium_operator_ipam_resync_latency_seconds_bucket{le="2.5"} 47
cilium_operator_ipam_resync_latency_seconds_bucket{le="5"} 47
cilium_operator_ipam_resync_latency_seconds_bucket{le="10"} 47
cilium_operator_ipam_resync_latency_seconds_bucket{le="+Inf"} 47
cilium_operator_ipam_resync_latency_seconds_sum 1.7370706419999995
cilium_operator_ipam_resync_latency_seconds_count 47
# HELP cilium_operator_ipam_resync_queued_total Number of queued triggers
# TYPE cilium_operator_ipam_resync_queued_total counter
cilium_operator_ipam_resync_queued_total 49
# HELP cilium_operator_ipam_resync_total Number of resync operations to synchronize and resolve IP deficit of nodes
# TYPE cilium_operator_ipam_resync_total counter
cilium_operator_ipam_resync_total 186
# HELP cilium_operator_process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE cilium_operator_process_cpu_seconds_total counter
cilium_operator_process_cpu_seconds_total 23.03
# HELP cilium_operator_process_max_fds Maximum number of open file descriptors.
# TYPE cilium_operator_process_max_fds gauge
cilium_operator_process_max_fds 1.048576e+06
# HELP cilium_operator_process_open_fds Number of open file descriptors.
# TYPE cilium_operator_process_open_fds gauge
cilium_operator_process_open_fds 17
# HELP cilium_operator_process_resident_memory_bytes Resident memory size in bytes.
# TYPE cilium_operator_process_resident_memory_bytes gauge
cilium_operator_process_resident_memory_bytes 7.624704e+07
# HELP cilium_operator_process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE cilium_operator_process_start_time_seconds gauge
cilium_operator_process_start_time_seconds 1.632397815e+09
# HELP cilium_operator_process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE cilium_operator_process_virtual_memory_bytes gauge
cilium_operator_process_virtual_memory_bytes 7.91793664e+08
# HELP cilium_operator_process_virtual_memory_max_bytes Maximum amount of virtual memory available in bytes.
# TYPE cilium_operator_process_virtual_memory_max_bytes gauge
cilium_operator_process_virtual_memory_max_bytes -1

Datadog support team has confirmed that the integration is not up to date and the metrics are not aligned.
It has been suggested to use Prometheus integration as a workaround to ingest these metrics


fix_license

I'm really in need of an example module or a reference repository.
To avoid that kind of mistakes.

the AFL license is twice in the license file.


[Bug]: Cannot load extension with file or directory name version.py. Filenames starting with "" are reserved for use by the system ;  Could not load manifest.

What happened?
Hello.
I'm using Ubuntu 23.04 and Chrome Version 117.0.5938.92 (Official Build) (64-bit). I'm trying to load your extension,but I see two different errors :
Error 1 :
Cannot load extension with file or directory name version.py. Filenames starting with "" are reserved for use by the system.
Error 2 : Could not load manifest.
How to fix them ?
Expected Result
That it has been able to load correctly.
Branch
master/main
What operating systems are you seeing the problem on?
Linux/Unix
Relevant log output
Cannot load extension with file or directory name _version.py. Filenames starting with "_" are reserved for use by the system ;  Could not load manifest.

Other information
No response

What the fuck.... this isn't a chrome extension....


Paging only a part of a page

Great example for a whole page that gets refreshed. What about an example that has a top section that doesn't change and needs the lower section to be paged. I can't find a complete example that pulls together Razor Pages and Ajax to achieve paging of only a part of the page. e.g. An order with lot's of order lines. You don't want to keep loading the order when the user just wants to see the next page of order-line items.

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3cf283c9-5cd2-a9ff-b8c8-372d8a04356d
Version Independent ID: 729fddcf-24e4-b563-4952-a8045b231868
Content: ASP.NET Core SignalR JavaScript client
Content Source: aspnetcore/signalr/javascript-client.md
Product: aspnet-core
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

Sorry, wrong page ;-(    I had two pages open and put a comment in the wrong one. My bad.


⚠ Samsung has degraded performance

In 8edc697, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2829 ms

Resolved: Samsung performance has improved in 8562621.


Extract quotes

Extract more or less short quotes from the transcript in caption.sbv and insert them into quotes.md.

I started with a single quote.


[Feature Request]: define better the repo and owner of the github plugin

Define better the repo and owner of the github plugin

Done


[Feature Request] Add optional context parameter to operators

Sometimes the function you want to some operators is not small, or sometimes you just want to reuse that function for multiple operators. Anyway, when you do that you end up by doing something like .map(this.myMethod.bind(this)) or .map(value => this.myMethod(value)).
That's ok, they both work, but if you're using typescript the second will lose the return type, and the second option is too much code repeated (this case is just one param, but what about if you're expecting 2 o 3?)
Instead, it would be really helpful if you add a final optional argument with the context like this .map(this.myMethod, this). This does not introduce any breaking change, and it would be super helpful to keep the typing in typescript.

Ok sorry, taking a look at the source code I can see there are some methods that have the thisArg?, but not all of them. Specifically the distinctUntilChange. Is this for any special reason?

It's because binding context is being deprecated and supposed to be supported only specific api surface which corresponds to native api such as map. One of major api surface change introducdd in v5 is actually removing thisArg, you can refer detailed discussions at https://github.com/ReactiveX/rxjs/issues/878.

So in case of specific cases of map, it is supported via current impmementation. (https://github.com/ReactiveX/rxjs/blob/master/src/operator/map.ts#L38)

.map(this.myMethod.bind(this)) will lose the return type.   I'm not seeing how .map(value => this.myMethod(value)) would the lose the return type, as it the types should flow very nicely.
As @kwonoj has stated, it's just one less part of the api surface that we're looking to support every where for all operators.  With some of the more complicated operators it becomes very hard to model, especially in TypeScript.
Personally I've  more or less started just doing fat arrows everywhere, and that seems to work fairly well.

@kwonoj a shame you're removing the thisArg :( it doesn't look consistent actually to have some methods with it and some other without it. But I understand your reasons :/
@david-driscoll I didn't say the arrow method was a problem with the types, only bind. The problem with the arrow function (besides the unnecessary closure created) is that you need to copy over all the parameters.
Consider .concatMapTo(obs, (outerValue, innerValue, outerIndex, innerIndex) => this.myCustomConcat(outerValue, innerValue, outerIndex, innerIndex)).
It's just too much code, it doesn't even fit in a single line.

Using bind is more explicit and easier to read for the next developer. The thisArg would look more like a magic argument at first blush.

Regardless, this feature has been discussed in the past, and I don't think we're going to implement it. I do appreciate your point of view and your suggestion, though. If it's okay with you, ins like to close this issue. Please feel free to reopen or comment if you'd like to continue discussion.

.concatMapTo(obs, (...args) => this.myCustomConcat(...args))

@trxcllnt it won't transmit the types definitions in typescript and will give an error that params does not match

If you don't use a selector function, the result will be a tuple of all the
input types. You can then destructure the tuple to get the strongly typed
values out.
On Fri, Sep 30, 2016 at 12:16 PM Diego Barahona<EMAIL_ADDRESS>wrote:

@trxcllnt https://github.com/trxcllnt it won't transmit the types
definitions in typescript and will give an error that params does not match
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ReactiveX/rxjs/issues/1988#issuecomment-250787049,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNdpQdz_5_yYw1WPyUIdZOaFhzPPM9oks5qvTXQgaJpZM4KIUMz
.

--
Thanks,
David


DPL-754 Traction to receive QC data endpoint from queue

User story
As TOL I want traction to have a new endpoint to receive QC data.
Qc columns
Sheared Femto Fragment Size (bp)
Post SPRI Concentration (ng/ul)
Post SPRI Volume (ul)
Final NanoDrop 260/280
Final NanoDrop 260/230
Final NanoDrop ng/ul
Shearing & QC comments (if applicable)
Date submitted
Priority level (if High or Medium)
Date data required by
Reason for priority
Who are the primary contacts for this story
Eduardo Martin
Who is the nominated tester for UAT
Charlie (TOL)
Acceptance criteria
To be considered successful the solution must allow:

[ ] HTTP endpoint that will receive this data
[ ] Data will be stored in Traction database as it happens currently

Dependencies
This story is blocked by the following dependencies:

#<issue_no.>
sanger/#<issue_no.>

References
This story has a non-blocking relationship with:

#<issue_no.>
sanger/#<issue_no.>

Additional context
Add any other context or screenshots about the feature request here.

This story specifies receiving and recording data from the queue into Traction, but we are not clear on how the data fields below will be used or viewed.
Is data required for the lab to adjust the sample processes?
When will the data be viewed or queried?
Who will be viewing or querying this data?
@SujitDey2022 is this something you could help us refine?
Fields for the above questions:
Sheared Femto Fragment Size (bp)
Post SPRI Concentration (ng/ul)
Post SPRI Volume (ul)
Final NanoDrop 260/280
Final NanoDrop 260/230
Final NanoDrop ng/ul
Shearing & QC comments (if applicable)

I have caught up with James from the Long Read team.
Getting these field into the MLWH is the best option in the short term.  He doesn't (yet) need to see these from within Traction, but Tableua report connecting to this data from MLWH will be a good first step.

Questions:

@Sangeetha-Bheeman  were you working on something similar?
Currently QcResults in Traction require the fields labware_barcode and sample_external_id, might these be provided too?

@harrietc52  yes, this is part of what am working now in consumer and I will be working on this soon on traction-service.

Traction Service tasks

[ ] update schema to add new columns for qc_results table (Date submitted, Priority level (if High or Medium), Date data required by, Reason for priority). These are optional/ only required for TOL?
[ ] new route in resource, for endpoint to create multiple qc results
[ ] new controller for route
[ ] new resource for route
[ ] new factory, possibly being passed all the qc results to create. this loops through, creating the qc result, and if successful, building the message
[ ] in factory, get the relevant assay types, using the tol used_by to filter them
[ ] in factory, validation required assay types are present
[ ] in the resource, if creation of qc results successful, access messages from the factory
[ ] add config to build MLWH message to pipelines.yml. this wants to be similar to the existing qc_result message (but without qc_decision etc). But it also wants to add new qc result fields such as (Date submitted, Priority level (if High or Medium), Date data required by, Reason for priority)
[ ] publish message using factory messages and config
[ ] edit rake task to add new assay types (confirm keys with tol, and check required units)
[ ] add new used_by to assay type model for tol

MLWH / Unified WH tasks

[ ] update MLWH table, via migration in unified warehouse, to add new qc_result fields (date submitted etc) possibly? See design of traction MLWH table here
[ ] check MLWH table inserts new qc assay type fields and values correctly

[ ] Validation
[ ] Tests for app/models/qc_receptions_factory.rb
[ ] Tests for the v1/qc_receptions requests  - controller and resource
[ ] Testing the message.publish
[ ] Test the assay type for ToL
[ ]

From Steve - Update from meeting 27/07: date_required_by and reason_for_priority are no longer required and can be removed. priority_level is not a qc_result attribute but should be moved to sample.


[BUG]Error: Destroy older clusters created with older version of openshift-install-powervs with new version

Describe the bug
Clusters created using  older version (v1.7.0) of script openshift-install-powervs is difficult to delete and get error when executed with newer version of script (v1.9.0).
To Reproduce
Steps to reproduce the behavior: ./openshift-install-powervs destroy -ignore-os-checks -force-destroy
Expected behavior
The script should be able to destroy the older cluster without any issue created with previous versions of script
Console Output
Error when executed the newer version (v1.9.0) of script on older clusters:
$ ./openshift-install-powervs destroy -ignore-os-checks -force-destroy
[main] WARN: Ignoring operating system related checks
[main] WARN: Enabling forceful destruction option for terraform destroy command
[setup_occli] Installing the stable version of OpenShift CLI...
Attempt: 1/5
Client Version: 4.12.16
Kustomize Version: v4.5.7
[destroy] Running terraform destroy... please wait
Attempt: 1/5
[retry_terraform] Encountered below errors:
│ Error: Inconsistent dependency lock file
[retry_terraform] WARN: Issues were seen while running the terraform command. Attempting to run again...
Attempt: 2/5
[retry_terraform] Encountered below errors:
│ Error: Inconsistent dependency lock file
[retry_terraform] WARN: Issues were seen while running the terraform command. Attempting to run again...
Attempt: 3/5
[retry_terraform] Encountered below errors:
│ Error: Inconsistent dependency lock file
[retry_terraform] WARN: Issues were seen while running the terraform command. Attempting to run again...
Attempt: 4/5
[retry_terraform] Encountered below errors:
│ Error: Inconsistent dependency lock file
[retry_terraform] WARN: Issues were seen while running the terraform command. Attempting to run again...
Attempt: 5/5
[retry_terraform] Encountered below errors:
│ Error: Inconsistent dependency lock file

Desktop (please complete the following information):

OS: fedora
Version: 33
Windows terminal: ssh (vscode)

Additional context
Add any other context about the problem here.

@yussufsh

could you try the below command and re-run?
rm automation/.terraform.lock.hcl

Hacky solution was provided.
The issue faced is related to Terraform maintaining the version in the lock file.


M2 Updates

@jnvtnguyen Is this ready for review yet?

@seanlip Sorry for delay, will finish by EOD, adding the SSH settings as well to getting started page.

PTAL @seanlip, Thanks.

PTAL @seanlip, Thanks.

Thanks, just one comment left.


[dv] mem test enhancements

As discussed with Tim, we can consider to add these 2 enhancements, but these seem not very urgent.

Test RO/WO memory from backdoor. Currently we only test memory from front-door for RW type memory in existing automatic mem/csr tests. For RO/WO memory, only error cases (such as writing to RO mem or reading WO mem will result in d_error=1) are covered by tl_error test and we rely on block owners to create the test to verify the other functionality.

We don't support excluding a memory in automatic mem/csr tests. If we can test RO memory from backdoor in automatic tests, we need to exclude the RO memory in flash_ctrl, as it will trigger an error if SW reads or writes more than what it's configured.

@tjaychen @sriyerg @cindychip @matutem

estimate 16

thanks for filing the issue Weicai.
On Sun, Dec 5, 2021 at 10:50 PM weicaiyang @.***> wrote:

As discussed with Tim, we can consider to add these 2 enhancements, but
these seem not very urgent.

Test RO/WO memory from backdoor. Currently we only test memory from
front-door for RW type memory in existing automatic mem/csr tests. For
RO/WO memory, only error cases (such as writing to RO mem or reading WO mem
will result in d_error=1) are covered by tl_error test and we rely on block
owners to create the test to verify the other functionality.
2.
We don't support excluding a memory in automatic mem/csr tests. If we
can test RO memory from backdoor in automatic tests, we need to exclude the
RO memory in flash_ctrl, as it will trigger an error if SW reads or writes
more than what it's configured.
@tjaychen https://github.com/tjaychen @sriyerg
https://github.com/sriyerg @cindychip https://github.com/cindychip
@matutem https://github.com/matutem
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/9532, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSXCCG7XBFEFGRYTKCTUPRMKZANCNFSM5JN3MWLA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

estimate range: 8 - 16

This issue is super old and it doesn't seem relevant anymore. I am thus closing it. Please feel free to reopen it if you disagree @matutem .


FloorCoeffs.h

hi, @koide3 ,your code include <hdl_slam_graph/FloorCoeffs.h>,but I can't find the FloorCoeffs.h

It is a custom message, so you can have a look at it inside <your_ws>/devel/include/hdl_graph_slam

Thanks @tuandle


Make linking the kubeconfig idempotent.

Previously there were situations where we needed to manually unlink the config, e.g., after build errors.
NONE

@joerg84: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.

One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.
Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hi @joerg84. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/assign @douglas-reid

/ok-to-test

/lgtm


I also put this in my .git/config:
[diff "adt"]
    textconv = "python -m proxyclient.m1n1.adt --sort-keys --sort-nodes"
    xfuncname = "^ *[a-zA-Z0-9_-]+ \\{$"

and this in .gitattributes:
*.adt   diff=adt

so that I am able to diff blobs directly, e.g. git diff --no-index DeviceTree.j51{6,4}map.adt