You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@proddata: Thanks for reporting this, and for your suggestions. I agree with your proposal.
@surister: I also try to approach improvements to this program each time like this again, but then, reality strikes: The program currently doesn't do much with environment variables, opposed to what one would expect for a cloud-native program. The configuration is mostly handled on behalf of configuration file settings.
Because it is possible to configure multiple CrateDB endpoints there, i.e. the program implements a flavor of multi-tenancy on that dimension, it is mostly not applicable to use settings that would apply globally.
Originated from community question: https://community.cratedb.com/t/prometheus-failed-to-write-data-into-cratedb-after-encountering-error-a-document-with-the-same-primary-key-exists-already/1724
We probably could add the option to use upserts or make it the even default approach.
Since the table definition is using primary keys we should change the
insert statement
cratedb-prometheus-adapter/crate.go
Line 16 in dc5c40f
to either ignore conflicts:
or handle upserts:
Potentially this could be configurable (to do either or).
The text was updated successfully, but these errors were encountered: