Skip to content

Conversation

shayancanonical
Copy link
Contributor

Issue

We would like to be able to instrument our charm and generate traces to discover inefficiencies in charm code execution. The observability team has developed a charm for tempo that we would like to integrate with.

Solution

Integrate with the tempo charm

Considerations

  1. We must use COS lite with edge until it is release to stable with some critical changes
  2. We are sending traces with HTTP until some rough edges are rounded with HTTPS

image


if server_cert is None:
logger.warning(
f"{charm}.{server_cert_getter} returned None; sending traces over INSECURE connection."

Check failure

Code scanning / CodeQL

Clear-text logging of sensitive information

This expression logs [sensitive data (certificate)](1) as clear text.
@shayancanonical shayancanonical changed the title Add support for tracing with tempo-k8s [DPE-4616] Add support for tracing with tempo-k8s Jun 12, 2024
@dragomirp dragomirp merged commit d197a7a into main Jun 15, 2024
@dragomirp dragomirp deleted the feature/tempo_tracing branch June 15, 2024 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants