sflow | see link ) - parses sflow samples

In PrepData, string are initialized without a given length, leading to arbitrary long string (until null '\0' is reached).

The correct code is :

When you add that argument from the Kafka container, it scrapes the MBeans of the JMX metrics, not any actual topic data, since Prometheus isn't a Kafka consumer

From that JMX information, you'd see metrics such as message rate and replica counts

If you'd like to read topic data, the Kafka Connect framework could be used, and there's a plugin for Influx, Mongo, and Elasticsearch, which are all good Grafana sources. I'm not sure if there's a direct Kafka to Prometheus importer, but I think it would require using the PushGateway

The node has a ScheduledActivityObserver that subscribes to the feed of new states added to the vault. Whenever a new state is added to the vault:

• The observer checks if the state is a SchedulableState
• If the state is a SchedulableState, the observer calls nextScheduledActivity to establish at what future point in time to run the scheduled activity, and adds the scheduled activity to its schedule

• Once this future point in time is reached, the observer calls nextScheduledActivity again to retrieve the scheduled activity and the point in time when the scheduled activity is supposed to occur

  • If the point in time is in the past, the observer runs the scheduled activity
  • If the point in time is now in the future, the observer considers the scheduled activity to have been rescheduled and reschedules it for that future point in time

In your case, nextScheduledActivity finds the point in time for the scheduled activity by calling Instant.now().plusSeconds(10). Since this expression is re-evaulated every time you call nextScheduledActivity, the observer will always consider this activity to have been rescheduled to ten seconds in the future, and never run it.

Instead, you need to evaluate the point in time to run the scheduled activity once and for all at state creation time. For example:

How you are defining flows? You need to set log=true in the flow definition in order to generate flow records. Also, set an activeTimeout to limit the delay before you receive a flow record, or set flowStart=true if you want an immediate notification and don't care about flow counter values.