Application Discovery - Match Step Predicate is not Matched

[Tom104]

Hi All,

Trying to discover installs of an in-house claims app we have,

I'm running a debug in pattern designer and am getting the following message:-

Test failed: Match step predicate is not matched. Failed Condition(s): [(${running_process_key_parameters} : value=) CONTAINS "claims"]

However, I've also run a quick discovery on the ci I'm debugging (Which I'm actually connected to, so know it's running), and it has indeed pulled back a running process where the key parameters contain "claims".

Any ideas at all? This is the first and only step at present.

Thanks

[Fabian Kunzke]

Hey,

the variable you are looking for usually does not exist in the pattern. The available process temporary variables are listed to the bottom right:

The closest you can get is probably using the process -> comandLine or something from the enviromental variables. The running process key parameters is a cmdb_ci value which is not accessible during the pattern. That value (and this is what you are noticing in the discovery) is filled during the process classification, but it is usually not carried over to the pattern (except with some advanced prepattern variable handling). However, the process classification usually fills that variable with information from the comandLine variable, which then should contain your "claims" part.

Hope this helps,

Regards,
Fabian

[Tom104]

Hi Fabian,

I don't see the process variable heading at all.

To clarify, I'm setting the operation to "Match".

I then get the commuter_system variable heading and the entry_point variable heading

None of these have the detail I want in, any thoughts on how I can get the "process" heading available?

[Fabian Kunzke]

Hey Tom,

If i understood correctly you are creating a discovery pattern for a horizontal application discovery, not service mapping, right? In that case there won't be any data in the "entry_point" variable as there is no "entry_point" within the debugging (when debugging, you will select "horizontal" and then select a host and process id). If you want to have access to the entry point data during the debugging you first have to select "top-down" in the debugging and then add the data for the debugging. However, during the horizontal discovery the entry point data is not present either - again, because there is no entry point in the service mapping sense.

Now your best alternative is to check for process information directly instead. This contains - ususally - the detail you will need. While debugging, this variable should appear as in the screenshot i posted.

Hope this helps,

Fabian