feat: create an instrumentation package for ogma

[jmcdo29]

Which problem is this PR solving?

• Providing Instrumentation support for the Ogma logger

Short description of the changes

• I'm the author of the Ogma logger and wanted to provide instrumentation support for it, as I've had requests for such in the past. I took a similar approach as the pino instrumentation implementation, and modified it for how Ogma works. All tests should be passing, and I've assigned myself as the codeowner for this instrumentation. If there's anything else I need to do, please let me know, I'll be more than happy to do so

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: jmcdo29 / name: Jay McDoniel (6b5eb62, d77fa4a, e20843d, 86772c9, e5348bc)

[codecov]

Codecov Report

Merging #1746 (6d5ec8c) into main (84e1a6b) will decrease coverage by 0.04%.
The diff coverage is 100.00%.

❗ Current head 6d5ec8c differs from pull request most recent head e5348bc. Consider uploading reports for the commit e5348bc to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1746      +/-   ##
==========================================
- Coverage   91.50%   91.47%   -0.04%     
==========================================
  Files         145      144       -1     
  Lines        7431     7342      -89     
  Branches     1489     1466      -23     
==========================================
- Hits         6800     6716      -84     
+ Misses        631      626       -5     

Files	Coverage Δ
...emetry-instrumentation-ogma/src/instrumentation.ts	100.00% <100.00%> (ø)

... and 23 files with indirect coverage changes

[jmcdo29]

Would I be able to request a review for this? Please and thank you

[jmcdo29]

I'm doing what I can top keep this PR active and current so it can be reviewed and merged when ready. Let me know if there's anything else that can be done here 😄

[seemk]

Looks great!

[SocketSomeone]

Any updates?

[pichlermarc]

I'm the author of the Ogma logger and wanted to provide instrumentation support for it, as I've had requests for such in the past. I took a similar approach as the pino instrumentation implementation, and modified it for how Ogma works. All tests should be passing, and I've assigned myself as the codeowner for this instrumentation. If there's anything else I need to do, please let me know, I'll be more than happy to do so

Hi @jmcdo29 usually there's an instrumentation request issue that should preceed a pull request adding a new instrumentation.

Is there a reason why you decided to add this instrumentation here as opposed to hosting it in the ogma repo and adding it to the instrumentation registry?

Usually we recommend that projects host their own instrumentations as it provides them with more control over the instrumentation. It also is easier for us as we're often not familiar with the library that's being instrumented.

[pichlermarc]

Adding native instrumentation might also be an option (directly depending on the @opentelemetry/api package and emitting telemetry this way).

[jmcdo29]

I'm not opposed to hosting it in the ogma repo at all. Thanks for getting back to me on this. It seemed that adding the instrumentation to the repo was a "proper" way to go about it, but obviously any kind of hosted packages can work. I'll close this out and host it in my own repo as to not keep this open longer than it needs to be. Thanks.