refactor: reworked aws_vpc_flow_log table as a custom table allowing for formats to be used #137

graza-io · 2025-04-02T19:06:42Z

No description provided.

tables/vpc_flow_log/vpc_flow_log_extractor.go

graza-io · 2025-04-09T10:16:30Z

tables/vpc_flow_log/vpc_flow_log_extractor.go

@@ -32,26 +40,21 @@ func (c *VPCFlowLogExtractor) Extract(_ context.Context, a any) ([]any, error) {
 		return nil, fmt.Errorf("expected byte[], got %T", a)
 	}

-	mappedData, err := ConvertToMapSlice(string(jsonBytes))
+	mappedData, err := ConvertToMapSlice(c, string(jsonBytes))
 	if err != nil {
 		return nil, fmt.Errorf("error in mapping the results in the form of []map[string]string")
 	}

 	var res = make([]any, len(mappedData))
 	for i, record := range mappedData {


Is this iteration required, previously the mappedData was iterated as a mapping was done and errors may have been reported out, I think we can just return mappedData here?

As we are not using any mapper here, the mapped data should be of type (*types.DynamicRow) I have made the changes to return the []*types.DynamicRow{}. Otherwisewe will get the error like required *types.DynamicRow got map[string]string

tables/vpc_flow_log/vpc_flow_log_extractor.go

tables/vpc_flow_log/vpc_flow_log_format.go

graza-io · 2025-04-09T10:31:18Z

tables/vpc_flow_log/vpc_flow_log_mapper.go

I had removed the need for this mapper, I can see you've added it back purely for S3 source, any particular reason we can't just use the default approach of the regex mapper?

Ah, my bad — I missed removing it in the initial commit. We no longer need this mapper since the Extractor now handles everything. I haven’t tried using the Gonx or Regex mapper in this case. My main goal was to preserve the previous table functionality, so we used an Extractor, which parses the entire object content at once and returns the rows directly.

@ParthaI What's the effect on removing vs. keeping this mapper for current users of the table who pull flow logs from an S3 bucket today for default and custom logs?

@cbruno10, in general, the mapper is designed to work on a per-row basis, while the extractor is intended for handling bulk or batch row data. In our earlier implementation, we used an extractor to download the full object content and map the column values based on the header line (i.e., the first line of the log data). To keep the behavior consistent with that approach, I’ve continued using an extractor here.

Additionally, we don't require a custom mapper in this case because the default SDK-provided mapper for custom tables already handles the mapping logic effectively.

Here are a few considerations when comparing extractor vs. mapper for this use case:

With a mapper, the user must explicitly provide a format layout. However, with an extractor, we have the flexibility to infer the header (i.e., the format layout) from the first line of the log file—whether or not the user specifies a format block.

In some cases, such as when logs are exported from CloudWatch to an S3 bucket, the log files don’t include a header line. The current extractor-based design handles this scenario well: users can still specify a format block to define the layout manually. The default mapper would work the same way in this case if it were used, but the extractor approach makes the solution more adaptive and user-friendly.

graza-io · 2025-04-09T10:32:45Z

tables/vpc_flow_log/vpc_flow_log_table.go

+const VpcFlowLogTableSkippedData = "SKIPDATA"
+const VpcFlowLogTableNoData = "NODATA"


These are valid log entries, I don't think we should forcefully remove them in code but rather make a suggestion that users can filter them out using a filter?

Hmm, good point, @cbruno10 - could we consider keeping the SKIPDATA/NODATA values as-is instead of skipping them? That said, this behavior would then apply to all columns. We still need to retain the check for tp_timestamp and tp_data, since those are required columns in the Tailpipe DB.

Yes, I think I'd keep them, as users can filter out these values when collecting or in their queries like @graza-io mentioned. May be worth adding an example in the Example Configurations section showing how to avoid collecting these with filter.

tables/vpc_flow_log/vpc_flow_log_table.go

Copilot

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

Copilot · 2025-04-09T12:11:43Z

tables/vpc_flow_log/vpc_flow_log_table.go

+
+	row.OutputColumns[constants.TpTable] = VpcFlowLogTableIdentifier
+
+	if startTime, ok := row.GetSourceValue("start_time"); ok && (startTime != VpcFlowLogTableSkippedData || startTime != VpcFlowLogTableNoData || startTime != VpcFlowLogTableNilValue) {


The condition uses logical OR (||) when checking against invalid values, which will always evaluate to true. Replace the OR operators with AND (&&) to correctly validate that startTime is not equal to any of the invalid constants.

Suggested change

if startTime, ok := row.GetSourceValue("start_time"); ok && (startTime != VpcFlowLogTableSkippedData || startTime != VpcFlowLogTableNoData || startTime != VpcFlowLogTableNilValue) {

if startTime, ok := row.GetSourceValue("start_time"); ok && (startTime != VpcFlowLogTableSkippedData && startTime != VpcFlowLogTableNoData && startTime != VpcFlowLogTableNilValue) {

Copilot · 2025-04-09T12:11:43Z

tables/vpc_flow_log/vpc_flow_log_mapper.go

-func (m *VPCFlowLogMapper) Identifier() string {
-	return "vpc_flow_log_mapper"
+func (c *VPCFlowLogMapper) Identifier() string {
+	return "aws_waf_traffic_log_mapper"


The mapper Identifier returns 'aws_waf_traffic_log_mapper', which appears inconsistent with the VPC Flow Log context. It should likely return an identifier that reflects VPC Flow Log mapping, for example 'vpc_flow_log_mapper'.

Suggested change

return "aws_waf_traffic_log_mapper"

return "vpc_flow_log_mapper"

cbruno10 · 2025-04-09T12:14:10Z

tables/vpc_flow_log/vpc_flow_log_table.go

+func (c *VpcFlowLogTable) GetTableDefinition() *schema.TableSchema {
+	return &schema.TableSchema{
+		Name: VpcFlowLogTableIdentifier,
+		Columns: []*schema.ColumnSchema{


@ParthaI Are there any changes from the previous version of the table, or are they the same?

They are the same, @cbruno10- we've just split the VpcFlowLog struct into a custom schema.

Copilot

Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.

Copilot · 2025-04-17T03:32:17Z

aws/plugin.go

+	// register formats
+	table.RegisterFormatPresets(vpc_flow_log.VPCFlowLogTableFormatPresets...)
+	table.RegisterFormat[*vpc_flow_log.VPCFlowLogTableFormat]()
+	row_source.RegisterRowSource[*cloudwatch_log_group.AwsCloudWatchLogGroupSource]()


The AwsCloudWatchLogGroupSource row source is registered twice, which may lead to duplicate registrations. Please remove one of the duplicate calls to avoid potential conflicts.

Suggested change

row_source.RegisterRowSource[*cloudwatch_log_group.AwsCloudWatchLogGroupSource]()

cbruno10

@ParthaI Please see comments, thanks!

cbruno10 · 2025-04-17T03:55:19Z

docs/tables/aws_vpc_flow_log/index.md

@@ -7,7 +7,18 @@ description: "AWS VPC flow logs capture information about IP traffic going to an

 The `aws_vpc_flow_log` table allows you to query data from [AWS VPC Flow Logs](https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html). This table provides detailed insights into network traffic within your VPC, including source and destination IP addresses, ports, protocols, and more.

-**Note**: For timestamp information, the `start` field will be used first, with the `end` field as a fallback. If neither field is available, then that log line will not be collected and Tailpipe will return an error.
+**Note**:
+- Using `aws_s3_bucket` source:


I think most of these notes could be explained through examples in the Example Configurations section and aren't required here, it's hard to understand without seeing the configs anyway

Removed the notes that are specific to example configuration.

cbruno10 · 2025-04-17T03:55:42Z

docs/tables/aws_vpc_flow_log/index.md

-    paths       = ["/Users/myuser/vpc_flow_logs"]
-    file_layout = `%{DATA}.json.gz`
+partition "aws_vpc_flow_log" "my_logs_instance" {
+  filter = "action <> 'REJECT'"


Do we use <> or != more commonly (I think the latter)?

Yes, != is the more commonly used operator. I've updated the query to use != instead.

cbruno10 · 2025-04-17T03:56:28Z

docs/tables/aws_vpc_flow_log/index.md

+}
+```
+
+### Collect logs from a CloudWatch log group


Please move this example up and review the order of other examples, we should make examples flow simple -> complex/edge

Reordered the example configurations from simple to complex/edge cases.

@cbruno10, would it make sense to reorder the example configurations from simple to complex/edge cases and group them by source?

cbruno10 · 2025-04-17T03:57:08Z

docs/tables/aws_vpc_flow_log/index.md

+}
+```
+
+### Collect VPC flow logs from a CloudWatch log group with custom log format


Suggested change

### Collect VPC flow logs from a CloudWatch log group with custom log format

### Collect logs from a CloudWatch log group with custom log format

I don't think we need to repeat VPC flow logs each time, we're already in the VPC flow log doc, so just logs is OK I think (I believe this is what we do in other docs too).

cbruno10 · 2025-04-17T03:57:53Z

docs/tables/aws_vpc_flow_log/index.md

+}
+```
+
+### Collect VPC flow logs from a CloudWatch log group for all ENIs with wildcard stream names


This title feels long, is there a shorter/more general title we can use to summarize what this example highlights?

Updated the title to make it shorter.

cbruno10 · 2025-04-17T03:58:57Z

sources/cloudwatch_log_group/cloudwatch_log_group_source.go

@@ -77,7 +77,7 @@ func (s *AwsCloudWatchLogGroupSource) Identifier() string {

 func matchesAnyPattern(target string, patterns []string) bool {
 	for _, pattern := range patterns {
-		match, err := filepath.Match(pattern, target)
+		match, err := path.Match(pattern, target)


Given that we decided to not escape chars, can you please add 1-2 examples in the CW log source table doc showing how escaping chars works? This can help us determine if we like that design as well.

Added example in CW source doc.

…for formats to be used

…he doc with example config to exclude the NODATA and SKIPDATA for a column

…licable for log-status field

…g the file source implementation to the table map

…s maintain order of precedence for tp_timestamp

…d on the source.

Copilot

Pull Request Overview

This PR refactors the aws_vpc_flow_log table to implement a custom table that supports multiple log formats. Key changes include embedding a custom table implementation in VpcFlowLogTable, refactoring the EnrichRow and source extraction logic to use dynamic rows, and updating format and registration logic accordingly.

Reviewed Changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
tables/vpc_flow_log/vpc_flow_log_table.go	Refactored the table structure, source metadata, and row enrichment logic to use dynamic rows and a custom table implementation.
tables/vpc_flow_log/vpc_flow_log_extractor.go	Updated the extractor logic to work with dynamic rows and handle header validation.
tables/vpc_flow_log/vpc_flow_log_format*.go	Introduced and registered new format definitions and presets.
docs/tables/aws_vpc_flow_log/index.md	Updated documentation to reflect the new processing logic and configuration options.
aws/plugin.go	Adjusted plugin registration for custom table and format registration.

Copilot · 2025-05-27T16:23:11Z

tables/vpc_flow_log/vpc_flow_log_table.go

+	row.OutputColumns[constants.TpIndex] = schema.DefaultIndex



The previous logic for setting TpIndex based on 'interface_id', 'subnet_id', or 'vpc_id' has been replaced with a default value. Confirm that this deviation from the documented precedence is intentional.

Suggested change

row.OutputColumns[constants.TpIndex] = schema.DefaultIndex

if interfaceID, ok := row.GetSourceValue("interface_id"); ok && interfaceID != VpcFlowLogTableNilValue {

row.OutputColumns[constants.TpIndex] = interfaceID

} else if subnetID, ok := row.GetSourceValue("subnet_id"); ok && subnetID != VpcFlowLogTableNilValue {

row.OutputColumns[constants.TpIndex] = subnetID

} else if vpcID, ok := row.GetSourceValue("vpc_id"); ok && vpcID != VpcFlowLogTableNilValue {

row.OutputColumns[constants.TpIndex] = vpcID

} else {

row.OutputColumns[constants.TpIndex] = schema.DefaultIndex

}

Copilot · 2025-05-27T16:23:11Z

docs/tables/aws_vpc_flow_log/index.md

-**Note**: For timestamp information, the `start` field will be used first, with the `end` field as a fallback. If neither field is available, then that log line will not be collected and Tailpipe will return an error.
+**Note**:
+- When determining each log's timestamp, the table uses the `start` field first, with the `end` field as a fallback. If neither field is available, then that log line will not be collected and Tailpipe will return an error.
+- When determining each log's index, the table uses the following order of precedence:


The documentation specifies that the TpIndex should be determined by 'interface_id', 'subnet_id', then 'vpc_id', with a default of 'default'. Update the documentation or adjust the code to ensure consistency between the intended behavior and its documentation.

Copilot

Pull Request Overview

A refactor converts the aws_vpc_flow_log table into a customizable table with support for user-defined formats, dynamic row mapping, and CloudWatch integration.

Switched to CustomTableImpl and DynamicRow for flexible schema and enrichment
Enhanced extractor and mapper to use custom layouts and fallback detection
Updated documentation with new examples for format presets and source configurations

Reviewed Changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
tables/vpc_flow_log/vpc_flow_log_table.go	Converted to CustomTable, dynamic enrichment logic
tables/vpc_flow_log/vpc_flow_log_format.go	Added token-based formatting with regex mapper
tables/vpc_flow_log/vpc_flow_log_format_presets.go	Defined default format preset
tables/vpc_flow_log/vpc_flow_log_extractor.go	Updated extractor to use `DynamicRow` and layout fallback
tables/vpc_flow_log/vpc_flow_log_cloudwatch_mapper.go	Added CloudWatch event mapper wrapping regex mapper
aws/plugin.go	Registered custom table and formats
docs/tables/aws_vpc_flow_log/index.md	Expanded and reorganized usage examples

Comments suppressed due to low confidence (2)

tables/vpc_flow_log/vpc_flow_log_cloudwatch_mapper.go:43

Consider adding unit tests to cover each input type branch and error case in this mapper to ensure robust handling of CloudWatch event formats.

switch v := a.(type) {

tables/vpc_flow_log/vpc_flow_log_extractor.go:71

Add tests for the header-fallback logic (when no header is detected) to verify that the default layout is correctly prepended and logged.

func toMapSlice(c *VPCFlowLogExtractor, data string) ([]map[string]string, error) {

Copilot · 2025-05-30T15:25:47Z

tables/vpc_flow_log/vpc_flow_log_table.go

+	row.OutputColumns[constants.TpIndex] = schema.DefaultIndex



The original logic prioritized interface_id, subnet_id, or vpc_id before defaulting; this overwrite always uses the default index. Reintroduce the precedence checks to preserve correct TpIndex values.

Suggested change

row.OutputColumns[constants.TpIndex] = schema.DefaultIndex

if interfaceID, ok := row.GetSourceValue("interface_id"); ok && interfaceID != VpcFlowLogTableNilValue {

row.OutputColumns[constants.TpIndex] = interfaceID

} else if subnetID, ok := row.GetSourceValue("subnet_id"); ok && subnetID != VpcFlowLogTableNilValue {

row.OutputColumns[constants.TpIndex] = subnetID

} else if vpcID, ok := row.GetSourceValue("vpc_id"); ok && vpcID != VpcFlowLogTableNilValue {

row.OutputColumns[constants.TpIndex] = vpcID

} else {

row.OutputColumns[constants.TpIndex] = schema.DefaultIndex

}

Copilot · 2025-05-30T15:25:48Z

tables/vpc_flow_log/vpc_flow_log_table.go

+		t, err := helpers.ParseTime(endTime)
+		if err != nil {
+			invalidFields = append(invalidFields, "end_time")
+		} else {


Using ParseTime on Unix-seconds strings may misinterpret the format. Consider converting the string to an integer and using time.Unix for accurate epoch parsing.

Suggested change

t, err := helpers.ParseTime(endTime)

if err != nil {

invalidFields = append(invalidFields, "end_time")

} else {

// Convert end_time to an integer and parse it as a Unix timestamp

endTimeInt, err := strconv.ParseInt(endTime, 10, 64)

if err != nil {

invalidFields = append(invalidFields, "end_time")

} else {

t := time.Unix(endTimeInt, 0)

Copilot · 2025-05-30T15:25:48Z

docs/tables/aws_vpc_flow_log/index.md

+
+  source "aws_cloudwatch_log_group"  {
+    connection = connection.aws.default
+    format     = format.aws_vpc_flow_log.log_layout


The example references log_layout but the preset is named log_format. Update to format.aws_vpc_flow_log.log_format to match the defined format label.

Copilot · 2025-05-30T15:25:48Z

docs/tables/aws_vpc_flow_log/index.md

@@ -142,27 +161,56 @@ partition "aws_vpc_flow_log" "my_logs_prefix" {

 ### Collect logs from local files

-You can also collect VPC Flow Logs from local files.
+You can also Collect logs from local files.


[nitpick] Capitalization: change Collect to lowercase (collect) to match sentence style.

Suggested change

You can also Collect logs from local files.

You can also collect logs from local files.

Copilot · 2025-05-30T15:25:48Z

docs/tables/aws_vpc_flow_log/index.md

@@ -126,9 +128,26 @@ partition "aws_vpc_flow_log" "my_logs" {
 }
 ```

+### Collect logs from a CloudWatch log group


[nitpick] This heading appears multiple times with similar content. Consolidate or differentiate sections to avoid duplication and improve clarity.

Copilot

Pull Request Overview

This PR refactors the AWS VPC flow log table implementation by converting it into a custom table that accepts various log formats. Key changes include:

Replacing the original VpcFlowLog structure with a dynamic row model.
Introducing custom format handling and a CloudWatch mapper.
Updating extractor logic to support flexible header handling and custom error messages.

Reviewed Changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
tables/vpc_flow_log/vpc_flow_log_table.go	Refactors table implementation to use a custom table interface and dynamic rows.
tables/vpc_flow_log/vpc_flow_log_format_presets.go	Adds format presets for the table.
tables/vpc_flow_log/vpc_flow_log_format.go	Introduces a new format struct and regex mapping logic.
tables/vpc_flow_log/vpc_flow_log_extractor.go	Adjusts the extractor to support custom headers and dynamic rows.
tables/vpc_flow_log/vpc_flow_log_cloudwatch_mapper.go	Implements a CloudWatch-specific mapper using the new format.
tables/vpc_flow_log/vpc_flow_log.go	Removes the old VpcFlowLog struct to complete the refactor.
docs/tables/aws_vpc_flow_log/index.md	Updates documentation to reflect new format and filtering options.
docs/sources/aws_cloudwatch_log_group.md	Updates examples for CloudWatch log group handling.
aws/plugin.go	Adjusts plugin registration for the custom table and formats.

Copilot · 2025-05-30T18:25:45Z

tables/vpc_flow_log/vpc_flow_log_extractor.go

@@ -61,6 +78,21 @@ func ConvertToMapSlice(data string) ([]map[string]string, error) {
 	// Extract header row as keys
 	keys := strings.Fields(lines[0]) // Splitting header by spaces

+	if !isValidHeader(keys) {


The header validation in isValidHeader strictly checks for known tokens, which may inadvertently flag valid custom headers that include additional fields. Consider allowing extra fields or documenting the required header format more explicitly.

Copilot · 2025-05-30T18:25:45Z

tables/vpc_flow_log/vpc_flow_log_table.go

-	} else {
-		row.TpIndex = "default"
+	if len(invalidFields) > 0 {
+		return nil, error_types.NewRowErrorWithFields([]string{}, invalidFields)


[nitpick] The error creation here only includes invalidFields without indicating which source fields were processed; including the relevant source field names could improve debugging.

graza-io requested a review from ParthaI April 2, 2025 19:06

graza-io commented Apr 9, 2025

View reviewed changes

cbruno10 requested a review from Copilot April 9, 2025 12:10

Copilot AI reviewed Apr 9, 2025

View reviewed changes

cbruno10 reviewed Apr 9, 2025

View reviewed changes

ParthaI changed the base branch from add-doc-for-cw-source-use-format to main April 9, 2025 15:47

cbruno10 requested a review from Copilot April 17, 2025 03:31

Copilot AI reviewed Apr 17, 2025

View reviewed changes

cbruno10 requested changes Apr 17, 2025

View reviewed changes

ParthaI force-pushed the vpc-flow-log-custom-table branch from 68da62e to cdcfed6 Compare May 22, 2025 07:24

ParthaI and others added 20 commits May 27, 2025 20:53

Added doc for the cloudwatch source

c75cc75

Updated the cloudwatch Go package name to cloudwatch_log_group

7fc3bd0

Update

e3081ed

refactor: reworked aws_vpc_flow_log table as a custom table allowing …

9bcc771

…for formats to be used

fix

7fdab04

Update the table to use the custom extractor and mapper

339e113

Made the changes based on the review comments

c7c9bbf

Used the column name export_timestamp instead of exported-at

163d994

Removed the duplicate files

f205bf7

Reverted the changes for extra spaces

0d83648

Updated the doc for the table aws_vpc_flow_log

8791bae

Updated the layout for the formats

d8a116a

Fixed the lint failure error

abd2bf7

Removed the unnecessary check for empty log stream name

3cfb087

Updated the table to keep the rows for NODATA and SKIPDATA, updated t…

0361f5b

…he doc with example config to exclude the NODATA and SKIPDATA for a column

Added notes on the source usage in the table doc

e0b1624

Removed the NODATA or SKIPDATA check for all fields as it is only app…

ddda5b9

…licable for log-status field

Used the regex to match the logstream name pattern in a better way

bd9d376

Update the doc with the better wording

6ece7a7

Updated the docs by changing the order of the example query and addin…

2a352ef

…g the file source implementation to the table map

ParthaI and others added 5 commits May 27, 2025 20:53

Made the changes based on the review comment

5afc34f

Removed duplicate source register

8b2716d

Update

0a36c11

Update the tp_index to use default

611d701

refactor: updated enrichment to set end_time and start_time as well a…

004d782

…s maintain order of precedence for tp_timestamp

ParthaI force-pushed the vpc-flow-log-custom-table branch from 0a74b02 to 004d782 Compare May 27, 2025 15:24

Updated the table to use the custom mapper to parse the CW event base…

de41257

…d on the source.

cbruno10 requested a review from Copilot May 27, 2025 16:22

Copilot AI reviewed May 27, 2025

View reviewed changes

ParthaI added 2 commits May 28, 2025 11:16

Updated the index.md including the CW source default value

44c4afb

Removed reference for default value CW source parameter in the doc

ef36029

cbruno10 requested a review from Copilot May 30, 2025 15:23

Copilot AI reviewed May 30, 2025

View reviewed changes

Update VPC flow log table doc examples

ac64e7b

cbruno10 requested a review from Copilot May 30, 2025 18:25

Copilot AI reviewed May 30, 2025

View reviewed changes

cbruno10 approved these changes May 30, 2025

View reviewed changes

cbruno10 merged commit 413f742 into main May 30, 2025
1 check passed

cbruno10 deleted the vpc-flow-log-custom-table branch May 30, 2025 18:29

		const VpcFlowLogTableSkippedData = "SKIPDATA"
		const VpcFlowLogTableNoData = "NODATA"


		row.OutputColumns[constants.TpTable] = VpcFlowLogTableIdentifier

		if startTime, ok := row.GetSourceValue("start_time"); ok && (startTime != VpcFlowLogTableSkippedData \|\| startTime != VpcFlowLogTableNoData \|\| startTime != VpcFlowLogTableNilValue) {

	return "aws_waf_traffic_log_mapper"
	return "vpc_flow_log_mapper"

	### Collect VPC flow logs from a CloudWatch log group with custom log format
	### Collect logs from a CloudWatch log group with custom log format

-	row.OutputColumns[constants.TpIndex] = schema.DefaultIndex
+	if interfaceID, ok := row.GetSourceValue("interface_id"); ok && interfaceID != VpcFlowLogTableNilValue {
+		row.OutputColumns[constants.TpIndex] = interfaceID
+	} else if subnetID, ok := row.GetSourceValue("subnet_id"); ok && subnetID != VpcFlowLogTableNilValue {
+		row.OutputColumns[constants.TpIndex] = subnetID
+	} else if vpcID, ok := row.GetSourceValue("vpc_id"); ok && vpcID != VpcFlowLogTableNilValue {
+		row.OutputColumns[constants.TpIndex] = vpcID
+	} else {
+		row.OutputColumns[constants.TpIndex] = schema.DefaultIndex
+	}

	You can also Collect logs from local files.
	You can also collect logs from local files.

refactor: reworked aws_vpc_flow_log table as a custom table allowing for formats to be used #137

refactor: reworked aws_vpc_flow_log table as a custom table allowing for formats to be used #137

Uh oh!

Conversation

graza-io commented Apr 2, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 9, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 17, 2025

Choose a reason for hiding this comment

Uh oh!

cbruno10 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview