feat: more confs for prometheus pushing #8
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ion-on-macos chore: fix RUNNER_ROOT_DIR detection on MacOS
…ion-id-should-return-204 refactor: return `204` instead of `200` for `PUT /authenticator/:id`
prior to this change, the message is dispatched to a shared subscriber even after unsubscribed
* avoid calling ets:select twice for sticky strategy * when the calling process is terminating, no loop-back dispatch
'hash' strategy has been removed from config schema hence no need to keep the compatibility code
https://emqx.atlassian.net/browse/EMQX-8547 If a Kafka Producer bridge is given bad configuration (e.g.: bad authn credentials), the Wolff client process is started successfully, as it does not attempt to connect, but when the producer process is attempted to be started, it fails (only then the client tries to connect to Kafka). At this point, an error was thrown, but the supervised client process remained running. If the configuration was later fixed and the bridge updated, which prompted its removal and recreation, the Wolff client would report to be "already started", so it would never pick up the new (fixed) configuration, and the producers would perpetually fail to start until the node would be restarted. We simply ensure the client is stopped before throwing the error, unrolling the start-up procedure.
otherwise when updating from dashboard, there is no way to set 'false' for 'retain' because it's a checkbox, it's either 'true' or 'undefined'
fix(influxdb): check if fields are empty before sending
worker pool is a buffer pool the description hinted connection pool which is wrong.
chore: Add more PR templates
The jq function in the rule engine uses the jq NIF implementation by default so there is often no need to start any jq port programs. Before this commit jq port programs were started anyway. This is fixed by not starting the jq application (the jq application is started automatically when the jq port implementation is activated).
…t_port_programs_when_they_are_not_needed fix: do not start jq port programs when they are not needed
1219 fix shared sub sticky
1219 fix mqtt bridge config
…n-tty chore: fix logging in bin/emqx on non-tty
fix(limiter): change limiter `cache` to `buffer`
An infinite loop was triggered in the mysql connector when a query used a prepared statement key that was not among the defined prepared statements on start. We now check that the key is defined among the prepared statements before recursing. It seems that this bug was never triggered in any production code flow and simply found while writing tests. An error return spell fix is also included as well as a FIXME comment regarding running mysql:prepare and not distinguishing between transient failures and syntax errors. Syntax errors should not be retried.
feat(emqx_metrics): Sliding window samples
…lient.connected-hook fix: bulk subscribe topics failed in the client.connected hook
…f-webhook-body fix: remove the default value of webhook body field
chore(readme): remove legacy Travis mentions
Co-authored-by: ieQu1 <99872536+ieQu1@users.noreply.github.com>
…-coverter fix: upgrade bridge config converter
…quest-body fix(mgmt_api): remove possibility to set clientid in /publish API
feat: introduce API keys bootstrap_file config
fix: bad auto_subscribe api schema
chore: bump up applications to release v5.0.14
…after-recreate-if-disabled fix(emqx_resource_manager): do not start when disabled
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
wirte_syntaxexamplewrite_syntaxusing raw typestring()on_batch_query/3callbackinfluxdb-client-erlvsnasync/batch_asyncqueryon_batch_queryon emqx_connector_mysqlpool_sizefor influxdb clientpasswordfor dashboardauto_retryindisconnectedstateinfluxdb-client-erlversiontelemetryversiontelemetryapp beforeemqxexpto be optional claimmax_topic_levelsto 128binary_to_atomlist_to_atom/positionto move authenticatorlimiterback to the configs API204instead of200forPUT /authenticator/:id204instead of200forPUT /authenticator/:id"/mqtt/sys_topicsto generic/configs/sys_topicson_exitcallbackslocal_topicconfigemqx_ee_bridge_gcp_pubsub_resourcetoemqx_ee_connector_gcp_pubsub/users/{name}/change_pwdmessage.droppedhook, incmessages.droppedmetricsredbugto 2.0.8emqx/rebar33.19.0-emqx-1redbugto 2.0.8 in mix.exs1.1.0-emqx-2format_status/1callbackzip,gzip,zip_compressfuncs in rule-sql204instead of200forPUT /authenticator/:idcachetobufferbannedis large enoughlists:flatten/1dropped.queue_fullevent from wolffredactedtest case for bridges apitypeandnamefields to theget/postAPI docsreplayqignoreresults (request failures)Fixes
PR Checklist
Please convert it to a draft if any of the following conditions are not met. Reviewers may skip over until all the items are checked:
changes/<version>/(feat|fix)-<PR-id>.en.mdand.zh.mdfiles