Correct bytes sent/received field aliases for pan:firewall_cloud #260
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
🎉 Thanks for opening this pull request! We really appreciate contributors like you! 🙌 |
paulmnguyen
force-pushed
the
develop
branch
2 times, most recently
from
de4dfdc
to
d7bd687
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Flip the bytes_in and bytes_out field aliases.
Motivation and Context
'bytes_in' should be mapped to the BytesReceived field from the perspective of the client in a client-to-server connection. Currently, bytes_in is evaluated from the perspective of the server.
How Has This Been Tested?
This change was tested and evaluated in my organization's Splunk environment using log events from Cortex Data Lake/Prisma Access. We were able to confirm that the change provides the expected mapping of BytesReceived and BytesSent to CIM-compliant fields.
This change was also evaluated using the existing built-in tests.
Screenshots (if appropriate)
Types of changes
Checklist