wu-sheng opened a new issue, #9745:
URL: https://github.com/apache/skywalking/issues/9745

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no 
similar feature requirement.
   
   
   ### Description
   
   This is a feature that was asked repeatedly, but we hold it for a long time, 
with concerns about the performance of upstream(exporting target).
   Now, the whole OAP backend is stable from an architectural perspective. 
   I would like to begin this feature discussion and talk about possible 
solutions.
   
   ### Use case
   
   ## Exporting SkyWalking's traces and logs to the 3rd party
   
   We had the metrics exporter, 
https://skywalking.apache.org/docs/main/next/en/setup/backend/metrics-exporter/,
 for years.
   Users could use this easy to build forward if they need most of the metrics, 
but on-demand query through GraphQL doesn't fit their requirements.
   
   Same for traces and logs. users may have some platform, which wants to 
analyze logs and traces for business performance analysis, or AIOps, like 
@Superskyyy 's new project 
(https://github.com/SkyAPM/aiops-engine-for-skywalking)
   
   ## Challenges 
   The major challenges about these exporting, are building 
   1. A scalable channel to export data.
   2. A good limiter and breaker to make sure low perf upstream would not break 
or slow down the OAP server.
   3. Measure the exporting performance and speed in the self-observability
   
   ## Milestone
   I am not sure whether we should set milestones in 9.3.0. I would discuss it 
with @wankai123 to see.
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to