Skip to content

DAOS-17447 control: Selective telemetry registration #16491

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

Open
wants to merge 1 commit into
base: google/2.6
Choose a base branch
from

Conversation

mjmac
Copy link
Contributor

@mjmac mjmac commented Jun 9, 2025

Update daos_agent configuration and logic to allow for
selective enablement and registration of client telemetry.

Adds two new daos_agent configuration parameters:
telemetry_enabled_procs:
telemetry_disabled_procs:

Setting one or the other of these will specify a pattern
against which connecting client process names will be
matched to provide more control over behavior. If neither
are set, then all clients will have telemetry enabled,
assuming that the value of telemetry_enabled is true.

Includes some improvements to the client telemetry init
logic to more clearly implement different use cases.

Change-Id: Iaa8b98b008de32e9d3b2c2b8d7583a5155fff9de
Signed-off-by: Michael MacDonald mjmac@google.com

Copy link

github-actions bot commented Jun 9, 2025

Ticket title is 'Allow hybrid client telemetry configuration'
Status is 'Open'
https://daosio.atlassian.net/browse/DAOS-17447

@mjmac mjmac force-pushed the mjmac/DAOS-17447-g26 branch from a4655f4 to 927097d Compare June 9, 2025 15:04
Base automatically changed from mjmac/DAOS-17043-g26 to google/2.6 June 11, 2025 16:04
@daosbuild3
Copy link
Collaborator

@daosbuild3
Copy link
Collaborator

@daosbuild3
Copy link
Collaborator

Update daos_agent configuration and logic to allow for
selective enablement and registration of client telemetry.

Adds two new daos_agent configuration parameters:
  telemetry_enabled_procs: <regex>
  telemetry_disabled_procs: <regex>

Setting one or the other of these will specify a pattern
against which connecting client process names will be
matched to provide more control over behavior. If neither
are set, then all clients will have telemetry enabled,
assuming that the value of telemetry_enabled is true.

Includes some improvements to the client telemetry init
logic to more clearly implement different use cases.

Change-Id: Iaa8b98b008de32e9d3b2c2b8d7583a5155fff9de
Signed-off-by: Michael MacDonald <mjmac@google.com>
@mjmac mjmac force-pushed the mjmac/DAOS-17447-g26 branch from 927097d to 6c90cc6 Compare June 11, 2025 16:41
@daosbuild3
Copy link
Collaborator

@daosbuild3
Copy link
Collaborator

@daosbuild3
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants