Konstantin

 i have the same problem, iscsid is running on all VM, i have this probles with only one of VM

``` 2023-07-24T22:13:28.614435Z WARN source{component_kind="source" component_id=kube_logs component_type=kubernetes_logs component_name=kube_logs}:file_server: vector::internal_events::file::source: Currently ignoring file too small to fingerprint. file=/var/log/pods/longhorn-system_engine-image-ei-74783864-5wpcs_18b56f61-37a5-4982-b99a-69204c0848a2/engine-image-ei-74783864/2.log 2023-07-24T22:13:28.614605Z WARN source{component_kind="source" component_id=kube_logs component_type=kubernetes_logs component_name=kube_logs}:file_server: vector::internal_events::file::source: Currently ignoring file too small to fingerprint....

any update ? how to setup ingress for tempo to send traces from more then from 1 cluster

also there is no distinct separation of topologies by namespaces. The current topology is terrible and awkward to use

scrape_interval: 15s Refresh interval: 15s

  

``` global: evaluation_interval: 1m scrape_interval: 15s scrape_timeout: 10s rule_files: - /etc/config/recording_rules.yml - /etc/config/alerting_rules.yml - /etc/config/rules - /etc/config/alerts scrape_configs: - job_name: prometheus static_configs: - targets: - localhost:9090 - bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token job_name:...

``` log-level: debug retention: 8h retention-levels: "0": 1h "1": 4h "2": 8h scrape-configs: - enabled-profiles: - cpu - mem job-name: kubernetes-pods kubernetes-sd-configs: - role: pod relabel-configs: - action: keep regex:...

 in the cluster 12 nodes

Running