Skip to content
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

alerts endpoint returns null for body.cef_details with email alerts and transformed fields are in body.details #377

Closed
gsreynolds opened this issue Dec 13, 2023 · 0 comments · Fixed by #420
Milestone

Comments

@gsreynolds
Copy link
Member

gsreynolds commented Dec 13, 2023

Custom column definitions look inside alerts[*].body.cef_details.${accessorPath}

const path = `alerts[*].body.cef_details.${accessorPath}`;

However, alerts that originated from Email and were transformed by Event Orchestration rules seem to put custom_details fields into alerts[*].body.details and .cef_details is empty:

"body": {
    "contexts": [],
    "details": {
        "runbook": "runbook URL",
        "environment": "production"
    },
    "cef_details": null,
    "type": "alert_body"
},

Events API v2 alert:

"body": {
    "contexts": [],
    "details": {
        "quote": "Difficult to see. Always in motion is the future..."
    },
    "cef_details": {
        "client": null,
        "client_url": null,
        "contexts": null,
        "creation_time": null,
        "dedup_key": "df21ba4700714a9ca98a8e1a678e3ff9",
        "description": "button up the loose ends",
        "details": {
            "quote": "Difficult to see. Always in motion is the future..."
        },
        "event_class": "Soul",
        "message": "button up the loose ends",
        "mutations": [],
        "priority": null,
        "reporter_component": null,
        "reporter_location": null,
        "service_group": "obtain",
        "severity": "warning",
        "source_component": "Daltfresh",
        "source_location": null,
        "source_origin": "242.95.132.249",
        "urgency": null,
        "version": "1.0"
    },
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 a pull request may close this issue.

1 participant