# Log Streaming Organization Metadata

**URL:** <https://community.auth0.com/t/log-streaming-organization-metadata/101080>\
**Category:** Get Help\
**Tags:** extensibility, deployment-extensions\
**Created:** [February 22, 2023, 7:17pm UTC](https://community.auth0.com/t/log-streaming-organization-metadata/101080 "2023-02-22T19:17:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kyle.flanagan](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kyle.flanagan](https://community.auth0.com/u/kyle.flanagan)\
**Post date:** [February 22, 2023, 7:17pm UTC](https://community.auth0.com/t/log-streaming-organization-metadata/101080/1 "2023-02-22T19:17:25Z")

</div>

tl;dr: log stream contains metadata for user objects but not for organization objects

I have a log stream set up to a custom webhook. The functionality is working as expected for users: e.g. I get log entries for logins, modifications, etc. Specifically, for users, if the user’s metadata is changed, I get a log entry with the metadata change in the request body as well as in the response, e.g.:

_Trimmed for brevity_

```auto
{
  "date": "2023-02-22T14:55:59.479Z",
  "type": "sapi",
  "description": "Update a User",
...
  "details": {
    "request": {
      "method": "patch",
      "path": "/api/v2/users/auth0%7C63f4fcXXXX",
      "query": {},
      "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36",
      "body": {
        "user_metadata": {
          "test": "just a test",
          "test2": "can you see me?"
        },
        "app_metadata": {}
      },
      "channel": "https://manage.auth0.com/",
...
    "response": {
      "statusCode": 200,
      "body": {
        "created_at": "2023-02-21T17:17:35.683Z",
        "email": "user@mail.com",
        ...
        "email_verified": false,
        "user_metadata": {
          "test": "just a test",
          "test2": "can you see me?"
        }
      }
    }
  }...
}

```

This is _not_ true for Organization metadata changes. E.g. this is the log event after updating an Organization’s metadata:

```auto
{
  "date": "2023-02-22T18:12:29.774Z",
  "type": "sapi",
  "description": "Modify an Organization",
  ...
  "details": {
    "request": {
      "method": "patch",
      "path": "/api/v2/organizations/org_iRZBXXXX",
      "query": {},
      "body": {},
      "channel": "https://manage.auth0.com/",
      "auth": {
        "user": {
          "user_id": "auth0|61731aXXXX",
          "name": "user@mail.com",
          "email": "user@mail.com"
        },
       ...
      }
    },
    "response": {
      "statusCode": 200,
      "body": {
        "id": "org_iRZBXXXX",
        "name": "org-test"
      }
    }
  },
...}

```

Is this behavior expected, i.e. that user metadata is logged but organization metadata is not? I don’t see anything in the docs highlighting it as excluded.

FYI on my custom log stream I have _no_ filters applied so I can troubleshoot, so it’s not a filtering issue.

![image](https://global.discourse-cdn.com/auth0/original/3X/0/a/0a7cbec9e3ecb8318a8dcd2f88c0a6e839ded501.png)

Also, I’m using the Dashboard → Monitoring → Logs for my troubleshooting to validate that it’s not an issue with the webhook.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [February 24, 2023, 9:28am UTC](https://community.auth0.com/t/log-streaming-organization-metadata/101080/2 "2023-02-24T09:28:33Z")

</div>

Hey there!

That’s a good question. Let me confirm it with the team and get back to you shortly!

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [February 27, 2023, 10:49am UTC](https://community.auth0.com/t/log-streaming-organization-metadata/101080/5 "2023-02-27T10:49:08Z")

</div>

So actually got some news back from the team. Generally speaking for orgs we only put the minimum to limit what’s going over the wire.

You can fetch org metadata if necessary using org\_id, for example

---

<div class="post-metadata">

**Author:** ![kyle.flanagan](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@kyle.flanagan](https://community.auth0.com/u/kyle.flanagan)\
**Post date:** [February 27, 2023, 2:40pm UTC](https://community.auth0.com/t/log-streaming-organization-metadata/101080/6 "2023-02-27T14:40:10Z")

</div>

Thanks for the follow-up. Would definitely be interested in receiving the org metdata via Log Stream in the future if you could pass that feedback along. For now, we’ll fallback to the API.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [February 28, 2023, 10:10am UTC](https://community.auth0.com/t/log-streaming-organization-metadata/101080/7 "2023-02-28T10:10:51Z")

</div>

Sure no problem! I would actually encourage you to actually pass that feedback using our Feedback category here:

> **[Feedback](https://community.auth0.com/c/feedback/95)**
>
> Submit and vote on product feedback and feature requests.

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [March 3, 2023, 9:28am UTC](https://community.auth0.com/t/log-streaming-organization-metadata/101080/8 "2023-03-03T09:28:36Z")

</div>


