Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build profiler sink #2875

Closed
pmbrull opened this issue Feb 20, 2022 · 2 comments · Fixed by #3011
Closed

Build profiler sink #2875

pmbrull opened this issue Feb 20, 2022 · 2 comments · Fixed by #3011
Assignees

Comments

@pmbrull
Copy link
Collaborator

pmbrull commented Feb 20, 2022

Feature
Based on #1311

Describe the task
Update the OM Python client and build the sink to send the profiler and test results to the OM API.

@pmbrull pmbrull self-assigned this Feb 20, 2022
@pmbrull pmbrull added this to To do in Release 0.9.0 via automation Feb 20, 2022
@mithmatt
Copy link
Collaborator

I hope the structure of the sink is in such a way that we can extend the implementation in the future to support an external sink such as CloudWatch of OpenTSDB, and make the metrics queryable through Grafana (iframe view embedded in OpenMetadata)

https://grafana.com/docs/grafana/latest/datasources/opentsdb/

@pmbrull pmbrull added this to the Milestone 4 - 0.9.0 Release milestone Feb 21, 2022
@pmbrull
Copy link
Collaborator Author

pmbrull commented Feb 21, 2022

The goal of the sink is to pick up the data structures created during the profiling and push them somewhere. We will start by preparing the OM sink, which will make some API calls to OM itself. We can create other sinks as needed, and they get configured in the JSON, e.g.,

"sink": {"type": "metadata-rest", "config": {}},

Release 0.9.0 automation moved this from To do to Done Mar 2, 2022
pmbrull added a commit that referenced this issue Mar 2, 2022
Fix #2875 - Profiler API Sink
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants