Thor.kell/add anthropic compliance logs

[tkell]

What does this PR do?

This might be right? Assets for anthropic-compliance-logs, re-using the existing source type id, but declaring a new folder with new assets.

I am unsure if I need to override the tile in web-ui, but I'll see if this builds first.

Motivation

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[dd-octo-sts]

⚠️ Recommendation: Add qa/skip-qa label

This PR does not modify any files shipped with the agent.

To help streamline the release process, please consider adding the qa/skip-qa label if these changes do not require QA testing.

[dd-octo-sts]

Validation Report

Validation	Description	Status
labeler	Validate PR labeler config matches integration directories	❌
saved-views	Validate saved view JSON file structure and fields	❌

Run ddev validate all changed --fix to attempt to auto-fix supported validations.

Passed validations (18)

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and Codecov settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
readmes	Validate README files have required sections	✅
version	Validate version consistency between package and changelog	✅

View full run

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 32c48f2fba

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Differentiate warning and critical trigger conditions

This monitor defines both critical and warning as 1 while evaluating a single last("1h") < 1 condition, so the warning path is effectively unreachable and the {{#is_warning}} branch (which claims a 30-minute early warning) will not trigger as intended. As written, users only get the critical behavior, which defeats the staged alerting described in the message.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Align parser test fixture with remapper output

The pipeline remaps top-level type to evt.name with preserveSource: false in assets/logs/anthropic-compliance-logs.yaml, so keeping type in the expected parsed payload makes this fixture inconsistent with the configured processors. This causes parser-test expectations to diverge from actual pipeline behavior and can fail integration asset validation.

Useful? React with 👍 / 👎.