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

[Citrix ADC] Add Integration Package with VPN Data Stream #4473

Merged
merged 8 commits into from
Dec 20, 2022

Conversation

harnish-crest
Copy link
Contributor

@harnish-crest harnish-crest commented Oct 19, 2022

  • Enhancement

What does this PR do?

  • Added 1 data stream (vpn metrics).
  • Added data collection logic for the data streams.
  • Added the ingest pipeline for the data streams.
  • Mapped fields according to the ECS schema and added Fields metadata in the appropriate yaml files.
  • Added dashboards and visualizations.
  • Added system test cases for the data stream.

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

  • Clone integrations repo.
  • Install elastic-package locally.
  • Start elastic stack using elastic-package.
  • Move to integrations/packages/citrix_adc directory.
  • Run the following command to run tests.
    elastic-package test

Related issues

Screenshots

citrix_adc-vpn-dashboard

@kush-elastic
Copy link
Collaborator

/test

@elasticmachine
Copy link

elasticmachine commented Oct 19, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-12-19T13:04:56.727+0000

  • Duration: 17 min 46 sec

Test stats 🧪

Test Results
Failed 0
Passed 31
Skipped 0
Total 31

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

elasticmachine commented Oct 19, 2022

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (5/5) 💚
Files 100.0% (5/5) 💚 6.667
Classes 100.0% (5/5) 💚 6.667
Methods 100.0% (48/48) 💚 15.0
Lines 97.782% (1102/1127) 👍 1.76
Conditionals 100.0% (0/0) 💚

Copy link
Collaborator

@kush-elastic kush-elastic left a comment

Choose a reason for hiding this comment

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

Add the dashboard screenshot in view mode rather than adding it in edit mode.

Copy link
Collaborator

@kush-elastic kush-elastic left a comment

Choose a reason for hiding this comment

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

LGTM!

@kush-elastic
Copy link
Collaborator

/test

@botelastic
Copy link

botelastic bot commented Dec 8, 2022

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Dec 8, 2022
@botelastic
Copy link

botelastic bot commented Dec 8, 2022

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

@botelastic botelastic bot removed the Stalled label Dec 13, 2022
@harnish-crest harnish-crest marked this pull request as ready for review December 13, 2022 10:31
@harnish-crest harnish-crest requested a review from a team as a code owner December 13, 2022 10:31
- name: count
type: float
description: Number of SSL VPN tunnels formed between VPN server and client.
metric_type: counter
Copy link
Contributor

Choose a reason for hiding this comment

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

This cannot be a counter metric_type.

- name: count
type: float
description: Number of client configuration requests received by VPN server.
metric_type: counter
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here we could not get a cumulative incremental value. Please change to gauge.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

The counters which you refer here is something which captures all the response fields and its different from what we consider as metric_type. The metric_type gauge is a single-valued metric which goes up and down. Ex: temperature. The metric_type: counter is a cumulative type which only goes up. Ex: Number of requests processed by web server.
I would recommend you to revisit the metric_type for all the fields and make changes wherever applicable.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

For the client_server.request.hit.count it could be gauge. So we can update it as per your suggestions. But for the configuration_request_served.count, it seems like a counter as per your example. Also as per our understanding, it aligns more with the counter. But let me know if you still want to change it to counter, we'll change it for this field too.

Copy link
Contributor

Choose a reason for hiding this comment

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

I would recommend to keep both as gauge values.

@muthu-mps
Copy link
Contributor

@SubhrataK - Please take a look into the changes.

@harnish-crest harnish-crest requested review from muthu-mps and removed request for lalit-satapathy and SubhrataK December 15, 2022 09:28
Copy link
Contributor

@muthu-mps muthu-mps left a comment

Choose a reason for hiding this comment

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

Looks Good!

@kush-elastic kush-elastic merged commit 18166df into elastic:main Dec 20, 2022
@elasticmachine
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Integration:Citrix-Netscaler Team:Service-Integrations Label for the Service Integrations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants