[Citrix ADC] Add Integration Package with lbvserver Data Stream

[harnish-crest]

• Enhancement

What does this PR do?

• Added 1 data stream (lbvserver 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

• Relates Create package to monitor server workers using Citrix ADC (Netscaler) #3746
• Relates [Citrix ADC] Add Integration Package with Interface Data Stream  #4322
• Relates [Citrix ADC] Add Integration Package with Service Data Stream #4364
• Relates [Citrix ADC] Add Integration Package with System Data Stream #4458
• Relates [Citrix ADC] Add Integration Package with VPN Data Stream #4473

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-11-28T10:23:56.760+0000

• Duration: 15 min 15 sec

Test stats 🧪

Test	Results
Failed	0
Passed	19
Skipped	0
Total	19

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[kush-elastic]

/test

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (3/3)	💚
Files	100.0% (3/3)	💚
Classes	100.0% (3/3)	💚
Methods	100.0% (29/29)	💚 1.961
Lines	97.902% (700/715)	👍 2.116
Conditionals	100.0% (0/0)	💚

[kush-elastic]

/test

[muthu-mps]

closes #3746

[muthu-mps]

Can this be a gauge value ?

[harnish-crest]

@muthu-mps, this field is containing the value of total backup server hits. Based on our understanding total backup hits won't get fluctuate it will only increase, it could get only reset on some unexpected scenarios but won't fluctuate. It should be consider as counter.

[muthu-mps]

Can we remove the over the time in the Visualisation names ?

[harnish-crest]

Can we remove the over the time in the Visualisation names ?

We generally follows this practice when it is a line chart. If we remove the over time from the title then it doesn't look compact. For example, title for the Spillovers over time, if we remove over time here then it would be moreover like Spillovers only. instead of that Spillovers over time give the sense that this dashboards is showing Spillovers against the time.

[muthu-mps]

LGTM!

[elasticmachine]

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