Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.43%. Comparing base (c241f67) to head (9ee4659).
⚠️ Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main    #7390      +/-   ##
==========================================
- Coverage   96.44%   96.43%   -0.02%     
==========================================
  Files         375      375              
  Lines       22878    22878              
==========================================
- Hits        22065    22062       -3     
- Misses        615      617       +2     
- Partials      198      199       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Tests failed

The original plan was to repoint the e2e test docker file to config-elasticsearch/opensearch. But the dilemma is that this config-es/os is used for es/os e2e test which requires

          server_urls:
            - http://localhost:9200

to run successfully. On the other hand, spm e2e test requires:

          server_urls:
            - http://elasticsearch:9200

to run successfully. I ask Gemmini to explain why we need - http://elasticsearch:9200 but not - http://localhost:9200. It says like this:

The issue you encountered is related to how Docker containers communicate with each other within a Docker network. Here's why changing localhost to elasticsearch fixed the problem:

Key Points:
Container Networking in Docker:

Each container in Docker has its own network namespace (its own "localhost")

localhost inside a container refers to that container itself, not the host machine or other containers

Containers can communicate with each other using their service names as hostnames

Your Specific Case:

When Jaeger was configured with http://localhost:9200, it was looking for Elasticsearch on its own local network (inside the Jaeger container), which didn't exist

When you changed it to http://elasticsearch:9200, it correctly looked for the Elasticsearch service in the Docker network

Docker Compose Networking:

Your services are connected via the backend network

Docker automatically sets up DNS resolution so containers can find each other by service name

The elasticsearch hostname resolves to the Elasticsearch container's IP within the Docker network

For this change, you can locally test the step I specify above and it runs good

Did you test that with these settings the commands I showed in the issue result in the Monitor tab being operational?

Yes I did test that.