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

[source-opsgenie] Incremental approach not working for Alerts #39545

Open
1 task done
anamargaridarl opened this issue Jun 18, 2024 · 3 comments
Open
1 task done

[source-opsgenie] Incremental approach not working for Alerts #39545

anamargaridarl opened this issue Jun 18, 2024 · 3 comments

Comments

@anamargaridarl
Copy link
Contributor

Connector Name

source-opsgenie

Connector Version

0.3.6

What step the error happened?

During the sync

Relevant information

The incremental sync for Opsgenie alerts is done using the query parameter: {query: updatedAt>=last updatedAt}. However, the low code connector does not specify this. Furthermore, I'm unsure if it is currently possible to define the "updatedAt>=" expression for a query parameter using the low-code approach.

Relevant log output

No response

Contribute

  • Yes, I want to contribute
@marcosmarxm
Copy link
Member

marcosmarxm commented Jun 18, 2024

Not 100% certain about it but it is probably possible to update the requester to make something:

query: "{query: updatedAt>= {{ stream_state.get('updatedAt') }} }" if stream_state.get('updatedAt') else ""

@marcosmarxm
Copy link
Member

The auth0 has a similar logic

q: "updated_at:{{ '{' }}{{stream_interval.start_time ~ ' TO ' ~ stream_interval.end_time ~ ']' if stream_interval.start_time else config['start_date'] ~ ' TO *]'}}"

@anamargaridarl let me know if you want to work on this issue I can help testing and validate the change.

@anamargaridarl
Copy link
Contributor Author

I managed to fix the issue! However, I recreated the connector alert stream on a more updated version of the yaml which does not entirely match this one - using the low code in Airbyte version 0.57.1

To resolve this, should I update the YAML connector to a more recent version and add the necessary changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants