Modify the configuration file structure and add parameter fields for subscription events

[yaofighting]

Modify the configuration file structure and add parameter fields for subscription events

Signed-off-by: yaofighting siyao@zju.edu.cn

Motivation

In some scenarios, only specifying the type of subscription event cannot meet our needs. Therefore, we need to enhance the features of the subscription part, support more detailed parameter lists, and control the CPP side to send only the event information we are concerned about to the Go side. For example, we need to specify system calls that filter latency is less than 500ms. When subscribing to events, we tell the CPP side to send only data that meets this condition, so as to avoid performance loss caused by data filtering on the Go side.

Related Issue

#366

[sanyangji]

LGTM.
We may unify the Naming Convention for cpp codes and cgo codes.
@dxsup @jundizhou

[dxsup]

LGTM.
We may unify the Naming Convention for cpp codes and cgo codes.
@dxsup @jundizhou

For example? I didn't see any difference on "Naming Convention" between these files. Do you mean the indentation style?

[sanyangji]

LGTM.
We may unify the Naming Convention for cpp codes and cgo codes.
@dxsup @jundizhou

For example? I didn't see any difference on "Naming Convention" between these files. Do you mean the indentation style?

void sub_event(char* eventName, char* category, event_params_for_subscribe params[]) Like In this line, eventName is different from others

[dxsup]

OK, so first let's determine the convention on naming, then we can rename them all.

[dxsup]

We can open another PR for the "naming convention". Back to this one, LGTM.

[yaofighting]

I think we should use underscore_case in C/C++ and camelCase in Golang.

[yaofighting]

I think we should use underscore_case in C/C++ and camelCase in Golang.