please provide the Log Analysis Language text regexp debugger

[zhouhuicong]

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Feature or performance improvement

---

Requirement or improvement

• Please describe your requirements or improvement suggestions.
  when i use the Log Analysis Language to parser the unstructured logs. i have to configure the text regexp . but I need to change the regular expression many times and then restart the oapsever. It is inefficient to load tests for many times . the Skywalking can it be provided the regular expression parser debugger like the kibana grok debugger

[wu-sheng]

I am not sure what Kibana does, but it makes sense to have a tool to debug, and make the behavior predictable.
But we need to see who wants to do this.

[kezhenxu94]

This is Java / Groovy regex and there are a bunch of tester out there for test and debugging, https://www.google.com.hk/search?q=java+regex+tester&safe=strict&client=safari&hl=en-cn&sxsrf=ALeKk01O7h-PjV9rN3nj76LKhdvSIauC6A%3A1624617447086&ei=57HVYOnCBIKMr7wP77uTyA4&oq=java+regex+tester&gs_lcp=ChNtb2JpbGUtZ3dzLXdpei1zZXJwEAMyBQgAEMQCMgIIADICCAAyAggAMgYIABAWEB4yBggAEBYQHjIGCAAQFhAeMgYIABAWEB46BAgAEEdQ8RVYrRdgyRhoAHACeACAAZwBiAGcAZIBAzAuMZgBAKABAcgBCMABAQ&sclient=mobile-gws-wiz-serp

[wu-sheng]

This is Java / Groovy regex and there are a bunch of tester out there for test and debugging, https://www.google.com.hk/search?q=java+regex+tester&safe=strict&client=safari&hl=en-cn&sxsrf=ALeKk01O7h-PjV9rN3nj76LKhdvSIauC6A%3A1624617447086&ei=57HVYOnCBIKMr7wP77uTyA4&oq=java+regex+tester&gs_lcp=ChNtb2JpbGUtZ3dzLXdpei1zZXJwEAMyBQgAEMQCMgIIADICCAAyAggAMgYIABAWEB4yBggAEBYQHjIGCAAQFhAeMgYIABAWEB46BAgAEEdQ8RVYrRdgyRhoAHACeACAAZwBiAGcAZIBAzAuMZgBAKABAcgBCMABAQ&sclient=mobile-gws-wiz-serp

@kezhenxu94 I haven't checked, I think he means a simulator, could get input and output, without running the OAP.

[wu-sheng]

@kezhenxu94 @Fine0830 Once #7180 has a solid result, we should have a discussion about how to do this. We may need a debug UI to interact with the backend. I don't have a design yet, let's discuss when the LAL engine is improved.

[wu-sheng]

@Fine0830 Is RocketBot UI suitable to pop up(or open a new window) for debugger tools? It should have 2 inputs and 1 output, which are listed like project kanban. And we need to add one more for MAL, @wankai123 I think you will like this idea.

Inputs have

1. Orginal text of log, @kezhenxu94 Should we support multiple logs?
2. LAL configuration

Output should be

1. The results of every execution stage
2. Final log in the database if it will be persistent.
3. Metrics output
4. @kezhenxu94 You could add one.

This should not be hard to implement in SkyWalking backend, we just need a debuger-tool GraphQL.

[kezhenxu94]

1. Orginal text of log, @kezhenxu94 Should we support multiple logs?

Supporting 1 or 1+ logs seems no difference from frontend or backend side, let's support this.

[wu-sheng]

1. Orginal text of log, @kezhenxu94 Should we support multiple logs?

Supporting 1 or 1+ logs seems no difference from frontend or backend side, let's support this.

The key is how to separate records because one log record could include multiple lines.

[kezhenxu94]

Well, I finally realize that this should be done only after we address the security of LAL or #6897, otherwise this would be a security problem

[wu-sheng]

#6897 would be withdraw, because I have done the research, it is too complex, and too dangerous to cause OOM and GC storm in the load traffic load.