Hi All:
Dear skywalking submitter,I am from Baidu Aifanfan,.We are currently selecting
the tracing system.There are currently 2 alternatives
1. Skywalking
2. Baidu Internal System in feng chao
Since the calculation of skywalking relies only on OAP clusters, reducing the
cost of deployment and operation and maintenance, currently it is more inclined
to choose skywalking
As the current system sla calculation is relatively special, the specific logic
is as follows:
One call across 3 systems.The call is c-> b-> a. If B is exception, A is
normal, C will also be recorded as an exception
I want to ask All, service, entrypoint dimensions, what is the logic of sla? At
present our department will want to It is used in the test environment on k8s,
but there is a problem in the calculation logic of sla, because the relevant
information is relatively small and cannot be determined at present,
The currently understood skywalking process:
1. java agent dot, generate span
2. Instance-level spans are aggregated into segments and issued
3. OAP parsing segments and local files
4. Stream processing
Points in doubt (none found in the code):
1.The segment index in the es data has an isError field. Is this part of the
isError an OR relationship? If there is an error in a segment in a segment, the
overall segment is judged for error
2.How does the isError of the spans in the segment converge to statuses such as
ALL, SERVICE, etc.
3. If the access party's RBI interface throws a service exception, is there an
ignored interface in skywalking?
I hope to get help from you, thankyou
Evan.liu
Evan.liu
