# Script-layer telemetry framework proposal

**URL:** <https://community.zeek.org/t/script-layer-telemetry-framework-proposal/6594>\
**Category:** Development\
**Tags:** telemetry\
**Created:** [July 8, 2022, 8:54am UTC](https://community.zeek.org/t/script-layer-telemetry-framework-proposal/6594 "2022-07-08T08:54:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![awelzel](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/awelzel/32/609_2.png) [@awelzel](https://community.zeek.org/u/awelzel)\
**Post date:** [July 8, 2022, 8:54am UTC](https://community.zeek.org/t/script-layer-telemetry-framework-proposal/6594/1 "2022-07-08T08:54:36Z")

</div>

Hello,

we’ve been looking at exposing a higher-level script framework for the the existing lower-level `Telemetry` bifs to make it easier for Zeek script writers to expose their own metrics.To that end, there’s a proposal doc available as Google doc: [Zeek Script Telemetry Module - Google Docs](https://docs.google.com/document/d/1zJOZd6mdOJK6t6iS58XSq_lebAwGnLs4xDfV2cYRsZA/edit?usp=sharing)

A work-in-progress implementation representing this proposal can be found in a [branch of the main Zeek repo](https://github.com/zeek/zeek/blob/topic/awelzel/telemetry-script-land-v0/scripts/base/frameworks/telemetry/main.zeek)sitory. This file currently contains [usage examples](https://github.com/zeek/zeek/blob/topic/awelzel/telemetry-script-land-v0/scripts/base/frameworks/telemetry/main.zeek#L350) as well. These may be easier to read through than the API or implementation

We’re looking for feedback (as comment on the doc or here) whether this goes into a direction that people would be happy to see and use.

Thanks!

[This is a repost of a message from the development channel on Slack]
