Skip to content

[confgenerator] Migrate important Self Log signals to Otel Logging. - #2389

Open
franciscovalentecastro wants to merge 19 commits into
masterfrom
fcovalente-otel-self-logs
Open

[confgenerator] Migrate important Self Log signals to Otel Logging.#2389
franciscovalentecastro wants to merge 19 commits into
masterfrom
fcovalente-otel-self-logs

Conversation

@franciscovalentecastro

@franciscovalentecastro franciscovalentecastro commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Description

This PR refactors fluent-bit self log pipelines and coverts them into default on Otel Logging pipelines. This are the two log signals that are refactored :

  • health_checks.log : This file is tailed and structured to have some labels about the agent.
  • Logging Ping : This is a DEBUG log that is sent every 10 minutes to verify GCL logs export is working.

This signals should the have the following labels :

  • "agent.googleapis.com/health/agentVersion" = "2.x.x"
  • "agent.googleapis.com/health/agentKind" = "ops-agent"
  • "agent.googleapis.com/health/schemaVersion" = "v1"

The tailing of "logging_module.log" is left as a Fluent-bit Pipeline which will be deleted in Ops Agent 3.0.

Related issue

b/540427023

How has this been tested?

Checklist:

  • Unit tests
    • Unit tests do not apply.
    • Unit tests have been added/modified and passed for this PR.
  • Integration tests
    • Integration tests do not apply.
    • Integration tests have been added/modified and passed for this PR.
  • Documentation
    • This PR introduces no user visible changes.
    • This PR introduces user visible changes and the corresponding documentation change has been made.
  • Minor version bump
    • This PR introduces no new features.
    • This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
    • This PR bumps the version.

@franciscovalentecastro franciscovalentecastro changed the title [Draft] Migrate important Self Log signals to Otel Logging. [confgenerator] Migrate important Self Log signals to Otel Logging. Jul 29, 2026
@rafaelwestphal

Copy link
Copy Markdown
Contributor

Can you make sure the tests are passing here? I see TestLoggingSelfLogs is failing

Comment thread confgenerator/confgenerator.go Outdated
}

agentSelfMetrics := AgentSelfMetrics{
AgentSelfMetrics := AgentSelfMetrics{

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this supposed to be upperacse or lowercase?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lower case, i'll update.

Comment thread confgenerator/confgenerator.go Outdated
}

func (uc *UnifiedConfig) GenerateOtelConfig(ctx context.Context, outDir, stateDir string) (string, error) {
func (uc *UnifiedConfig) GenerateOtelConfig(ctx context.Context, logsDir, stateDir, outDir string) (string, error) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was the change in the order here intentional?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ohhhh man! Thanks for letting me know! I brushed that change off after doing "Gemini please refactor the method with logsDir", but didn't realize the order was updated :o . Bad AI.

@franciscovalentecastro

Copy link
Copy Markdown
Contributor Author

Can you make sure the tests are passing here? I see TestLoggingSelfLogs is failing

I fixed the bug in TestLoggingSelfLogs (the logging ping was missing). It is passing now, modulo the test flakes. PTAL.

@franciscovalentecastro franciscovalentecastro added the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 6, 2026
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants