Skip to content

Updates to OTel VPC Flow Log Dashboard + YAML Dashboard Validator#17358

Merged
strawgate merged 28 commits intomainfrom
update-vpc-flow
Mar 11, 2026
Merged

Updates to OTel VPC Flow Log Dashboard + YAML Dashboard Validator#17358
strawgate merged 28 commits intomainfrom
update-vpc-flow

Conversation

@strawgate
Copy link
Copy Markdown
Contributor

@strawgate strawgate commented Feb 11, 2026

Updates to the OTel VPC Flow Log Dashboard + YAML version of dashboard leveraging https://github.com/strawgate/kb-yaml-to-lens

Removes _dev folder from content packs during build

Iterating on the actual panels here strawgate/kb-yaml-to-lens#914

Overview

Overview

Interface Analysis

Interface Analysis Interface Analysis 2

Traffic Analysis

Traffic Analysis Traffic Analysis 2

Current Dashboard on Main

The following is the dashboard on main that is being replaced
Current Main

@strawgate strawgate requested review from a team as code owners February 11, 2026 00:36
Comment thread packages/aws_vpcflow_otel/changelog.yml
Comment thread .github/workflows/validate-yaml-dashboards.yml Outdated
Comment thread .github/workflows/validate-yaml-dashboards.yml Outdated
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changelog PR link issue has already been flagged in an unresolved comment (line 5 of packages/aws_vpcflow_otel/changelog.yml - links to #16969 but should be #17358).

Previous review comments on the workflow file have been addressed:

  • PyPI packages are now pinned to specific version (@0.2.7) instead of @latest
  • The diff -r comparison approach was replaced with --exit-non-zero-on-change flag

The implementation looks sound overall - the YAML dashboard validation workflow and the _dev folder removal for content packages follow existing patterns in the codebase.


Why is Claude responding? | Type @claude to interact further

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

@elastic-vault-github-plugin-prod
Copy link
Copy Markdown

elastic-vault-github-plugin-prod Bot commented Feb 11, 2026

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@andrewkroh andrewkroh added dashboard Relates to a Kibana dashboard bug, enhancement, or modification. Integration:aws_vpcflow_otel AWS VPC Flow Logs OpenTelemetry Assets Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations] labels Feb 11, 2026
Comment thread .buildkite/scripts/common.sh Outdated
Copy link
Copy Markdown
Contributor

@teresaromero teresaromero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes lgtm, however i'd like to get some extra eyes 👀

@strawgate
Copy link
Copy Markdown
Contributor Author

@claude let's remove the _dev clean-up from this, we'll merge this after #17370 and we wont need the _dev cleanup anymore

@mykola-elastic waiting on #17370 to merge i think

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 13, 2026

Claude finished @strawgate's task in 1m 2s —— View job


Removing _dev Cleanup Code

  • Gather context and understand the changes to remove
  • Remove the _dev cleanup code from .buildkite/scripts/common.sh
  • Commit and push changes

Done! Removed the remove_dev_folder_for_content_packages function and its calls from .buildkite/scripts/common.sh. This workaround will no longer be needed once #17370 is merged.

Changes pushed in commit 87367c1.

--- | View branch update-vpc-flow


Why is Claude responding? | Type @claude to interact further

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

This workaround is no longer needed after #17370 is merged, which adds
support for _dev folders in content packages in the package spec.

Co-authored-by: Bill Easton <strawgate@users.noreply.github.com>
@strawgate
Copy link
Copy Markdown
Contributor Author

@claude that pr i mentioned has landed, is this ready to go?

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 17, 2026

Claude finished @strawgate's task in 2m 20s —— View job


Checking PR Readiness

Status Summary:

Yes, PR #17370 has been merged (on 2026-02-16), and I've verified the current state of this PR:

Check Status
PR #17370 merged ✅ Merged
_dev cleanup code removed ✅ Removed in previous commit
GitHub Actions CI ✅ All passing
Buildkite CI ⌛ Build #38356 running
Review approval ✅ Approved by @mykola-elastic
Review threads ✅ All resolved

The PR is looking good. Once the Buildkite build passes, it should be ready to merge. The branch is up-to-date with main (merged in commit 210e5fd).

I also resolved the outdated review thread from @mykola-elastic about the TODO reference - since that code was removed entirely when the _dev cleanup workaround was removed, the comment is no longer applicable.

--- | View branch update-vpc-flow


Why is Claude responding? | Type @claude to interact further

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

Comment thread packages/aws_vpcflow_otel/manifest.yml Outdated
Comment thread packages/aws_vpcflow_otel/manifest.yml Outdated
@strawgate strawgate enabled auto-merge (squash) March 10, 2026 22:03
@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

History

@ishleenk17
Copy link
Copy Markdown
Member

Thanks @strawgate for the changes. Looks good!
We are working on revamping our existing content packs anyhow.
This is a good step towards that.

Copy link
Copy Markdown
Contributor

@lalit-satapathy lalit-satapathy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code owner approval

@strawgate strawgate merged commit 582b57d into main Mar 11, 2026
10 checks passed
@strawgate strawgate deleted the update-vpc-flow branch March 11, 2026 11:59
@elastic-vault-github-plugin-prod
Copy link
Copy Markdown

Package aws_vpcflow_otel - 0.2.0 containing this change is available at https://epr.elastic.co/package/aws_vpcflow_otel/0.2.0/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dashboard Relates to a Kibana dashboard bug, enhancement, or modification. Integration:aws_vpcflow_otel AWS VPC Flow Logs OpenTelemetry Assets Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants