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
Is your feature request related to a problem? Please describe.
The current AWS Firehose receiver only supports cwlogs record type which is ingesting JSON format logs from CloudWatch. We should also add support for logs sent from services directly to Firehose. For example VPC flow logs can be sent directly to Firehose and our awsfirehosereceiver should be able to process these requests as well.
Describe the solution you'd like
We can introduce a new record_type: firehoselogs to separate the log type from record_type: cwlogs. Since there can be logs from different AWS services send directly to Firehose, the format will be different too. This record_type: firehoselogs will process the request, store the whole record data into message field, store the timestamp and firehose ARN.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
receiver/awsfirehose
Is your feature request related to a problem? Please describe.
The current AWS Firehose receiver only supports
cwlogs
record type which is ingesting JSON format logs from CloudWatch. We should also add support for logs sent from services directly to Firehose. For example VPC flow logs can be sent directly to Firehose and ourawsfirehosereceiver
should be able to process these requests as well.Describe the solution you'd like
We can introduce a new
record_type: firehoselogs
to separate the log type fromrecord_type: cwlogs
. Since there can be logs from different AWS services send directly to Firehose, the format will be different too. Thisrecord_type: firehoselogs
will process the request, store the whole record data into message field, store the timestamp and firehose ARN.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: