[
https://issues.apache.org/jira/browse/MINIFICPP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796054#comment-16796054
]
Arpad Boda commented on MINIFICPP-622:
--------------------------------------
Just to have some written concept here.
I found two ways of gathering system information:
-Add some compiler macros in Nanofi API that provide some information about the
customer's program (compiler, version, architecture, etc).
-Execute some subprocesses with popen (to get python version and uname).
I think this information is only to be sent once, so we can either:
-Add a new section to heartbeat, which is not mandatory, only the first
heartbeat contains this information.
-Add a new operation, which is only sent once after C2 connection is initiated.
[~phrocker] , [~aldrin] do you have anything to add to the above or do you see
any pitfalls?
> Transmit binary information for CAPI implementations in heartbeat
> -----------------------------------------------------------------
>
> Key: MINIFICPP-622
> URL: https://issues.apache.org/jira/browse/MINIFICPP-622
> Project: NiFi MiNiFi C++
> Issue Type: New Feature
> Reporter: Mr TheSegfault
> Assignee: Arpad Boda
> Priority: Major
> Labels: CAPI, nanofi
>
> Heartbeats transmit a great deal of information as per our defined spec:
> [https://cwiki.apache.org/confluence/display/MINIFI/C2+Design+Proposal]
> This ticket will be responsible for figuring out what can and cannot be sent
> via these binaries created using the CAPI
>
> For CAPI : probably need the AgentBuild information, but also potentially
> information from a consumer's program – is there a way to capture information
> about THEIR binary information
>
> May include information like python version, GCC version, etc that's NOT
> about our library ( and not captured in AgentBuild) – but rather about
> theirs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
