Detail Levels Seem To Be Ignored When Defined In Ruleset File

[hannahchiodo-msft]

My filter file reports at the expected detail level if I don't use a ruleset, e.g.:

keynames:
  nickname_key: "otel.trace2.nickname"

nicknames:
  "office": "dl:process"

defaults:
  ruleset: "dl:drop"

However, when I use a separate ruleset file, it seems to use the default detail level regardless:

keynames:
  nickname_key: "otel.trace2.nickname"

nicknames:
  "office": "rs:office"

rulesets:
  "rs:office": "C:/ProgramData/git-telemetry-service/rs-office.yml"

defaults:
  ruleset: "dl:drop"

My ruleset file:

commands:
  "git:config":             "dl:drop"
  "git:cat-file":           "dl:drop"
  "git:maintenance":        "dl:drop"
  "git:for-each-repo":      "dl:drop"

default:
  detail: "dl:process"

Yet whatever detail level I set in the ruleset, it still reports at the default detail level.

[jeffhostetler]

Try changing "default:" to "defaults:" in your ruleset file.

[jeffhostetler]

I'm surprised it didn't throw an error for an undefined key.

[hannahchiodo-msft]

Yep, using defaults instead of default fixed it - glad this was an easy fix on my end. It does seem surprising that validation didn't catch this.