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
add apache logs s3 flint based integration assets into the existing apache-logs integration
What is the integration source protocol ? Apache Logs format
Similar to the existing apache protocol, this integration would address the logs arriving from an S3 based table.
Which agents would you use to ship this data ?
The integration expects the data to reside within an S3 bucket and allow usage of the Flint spark plugin
Would you be using an ingestion pipeline ? The integration expects the data to reside on S3 bucket
Which Dashboards would you be using ? Similar dashboards as the existing one in the index only based cloudfront integration
Do you have any additional context?
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
YANG-DB
No branches or pull requests
add apache logs s3 flint based integration assets into the existing apache-logs integration
What is the integration source protocol ?
Apache Logs format
Similar to the existing apache protocol, this integration would address the logs arriving from an S3 based table.
Which agents would you use to ship this data ?
The integration expects the data to reside within an S3 bucket and allow usage of the Flint spark plugin
Would you be using an ingestion pipeline ?
The integration expects the data to reside on S3 bucket
Which Dashboards would you be using ?
Similar dashboards as the existing one in the index only based cloudfront integration
Do you have any additional context?
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: