[feature] Support for Periodic Threshold preview.

[Duansg]

What's changed?

Support for Periodic Threshold preview.

For details:

1. Added Threshold -> Periodic Threshold preview, exception content support for internationalization
2. Add anltr4 Look Ahead method to determine if parsing is finished.
3. Add new test cases/fix test cases and go through the history of test cases successfully.

Checklist

• I have read the Contributing Guide
• I have written the necessary doc or comment.
• I have added the necessary unit tests and all cases have passed.

Add or update API

• I have added the necessary e2e tests and all cases have passed.

1、andOp

2、compareOp

3、orOp

[MasamiYui]

looks great!

[Duansg]

looks great!

hh, review it for me if you have time. 😉

[MasamiYui]

@tomsun28 @bigcyy What are your thoughts on this preview feature? Personally, From a UI perspective, as an common user, I might not fully grasp the meaning conveyed here, such as inner elements like __value__

[Duansg]

@tomsun28 @bigcyy What are your thoughts on this preview feature? Personally, From a UI perspective, as an common user, I might not fully grasp the meaning conveyed here, such as inner elements like __value__

I don't think there is anything to worry about for the following reasons.

1. If __value__ doesn't make sense, we can change it to value.
2. If value is not understandable, then I would suggest the user to read the official documentation.

[bigcyy]

Looks good, but would it be better to display it as shown in the picture? My reasons are as follows:
Due to the 'and' set operations, if a structured table is used, the table header might be very long. Perhaps JSON would be more suitable.

[Duansg]

Looks good, but would it be better to display it as shown in the picture? My reasons are as follows: Due to the 'and' set operations, if a structured table is used, the table header might be very long. Perhaps JSON would be more suitable.

That's good advice, I'll have time to deal with it tomorrow.

[MasamiYui]

@Duansg How about adding a marker to the corresponding row if it can trigger an alert?

[Duansg]

How about adding a marker to the corresponding row if it can trigger an alert?

@MasamiYui Sorry, I didn't quite get your point, could you expand on it. :)

[MasamiYui]

Like this:

__VALUE__ == null -> No

__VALUE__ != null -> YES

[Duansg]

Like this:

`__VALUE__ == null` -> No

__VALUE__ != null -> YES

@MasamiYui Emmm, this is indeed in line with the current design, but I think we should not add this description for the time being, for the following reasons

1. After our last discussion, I still firmly believe that we must ensure the integrity and scalability of the parser and ensure consistency with the promql semantics, that is, abandon the judgment of value == null and replace it with metrics == null. Otherwise, adding hertzbeat's unique judgment to the parser will make the parser very difficult to maintain and the complexity of achieving semantic correctness.
2. If the above functional effects are achieved, the result of the preview function will be what you see is what you get, just like the search in the prometheus ui, so there is no need for a special mark to tell the user whether this item is hit, otherwise if a large amount of missed data is a terrible rendering function point.

Therefore, I think that it is enough to achieve the effect of basic preview at present. After we complete the relevant logic of the parser in the future, we will come back to see if there are other optimization points for this content. What do you think?

[Duansg]

Looks good, but would it be better to display it as shown in the picture? My reasons are as follows: Due to the 'and' set operations, if a structured table is used, the table header might be very long. Perhaps JSON would be more suitable.

@MasamiYui @bigcyy

Sorry friends, I'm busy with work recently. I will continue to improve this PR tomorrow. If you are all free at that time, please review it for me. Thanks. 😅

[bigcyy]

1. I still firmly believe that we must ensure the integrity and scalability of the parser and ensure consistency with the promql semantics

I agree, see #3496 .

[Duansg]

1、orOp

2、andOp

3、comOp

3、error display

5、unlessOp

4、metrics data is empty

[MasamiYui]

LGTM.