Search for configuration within the search bar

  • 5 July 2022
  • 1 reply


Iam searching for a possibility to return the configuration of defined alert rules in the logpoint search tab.

Background: I would like to report over icindents which are created by alert rules for a specific user group. We got several test alarms, which are “managed” by an other user and which should not appear in the report. So I have to combine the configuration of alert rules and the results with “repo_name="_logpoint" action="Alert received" | chart count () by alert_name, risk_level”.

Unfortunately I could not find a way to bring up the alert rule configuration with a search and combine the result with another search to narrow down the alert rules which I need to report. (I dont want to do that manually per hand by tyoing the names in the search)

I came over this idea because I have done such things with Splunk in the past. (was like an API-Call within the search bar to return internal configuration parameters) 

Is it even possible to get the configuration of the XXX back as a json/xml (or other) string?


Thanks in advance.



Best answer by Nils Krumey 18 July 2022, 12:03

View original

1 reply

Userlevel 3
Badge +7

Unfortunately, just like in your other question, the configuration of the alert rules is not held in a repository and therefore can’t be queried with the search language. Once an incident is generated some information is logged as an audit event, but again that does not include information about the alert configuration/ownership itself.

You should be able to use the Incident API to get this information, although it would require a CURL command or a script outside of Logpoint. Alternatively, perhaps a SOAR action could do that too - we do use some of the incident API when we use a SIEM incident to trigger into SOAR.

The list of incidents (https://LogPoint-IP/incidents) includes “username” and “assigned to” as the information. You can use https://LogPoint-IP/get_users to get a list of all the Logpoint users and their IDs.

I appreciate that that’s not in the search at all though and you would have to some external processing afterwards - perhaps you can raise an idea for us in the idea portal and describe what you would like to see / what you can do in Splunk? I think it would be great if we could do this without using the API externally...