Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hi, When I Use The Slack Monitoring Service It Creates A Link With

Hi, when I use the slack monitoring service it creates a link with task.get_output_log_web_page() However, this gives something like http://apiserver:8080/projects/9edb12212a104270a995378ec190f06a/experiments/25f4b3ebb7304db1a2216c2502cd90bd/output/log . This http://apiserver:8080 is a site that cannot be reached, what is going wrong here?

  
  
Posted 3 years ago
Votes Newest

Answers 17


I created it with clearml-init, nothing special. It looks like

# ClearML SDK configuration file api { # Notice: 'host' is the api server (default port 8008), not the web server. api_server: web_server: files_server: # Credentials are generated using the webapp, # Override with os environment: CLEARML_API_ACCESS_KEY / CLEARML_API_SECRET_KEY credentials {"access_key": "NMWOE5C3RGTX473M9D3M", "secret_key": "L@G50jO+TJ23#8Eerp1E$4y=elUt11P!BL2Ouas=1$GY-GxY%^"} } sdk { # ClearML - default SDK configuration

  
  
Posted 3 years ago

btw the same happens when I try this on localhost

# ClearML SDK configuration file api { # Notice: 'host' is the api server (default port 8008), not the web server. api_server: web_server: files_server: # Credentials are generated using the webapp, # Override with os environment: CLEARML_API_ACCESS_KEY / CLEARML_API_SECRET_KEY

  
  
Posted 3 years ago

Hi GreasyPenguin14 ,

What is the web server configure in your ~/clearml.conf file ( api.web_server )?

  
  
Posted 3 years ago

I enqueue to service to the services queue, not done anything myself with agents

  
  
Posted 3 years ago

Are you running the services with an agent?

Which version do you use?

  
  
Posted 3 years ago

Yes other then the link it generates it works fine

  
  
Posted 3 years ago

And all the others works as expected?

  
  
Posted 3 years ago

Version: 0.17.4

  
  
Posted 3 years ago

Hi GreasyPenguin14 ,
The reason for this is the Services Agent is not aware of the WebApp address, and tries to guess by using the ApiServer address (which internally, in docker-compose, is http://apiserver:8008 ) by replacing the port to 8080 .
To fix it, you simply need to specify the correct address by which the WebApp can be accessed when starting the server using docker-compose .

The easiest way to do that is to set the environment variable CLEARML_WEB_HOST before starting docker-compose, in your case:
> CLEARML_WEB_HOST= docker-compose -f /opt/clearml/docker-compose.yml up -d

  
  
Posted 3 years ago

I tried it but it doesnot work. I checked the clearml-agent-services container and it does have the right CLEARML_WEB_HOST
echo $CLEARML_WEB_HOST
http://192.168.4.1:8080
however, the messages on slack still point to apiserver:8080

  
  
Posted 3 years ago

GreasyPenguin14 I was able to reproduce it, will keep you update when a fix is ready

  
  
Posted 3 years ago

It seems there might be a bug there -we'll release an RC soon to fix it

  
  
Posted 3 years ago

Try it out and let us know 🙂

  
  
Posted 3 years ago

👍
let me check

  
  
Posted 3 years ago

Strange, I'll check

  
  
Posted 3 years ago

👍

  
  
Posted 3 years ago

👍

  
  
Posted 3 years ago