[CLI] Incorrect instance and enpoint level query implementation

[wu-sheng]

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Question or discussion
• Bug
• Requirement
• Feature or performance improvement

---

Bug

This bug is detected, which starts with the discussion here, apache/skywalking-swck#12 (comment). The current implementation of linear(maybe more) query, doesn't adopt/use the correct parameters.

We should provide separate parameters for instance and endpoint names, with isNormal flag, which could be used in conjecture services.

@fgksgf Let's fix this and call for 0.5.0 release. Note, #4466 should follow this when you implement those queries.

[fgksgf]

@wu-sheng
I added a bool flag named unnormal, it's not required. Because the default value of bool is true.
If we create a isNormal flag, we probably have to add this flag most of the time.
What do you think ？

[wu-sheng]

I added a bool flag named unnormal, it's not required. Because the default value of bool is true.
If we create a isNormal flag, we probably have to add this flag most of the time.
What do you think ？

I think this is only coding style. You could give the parameter true if no input parameter. Right? unnormal is anti-protocol, which should not be recommended.

[kezhenxu94]

I added a bool flag named unnormal, it's not required. Because the default value of bool is true.
If we create a isNormal flag, we probably have to add this flag most of the time.
What do you think ？

I think this is only coding style. You could give the parameter true if no input parameter. Right? unnormal is anti-protocol, which should not be recommended.

+1, @fgksgf make isNormal type of string, and give it default value "true", and validate that it should be either "true" or "false"

[fgksgf]

Make sense to me