Forum Discussion

Stephen_C's avatar
Stephen_C
Icon for Neophyte rankNeophyte
9 months ago

Process monitoring (Linux)

I have a requirement to monitoring Linux processes - and am really hoping that someone has done something similar. Initially I thought the datasource "LinuxNewProcesses_byProperty" would meet the re...
  • Anonymous's avatar
    Anonymous
    9 months ago

    You wouldn't need to use the API. You could just build a property source that reads in the list of groups the device belongs to using `hostProps.get("system.groups")` or `hostProps.get("system.staticgroups")` and builds a single property to apply to the device. You wouldn't need the API at all.

    It could look something like this:

    propValue = []
hostProps.get("syste.groups").each{group->
    switch(expression){
        case "Applications/App A":
            propValue.add("app_a_service"); break;
        case "Another group/Tartanic":
            propValue.add("tartanic_process_name"); break;
        // etc.
    }
}
println(propValue.join("|"))
return 0

    This is off-the-cuff code; tweak as necessary.

Anonymous's avatar
Anonymous

Ah, i see what you mean now. You would definitely not want to specify this property in more than one branch of the tree. If you did, the inheritance would be not determinable. Well, technically, the "deeper" group would win. Two groups with the same depth would go based on group id (can't remember if it's highest or lowest that wins). 

So, you would either want to limit yourself to a single branch of the tree where this property is defined, or you would want to create a dedicated group structure where this is defined. There is no merging of properties when it comes to property inheritance.

We are an MSP, so we have a branch of our tree that branches per customer then has subgroups under each customer. This is where we specify properties like this. The device exists in other groups, but we don't specify properties like this on those other groups. By keeping these properties only on the customers branch of the tree, we only have to worry about parent/child inheritance instead of trying to figure out 2nd cousin inheritance as well (if that makes sense). 

The same applies for threshold overrides. We only do threshold overrides on this customers branch of the group tree. Global overrides happen at /Customers while other overrides go somewhere under there.

Stephen_C's avatar
Stephen_C
Icon for Neophyte rankNeophyte
9 months ago

Would it be a bit clunky to use the API to build process property name list based on group membership?

ie. server1 is in process(x) group and process(y) group, a property on the resource is then updated to monitor process-x and process-y

There are just so many variations on our side. Some servers have common processes, while others are very specific or have a combination of processes.

  • Anonymous's avatar
    Anonymous
    9 months ago

    You wouldn't need to use the API. You could just build a property source that reads in the list of groups the device belongs to using `hostProps.get("system.groups")` or `hostProps.get("system.staticgroups")` and builds a single property to apply to the device. You wouldn't need the API at all.

    It could look something like this:

    propValue = []
hostProps.get("syste.groups").each{group->
    switch(expression){
        case "Applications/App A":
            propValue.add("app_a_service"); break;
        case "Another group/Tartanic":
            propValue.add("tartanic_process_name"); break;
        // etc.
    }
}
println(propValue.join("|"))
return 0

    This is off-the-cuff code; tweak as necessary.

    • Anonymous's avatar
      Anonymous
      9 months ago

      Being able to populate/create this property using a property source is the very reason i built that DS based off a property.

    • Stephen_C's avatar
      Stephen_C
      Icon for Neophyte rankNeophyte
      9 months ago

      Fantastic! Thanks Stuart - for some reason the API just get coming back as a solution to me!

      • Anonymous's avatar
        Anonymous
        9 months ago

        The API is always an option. But sometimes there's an easier way.