-
Notifications
You must be signed in to change notification settings - Fork 444
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
[f5_bigip] Initial Release for the F5 BIG-IP #4242
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
🌐 Coverage report
|
|
||
## Overview | ||
|
||
The [F5 BIG-IP](https://www.f5.com) integration allows users to monitor LTM, AFM, APM, ASM, and AVR activity. F5 BIG-IP covers software and hardware designed around application availability, access control, and security solutions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The [F5 BIG-IP](https://www.f5.com) integration allows users to monitor LTM, AFM, APM, ASM, and AVR activity. F5 BIG-IP covers software and hardware designed around application availability, access control, and security solutions. | |
The [F5](https://www.f5.com) BIG-IP integration allows users to monitor [LTM](https://www.f5.com/products/big-ip-services/local-traffic-manager), [AFM](https://www.f5.com/products/security/advanced-firewall-manager), [APM](https://www.f5.com/products/security/access-policy-manager), [ASM](https://www.f5.com/pdf/products/big-ip-application-security-manager-overview.pdf), and [AVR](https://clouddocs.f5.com/training/community/analytics/html/class1/class1.html) activity. F5 BIG-IP covers software and hardware designed around application availability, access control, and security solutions. |
Are there better links for ASM and AVR?
Alternatively maybe just...
The [F5 BIG-IP](https://www.f5.com) integration allows users to monitor LTM, AFM, APM, ASM, and AVR activity. F5 BIG-IP covers software and hardware designed around application availability, access control, and security solutions. | |
The [F5 BIG-IP](https://www.f5.com/products/big-ip-services) integration allows users to monitor LTM, AFM, APM, ASM, and AVR activity. F5 BIG-IP covers software and hardware designed around application availability, access control, and security solutions. |
and use any useful links in the set above in the "Data stream" section below.
"expected": [ | ||
{ | ||
"@timestamp": "2018-12-17T22:46:04.000Z", | ||
"destination": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GeoIP look-ups for destination and source in the common pipeline?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As all the event categories doesn’t have a field that contains public IP, so we haven’t use GeoIP in default pipeline.
}, | ||
"related": { | ||
"hosts": [ | ||
"81.2.69.192:80" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ensure that hosts have had any ports removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We noticed in the live log that the field value couldn't follow a specific pattern, therefore we decided it would be better to delete it from related.host in order to keep the related.host field's proper value.
@@ -0,0 +1,20 @@ | |||
- name: data_stream.dataset |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Move ECS-defined fields into ecs.yml with external definitions where possible.
@@ -0,0 +1,840 @@ | |||
- name: f5_bigip.log |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there documentation available for the definitions of the use of these fields in the f5 docs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have gone through the Telemetry Streaming doc which contains the sample events having only field names but no description.
"response": { | ||
"code": 0 | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering how many of these nested fields with no siblings need to be nested (there are a fair few of them).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are getting many other fields like “ResponseDuration” and we have grouped those fields under the name “response”, so we kept it as a type “group”.
@vinit-elastic we currently have an F5 integration which supports 2 BIG-IP products. Rather than shipping a new package, do you think we could upgrade the current package with the new/updated pipelines? This avoids having to deprecate the current F5 package and ensures users can easily access the improved integration, without having to move to a new integration. |
Hey Jamie - The older integration uses the F5 default input (fetch logs directly from the F5 instance) and the new integration leverages the |
Discussed offline, and agreed that we'll stick with a new F5 BIG-IP integration as the current experimental integration relies on syslog directly from ASM/AFM, whereas the new integration leverages the Telemetry Streaming Services. We'll be deprecating the experimental F5 module and integration once this new one is available. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think some overall discussion has to be done around ignore_failure
, but that is not related to this single package, the rest is LGTM for now.
Great job!
Package f5_bigip - 0.1.0 containing this change is available at https://epr.elastic.co/search?package=f5_bigip |
What does this PR do?
Integration release checklist
This checklist is intended for integrations maintainers to ensure consistency
when creating or updating a Package, Module or Dataset for an Integration.
All changes
New Package
Dashboards changes
Log dataset changes
How to test this PR locally
Related issues
Screenshots