Platform

Acure Life Hacks: Local Function for Event Name Conversion

3 minutes read
22 Dec 2022

In our publications, we often harp on Acure being a platform created by engineers for engineers. This means that in addition to improving service availability and data monitoring transparency, we also simplify the lives of end users – DevOps, SREs, IT admins and everyone else we protect from the 24/7 alert storms, calls at night and dozens of routine operations. This also includes constant work on updates, the implementation of new functionality and interface improvements in accordance with user requests. In addition to product support, we at Acure are also open to suggestions and ideas that users have while working with the system, which allow us to improve and open up new possibilities.

In this article, we want to share one of these life hacks, developed in collaboration with one of our clients, which makes the life of engineers much easier.

Elena Hawk
Content Manager at Acure.io
Share:
Blog
Platform
Acure Life Hacks: Local Function for Event Name Conversion

Acure allows you to connect data from a wide variety of monitoring tools. However, events from primary systems often have complex names that do not help to simplify the analysis of the state of the infrastructure. Often a time for decision-making is in short supply, so you need to reduce the cognitive load and make the data understandable for perception.

Let’s look at how to do this in Acure using regular expressions and a new local function.

Event name conversion examples

💡 Imagine that you receive a problematic event from the primary monitoring system with the name SomeHost: High CPU utilization (over 90% for 5m).

For this event, we can apply the following regular expression “High.CPU.util.*over.(\\d+)%.*” and open the Signal in a readable form, with the name “CPU > 90%”.

💡 There can be a lot of examples of such transformations, for example, here is another one for a data storage system:

  • Initial event name: “C:: Disk space is critically low (used > 90%)”
  • Regular expression: “(.*): Disk space.*used.>.(.*)%.*”
  • Resulting pattern: “$1 Storage Partition Usage > $2%”
  • Signal Name: “C: Storage Partition Usage > 90%”

✅ We have implemented this request in the automation script as a local function that instantly converts values according to the dictionary defined in the same function. Unlike hard-coded global functions, local functions are a playground where you can implement any of your ideas within a C# script.

How event name conversion works in Acure

👉 To repeat such conversions in Acure, you need to create a local function in the Automation script and transform the Signal name before opening the signal.

Conversion Function in Local Functions List
Conversion Function in Local Functions List

Function parameters:

🔵 Incoming pin – Input – a string containing the name of the event.

🔵 Outgoing pin – Result – a string containing the converted value.

Conversion Function in Low-code Scenario
Conversion Function in Low-code Scenario

📜 Function code:

var regexDict = new Dictionary<string, string>()

{

   {“(.*): Disk space.*used.>.(.*)%.*”,”$1: Storage partition usage > $2%”},

    {“High memory util.*>(\\d+)%.*”,”RAM usage > $1%”},

    {“High.CPU.util.*over.(\\d+)%.*”,”CPU Usage > $1%”},

};

foreach (var regex in regexDict)

{

    if (!System.Text.RegularExpressions.Regex.IsMatch(Input, regex.Key))

        continue;

    return System.Text.RegularExpressions.Regex.Replace(Input, regex.Key, System.Text.RegularExpressions.Regex.Replace(regex.Value, “$”, “”));

}

returnInput;

***

⚙️ If the function finds a regular expression in its dictionary that matches the original event name, this value will be converted according to the pattern specified in the dictionary. If there is no matching regular expression in the dictionary, the original value will be returned.

📖 Read more about the functionality of the automation engine in the corresponding section of the Documentation.

💬 Do not forget to share your cool ideas in our Community or Discord channel, and we will add them to our functionality in turn.

You may be also interested in:
Monitoring of Metrics and Other Features of Acure 2.2
Read more
Acure 2.1: Manual Signals, Table CMDB and Many More
Read more
Low-code as a Future of Development and Its Realization in Acure
Read more
ACURE 2.0 Is Officially Released
Read more
WEEKLY DEMO
SEE ACURE AIOPS IN THE ACTION
Join now

Subscribe now!

Hot threads, hilarious memes and a tons of DevOps inspiration

You could withdraw your consent at any time contacting by hello@acure.io

You may be also interested in:
Monitoring of Metrics and Other Features of Acure 2.2
Read more
Acure 2.1: Manual Signals, Table CMDB and Many More
Read more
Low-code as a Future of Development and Its Realization in Acure
Read more
ACURE 2.0 Is Officially Released
Read more