From version GA3.7 and above, the Gateway can accept right-click commands through REST service like from the Active Console. You may refer to another article using REST and "curl" as example. This article talks about a workaround for older gateway versions.
This can be achieved by using a toolkit that scans a file which is modified externally to set the status of the entity. Also, create two rules where one is for setting the severity and another one for checking and applying the snooze/unsnooze command.
You can refer to the attached file below of the article for a template of your setup
In your own setup.xml file, copy the Sampler, Actions, and Rules part of the autosnooze.setup.xml as shown in the picture below
|Make sure that the Targets of your Rules are correctly directed to your the Managed Entity that you wish to remotely snooze.|
The files attached below the article are the files that will be scanned by your toolkit.
In your command line, copy these files to your "entity.out" file to which corresponds to your needs:
cp entity.OK entity.out (Snooze off)
cp entity.Snooze entity.out (Snooze On)
You need to create multiple toolkit samplers for each Managed Entity that you would like to 'snooze' remotely where each of the toolkit sampler will point to a different 'entity.out' file. All you have to do is set a different name for each and connect them accordingly.
e.g. If you have 3 managed entities, namely: ME1, ME2, ME3; you need to have 3 copies of the Entity-Status samplers (i.e. Entity1-status, Entity2-status, Entity3-status). Then add these samplers to their corresponding managed entities. In this case, you need to define 3 'entity.out' files for each of the samplers (i.e. entity1.out, entity2.out, entity3.out). If you want to snooze ME1, copy the 'entity.Snooze' file attached above and overwrite entity1.out (cp entity.Snooze entity.out); unsnoozing will be to copy-over 'entity.OK' to entity1.out (cp entity.OK entity.out) as shown in the syntax above.