-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Integrate source performance harness with datadog #31410
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
@@ -180,6 +180,7 @@ jobs: | |||
export STREAM_NUMBER=$STREAM_NUMBER | |||
export SYNC_MODE=$SYNC_MODE | |||
export HARNESS=$HARNESS_TYPE | |||
export DD_API_KEY=${{ secrets.DD_API_KEY }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can set this env var in the env:
section of this step
@@ -180,6 +181,7 @@ jobs: | |||
export STREAM_NUMBER=$STREAM_NUMBER | |||
export SYNC_MODE=$SYNC_MODE | |||
export HARNESS=$HARNESS_TYPE | |||
export DD_API_KEY=$DD_API_KEY |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I'm missing something here, but why do we need to export like this when the env var is already set?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m following the comment on line 178 - seems we need to export those to be accessible to envsubst- though I haven’t tested if that comment is true in this case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you are right - that comment wasn't true. Fixed and cleaned it up.
I tested it on the wrong commit... rerunning the action
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and it still works! https://github.com/airbytehq/airbyte/actions/runs/6540161486/job/17759616382 so you are right, we don't need to re-export stuff that has already been set in env.
new MetricResource().name("github").type("runner"), | ||
new MetricResource().name(imageName).type("image"), | ||
new MetricResource().name(dataset).type("dataset")); | ||
MetricPayload body = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
amazing!
Co-authored-by: xiaohansong <[email protected]>
What
#31363
Integrate performance harness with datadog. This will send out a metric report after the run to datadog and datadog could collect them as a metric. Example:
https://app.datadoghq.com/metric/explorer?start=1697235297143&end=1697238897143&paused=false#N4Ig7glgJg5gpgFxALlAGwIYE8D2BXJVEADxQEYAaELcqyKBAC1pEbghkcLIF8qo4AMwgA7CAgg4RKUAiwAHOChASAtnADOcAE4RNIKtrgBHPJoQaUAbVBGN8qVoD6gnNtUZCKiOq279VKY6epbINiAiGOrKQdpYZAYgUJ4YThr42gDGSsgg6gi6mZaBZnHKGABuMMiZUiJwmQhuGgB0itqu7hgi2S1M2vic8gTAAFQ8IDwAulSdqniYoeFzCxgxpfGTMyAacmg5oPIY+wgIOUk4ME6ZixoQmYloonBOcorK6U9Qj89O9EzKERuDxoSb8CD2TBYV4Kc5PepbHh8HbyJ4IADCUmEMBQIgWaB4QA
How
Use Datadog Client to send a HTTP request with corresponding DD_API_KEY, which is stored as a secret in airbyte. I asked @git-phu to enable that secret for this repo so we would be able to reuse that.
Change k8s env and related command in GHA workflow so we can pass along these env variables.
Recommended reading order
x.java
y.python
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user?
For connector PRs, use this section to explain which type of semantic versioning bump occurs as a result of the changes. Refer to our Semantic Versioning for Connectors guidelines for more information. Breaking changes to connectors must be documented by an Airbyte engineer (PR author, or reviewer for community PRs) by using the Breaking Change Release Playbook.
If there are breaking changes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
Pre-merge Actions
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.0.0.1
Dockerfile
has version0.0.1
README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog with an entry for the initial version. See changelog exampledocs/integrations/README.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
Updating a connector
Community member or Airbyter
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
Connector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:generateScaffolds
then checking in your changesUpdating the Python CDK
Airbyter
Before merging:
--use-local-cdk --name=source-<connector>
as optionsairbyte-ci connectors --use-local-cdk --name=source-<connector> test
After merging: