Macro of RMA IP Address

grussell · Post by **grussell** » Mon Feb 01, 2010 7:35 am

Hi,

I am reviewing my logs and notice a number return "localhost" despite the test being executed by an RMA.

Is there a variable I can use to get the RMA IP address?

Something like %rma_ipaddress%

I want to avoid getting people to define custom comments..etc.

Many thanks,

Gavin.

KS-Soft · Post by **KS-Soft** » Mon Feb 01, 2010 7:58 pm

I think you may use %TestedObjectInfo% variable.
If you set "localhost" or "127.0.0.1" as target address and test is performed by the agent, this variable will show address of the agent (IP address or hostname, depends on option you have used when setup agent).

Regards
Alex

grussell · Post by **grussell** » Tue Feb 02, 2010 3:30 am

Thanks for the workaround - but would be great to have a variable which always returns the agent IP address (if it's not too difficult?)

Many thanks,

Gavin.

KS-Soft · Post by **KS-Soft** » Tue Feb 02, 2010 12:04 pm

%Agent% variable is not good enough?
You need just IP address, not hostname or name of the agent?

Regards
Alex

grussell · Post by **grussell** » Tue Feb 02, 2010 4:07 pm

Ideally an IP address - it will help our engineers ensure that should "localhost" be the IP address, the agent IP takes precedence. It is just to clear up any potential ambiguity arise from a logged event for "host" not actually being that host because its performed via an Agent.

While on the subject of agents - I don't suppose its possible to specify the agent in a variable - so tests moved from folder to folder (with the variable set) will automatically use the correct agent?

Thank you.

p.s. Keep up the great work - I've seen a lot of monitoring solutions and AHM ticks more boxes than the rest. There are some real strokes of genius in the package.

KS-Soft · Post by **KS-Soft** » Tue Feb 02, 2010 6:52 pm

Ideally an IP address - it will help our engineers ensure that should "localhost" be the IP address, the agent IP takes precedence. It is just to clear up any potential ambiguity arise from a logged event for "host" not actually being that host because its performed via an Agent.

Ok, I have added "low" priority task into "to do" list

p.s. Keep up the great work - I've seen a lot of monitoring solutions and AHM ticks more boxes than the rest. There are some real strokes of genius in the package.

Thank you

Regards
Alex