Skip to content
New issue

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

[squid] Add dashboard, improve documentation, GA integration #11145

Merged
merged 2 commits into from
Sep 24, 2024

Conversation

taylor-swanson
Copy link
Contributor

@taylor-swanson taylor-swanson commented Sep 16, 2024

Proposed commit message

  • Improve the documentation of the integration
  • Add dashboard
  • Release integration as GA

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

cd packages/squid
elastic-package test

Related issues

Screenshots

dashboard-1 dashboard-2 dashboard-3

- Improve the documentation of the integration
- Add dashboard
- Release integration as GA
@taylor-swanson taylor-swanson added enhancement New feature or request Integration:squid Squid Proxy Team:Security-Deployment and Devices Deployment and Devices Security team [elastic/sec-deployment-and-devices] labels Sep 16, 2024
@taylor-swanson taylor-swanson self-assigned this Sep 16, 2024
@andrewkroh andrewkroh added the dashboard Relates to a Kibana dashboard bug, enhancement, or modification. label Sep 16, 2024
@elastic-vault-github-plugin-prod

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

💚 Build Succeeded

cc @taylor-swanson

@taylor-swanson taylor-swanson marked this pull request as ready for review September 16, 2024 19:59
@taylor-swanson taylor-swanson requested a review from a team as a code owner September 16, 2024 19:59
@elasticmachine
Copy link

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

Copy link
Contributor

@dwhyrock dwhyrock left a comment

Choose a reason for hiding this comment

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

LGTM.

I have a few questions, but mostly for the sake of me understanding this better.

@@ -1,11 +1,64 @@
# Squid integration
# Squid Proxy
Copy link
Contributor

Choose a reason for hiding this comment

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

This _dev/build/docs/README.md looks like it's exactly the same as docs/README.md minus additional data in the latter.

Why is this the case? And is there something in place to ensure that if something in this one gets updated, that the docs/README.md one get updated, too?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

_dev/build/docs/README.md is the "template" version and docs/README.md is the "generated" version. We edit the template version. When you run elastic-package build, it will regenerate the docs/README.md file, bringing in field definitions and sample events as part of the process.

There is a CI check (done by elastic-package check if I'm not mistaken) that verifies you've done the build process and that you've checked-in the result.

@@ -0,0 +1,2604 @@
{
"attributes": {
"description": "Overview of Squid Proxy access log events",
Copy link
Contributor

Choose a reason for hiding this comment

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

Curious how this file is generated.

Do you create the dashboard in Kibana, and then do some sort of export?

I assume these files are rarely modified by hand, and instead overwritten by a newer version of the dashboard json?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, we create the dashboard in kibana and use elastic-package export dashboards to get the json files. Same applies for modifications.

screenshots:
- src: /img/dashboard-1.png
title: Dashboard
size: 2432x2368
Copy link
Contributor

Choose a reason for hiding this comment

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

Did you have to use a photo program to get the size here? Seems a bit odd that we have to specify the size. What happens if the size is wrong?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

To be honest, I don't think the size does anything. Neither does the type for that matter, as you can give the wrong mime type and it'll fine (in fact in some cases, giving the correct mime type will actually crash Kibana, but that's a separate issue). Regarding the size, most GUI shells (Finder, Windows Explorer) will show the image size in the properties of the file.

@taylor-swanson taylor-swanson merged commit b2e43df into elastic:main Sep 24, 2024
5 checks passed
@taylor-swanson taylor-swanson deleted the enhance/squid-followup branch September 24, 2024 15:16
@elastic-vault-github-plugin-prod

Package squid - 1.0.0 containing this change is available at https://epr.elastic.co/search?package=squid

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. enhancement New feature or request Integration:squid Squid Proxy Team:Security-Deployment and Devices Deployment and Devices Security team [elastic/sec-deployment-and-devices]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[squid] Follow up items for Squid rewrite
5 participants