Add TYCHON Quantum Command integration package#20142
Conversation
|
💚 CLA has been signed |
ReviewersBuildkite won't run for external contributors automatically; you need to add a comment:
NOTE: https://github.com/elastic/integrations/blob/main/.buildkite/pull-requests.json contains all those details. |
andrewkroh
added
needs CLA
andrewkroh
removed
the
needs CLA
There was a problem hiding this comment.
Please re-export all the dashboards using elastic-package. The direct API save leaves the object as a JSON-encoded object in a string instead of a JSON object.
There was a problem hiding this comment.
I re-exported the dashboards and dependencies with elastic-package However, the resulting files still contain Kibana JSON-string fields such as panelsJSON, searchSourceJSON, and index pattern fields like fieldAttrs and fields. Could you clarify the exact normalization/export workflow you expect for package-ready saved objects in this repo?
There was a problem hiding this comment.
How did you do that? Did you follow the instruction here?
There was a problem hiding this comment.
that is correct, used 'elastic-package export dashboards' command. I provided them in latest commit. Let me know if there's something I'm missing in this process.
There was a problem hiding this comment.
Please remove the tests directory.
| **Exported fields** | ||
|
|
||
| | Field | Description | Type | | ||
| |---|---|---| | ||
| | @timestamp | | date | | ||
| | event.category | | keyword | | ||
| | event.dataset | | keyword | | ||
| | event.ingested | | date | | ||
| | host.hostname | | keyword | | ||
| | host.id | | keyword | | ||
| | id | Tychon unique document identifier for the application record. | keyword | | ||
| | kerberos.config_source | | keyword | | ||
| | kerberos.has_aes128 | | boolean | | ||
| | kerberos.has_aes256 | | boolean | | ||
| | kerberos.has_des | | boolean | | ||
| | kerberos.has_rc4 | | boolean | | ||
| | kerberos.is_quantum_safe | | boolean | | ||
| | kerberos.raw_bitmask | | long | | ||
| | kerberos.supported_types | | keyword | | ||
| | observer.domain | | keyword | | ||
| | observer.hostname | | keyword | |
There was a problem hiding this comment.
These should not be included in the _dev/build/docs file, they should be templated into the final file in README.md by addition of the short code.
… in README Template with {{ fields tychon_pqc }} and {{ event tychon_pqc }} - replaced dashboard and supporting objects with those output from 'elastic-package export dashboards' command.
3 participants
Proposed commit message
Add the TYCHON Quantum Command integration package for Elastic Agent and Fleet
This change introduces the initial
2.0.4release of thetychon_quantum_commandintegration package aligned to the current TYCHON Quantum Command release.WHAT:
tychon_pqclogs data stream for TYCHON Quantum Command NDJSON/JSON output collected through thefilestreaminput.logs-tychon_quantum_command.tychon_pqc-*and publish analytical destination indices for TYCHON datasets including inventory, applications, certificates, ciphers, crypto libraries, keystores, VPN clients, IPsec tunnels, MACsec, installed apps, browser extensions, assets, archives, and system readiness.WHY:
2.0.4so the initial integration release matches the currently released TQC version.Checklist
changelog.ymlfile.Author's Checklist
elastic-package checkcompletes successfully.elastic-package buildproducestychon_quantum_command-2.0.4.zip.sample_event.jsonis a real event and not the default placeholder.logs-tychon_quantum_command.tychon_pqc-*.How to test this PR locally
elastic/integrations.packages/tychon_quantum_command.