We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Similar to qryn for simple log ingestion from something like cloudflare worker logpush for the datadog api. See https://docs.datadoghq.com/api/latest/logs/ and https://developers.cloudflare.com/logs/get-started/enable-destinations/datadog/
This is how you change it: https://blog.qryn.dev/cloudflare-log-push-with-qryncloud
If qryn ends up using IceDB then this wont be needed
The text was updated successfully, but these errors were encountered:
Gotta figure out how to get severity and such... the docs aren't great
Sorry, something went wrong.
See https://docs.datadoghq.com/logs/log_configuration/attributes_naming_convention/#reserved-attributes
We get status to determine the level, see https://docs.datadoghq.com/logs/log_configuration/processors/?tab=ui#log-status-remapper for the levels (and remapping needed)
status
For sending multiple you get an array of JSON to the endpoint
No branches or pull requests
Similar to qryn for simple log ingestion from something like cloudflare worker logpush for the datadog api. See https://docs.datadoghq.com/api/latest/logs/ and https://developers.cloudflare.com/logs/get-started/enable-destinations/datadog/
This is how you change it: https://blog.qryn.dev/cloudflare-log-push-with-qryncloud
If qryn ends up using IceDB then this wont be needed
The text was updated successfully, but these errors were encountered: