@contrast/agent-bundle 5.47.0 → 5.48.0

package/node_modules/pino/docs/transports.md

@@ -15,7 +15,7 @@ now referred to as [Legacy Transports](#legacy-transports).
 
 From Pino v7 and upwards transports can also operate inside a [Worker Thread][worker-thread]
 and can be used or configured via the options object passed to `pino` on initialization.
-In this case the transports would always operate asynchronously, and logs would be
+In this case the transports would always operate asynchronously (unless `options.sync` is set to `true` in transport options), and logs would be
 flushed as quickly as possible (there is nothing to do).
 
 [worker-thread]: https://nodejs.org/dist/latest-v14.x/docs/api/worker_threads.html
@@ -25,7 +25,7 @@ flushed as quickly as possible (there is nothing to do).
 A transport is a module that exports a default function that returns a writable stream:
 
 ```js
-import { createWriteStream } from 'fs'
+import { createWriteStream } from 'node:fs'
 
 export default (options) => {
   return createWriteStream(options.destination)
@@ -54,7 +54,7 @@ The exported function can also be async. If we use an async function we can thro
 if the transform could not be opened. As an example:
 
 ```js
-import fs from 'fs'
+import fs from 'node:fs'
 import { once } from 'events'
 export default async (options) => {
   const stream = fs.createWriteStream(options.destination)
@@ -84,8 +84,8 @@ is serialized and injected into the transport worker thread, then passed to the
 This means that the options object can only contain types that are supported by the
 [Structured Clone Algorithm][sca] which is used to (de)serialize objects between threads.
 
-What if we wanted to use both transports, but send only error logs to `some-file-transport` while
-sending all logs to `my-transport.mjs`? We can use the `pino.transport` function's `destinations` option:
+What if we wanted to use both transports, but send only error logs to `my-transport.mjs` while
+sending all logs to `some-file-transport`? We can use the `pino.transport` function's `level` option:
 
 ```js
 const pino = require('pino')
@@ -124,6 +124,19 @@ const transport = pino.transport({
 pino(transport)
 ```
 
+To make pino log synchronously, pass `sync: true` to transport options.
+```js
+const pino = require('pino')
+const transport = pino.transport({
+  targets: [
+    { target: '/absolute/path/to/my-transport.mjs', level: 'error' },
+  ],
+  dedupe: true,
+  sync: true,
+});
+pino(transport);
+```
+
 For more details on `pino.transport` see the [API docs for `pino.transport`][pino-transport].
 
 [pino-transport]: /docs/api.md#pino-transport
@@ -209,7 +222,7 @@ In case you want to both use a custom transport, and output the log entries with
       }
     ]
 
-    const logger = pino(pino.transport({ targets: transports })
+    const logger = pino(pino.transport({ targets: transports }))
 ```
 
 ### Creating a transport pipeline
@@ -218,7 +231,7 @@ As an example, the following transport returns a `Transform` stream:
 
 ```js
 import build from 'pino-abstract-transport'
-import { pipeline, Transform } from 'stream'
+import { pipeline, Transform } from 'node:stream'
 export default async function (options) {
   return build(function (source) {
     const myTransportStream = new Transform({
@@ -378,7 +391,7 @@ A legacy Pino "transport" is a supplementary tool that consumes Pino logs.
 Consider the following example for creating a transport:
 
 ```js
-const { pipeline, Writable } = require('stream')
+const { pipeline, Writable } = require('node:stream')
 const split = require('split2')
 
 const myTransportStream = new Writable({
@@ -410,20 +423,27 @@ PRs to this document are welcome for any new transports!
 
 ### Pino v7+ Compatible
 
++ [@axiomhq/pino](#@axiomhq/pino)
 + [@logtail/pino](#@logtail/pino)
-+ [pino-elasticsearch](#pino-elasticsearch)
-+ [pino-pretty](#pino-pretty)
-+ [pino-loki](#pino-loki)
-+ [pino-seq-transport](#pino-seq-transport)
-+ [pino-sentry-transport](#pino-sentry-transport)
++ [@macfja/pino-fingers-crossed](#macfja-pino-fingers-crossed)
++ [@openobserve/pino-openobserve](#pino-openobserve)
 + [pino-airbrake-transport](#pino-airbrake-transport)
-+ [pino-datadog-transport](#pino-datadog-transport)
-+ [pino-slack-webhook](#pino-slack-webhook) 
 + [pino-axiom](#pino-axiom)
-+ [pino-opentelemetry-transport](#pino-opentelemetry-transport)
-+ [@axiomhq/pino](#@axiomhq/pino)
++ [pino-datadog-transport](#pino-datadog-transport)
 + [pino-discord-webhook](#pino-discord-webhook)
++ [pino-elasticsearch](#pino-elasticsearch)
++ [pino-hana](#pino-hana)
++ [pino-logflare](#pino-logflare)
 + [pino-logfmt](#pino-logfmt)
++ [pino-loki](#pino-loki)
++ [pino-opentelemetry-transport](#pino-opentelemetry-transport)
++ [pino-pretty](#pino-pretty)
++ [pino-roll](#pino-roll)
++ [pino-seq-transport](#pino-seq-transport)
++ [pino-sentry-transport](#pino-sentry-transport)
++ [pino-slack-webhook](#pino-slack-webhook)
++ [pino-telegram-webhook](#pino-telegram-webhook)
++ [pino-yc-transport](#pino-yc-transport)
 
 ### Legacy
 
@@ -436,7 +456,6 @@ PRs to this document are welcome for any new transports!
 + [pino-http-send](#pino-http-send)
 + [pino-kafka](#pino-kafka)
 + [pino-logdna](#pino-logdna)
-+ [pino-logflare](#pino-logflare)
 + [pino-loki](#pino-loki)
 + [pino-mq](#pino-mq)
 + [pino-mysql](#pino-mysql)
@@ -451,6 +470,34 @@ PRs to this document are welcome for any new transports!
 + [pino-websocket](#pino-websocket)
 
 
+<a id="@axiomhq/pino"></a>
+### @axiomhq/pino
+
+[@axiomhq/pino](https://www.npmjs.com/package/@axiomhq/pino) is the official [Axiom](https://axiom.co/) transport for Pino, using [axiom-js](https://github.com/axiomhq/axiom-js).
+
+```javascript
+import pino from 'pino';
+
+const logger = pino(
+  { level: 'info' },
+  pino.transport({
+    target: '@axiomhq/pino',
+    options: {
+      dataset: process.env.AXIOM_DATASET,
+      token: process.env.AXIOM_TOKEN,
+    },
+  }),
+);
+```
+
+then you can use the logger as usual:
+
+```js
+logger.info('Hello from pino!');
+```
+
+For further examples, head over to the [examples](https://github.com/axiomhq/axiom-js/tree/main/examples/pino) directory.
+
 <a id="@logtail/pino"></a>
 ### @logtail/pino
 
@@ -458,6 +505,85 @@ The [@logtail/pino](https://www.npmjs.com/package/@logtail/pino) NPM package is
 
 [Quick start guide ⇗](https://betterstack.com/docs/logs/javascript/pino)
 
+<a id="macfja-pino-fingers-crossed"></a>
+### @macfja/pino-fingers-crossed
+
+[@macfja/pino-fingers-crossed](https://github.com/MacFJA/js-pino-fingers-crossed) is a Pino v7+ transport that holds logs until a log level is reached, allowing to only have logs when it matters.
+
+```js
+const pino = require('pino');
+const { default: fingersCrossed, enable } = require('@macfja/pino-fingers-crossed')
+
+const logger = pino(fingersCrossed());
+
+logger.info('Will appear immedialty')
+logger.error('Will appear immedialty')
+
+logger.setBindings({ [enable]: 50 })
+logger.info('Will NOT appear immedialty')
+logger.info('Will NOT appear immedialty')
+logger.error('Will appear immedialty as well as the 2 previous messages') // error log are level 50
+logger.info('Will NOT appear')
+logger.info({ [enable]: false }, 'Will appear immedialty')
+logger.info('Will NOT appear')
+```
+<a id="pino-openobserve"></a>
+### @openobserve/pino-openobserve
+
+[@openobserve/pino-openobserve](https://github.com/openobserve/pino-openobserve) is a 
+Pino v7+ transport that will send logs to an 
+[OpenObserve](https://openobserve.ai) instance.
+
+```
+const pino = require('pino');
+const OpenobserveTransport = require('@openobserve/pino-openobserve');
+
+const logger = pino({
+  level: 'info',
+  transport: {
+    target: OpenobserveTransport,
+    options: {
+      url: 'https://your-openobserve-server.com',
+      organization: 'your-organization',
+      streamName: 'your-stream',
+      auth: {
+        username: 'your-username',
+        password: 'your-password',
+      },
+    },
+  },
+});
+```
+
+For full documentation check the [README](https://github.com/openobserve/pino-openobserve).
+
+<a id="pino-airbrake-transport"></a>
+### pino-airbrake-transport
+
+[pino-airbrake-transport][pino-airbrake-transport] is a Pino v7+ compatible transport to forward log events to [Airbrake][Airbrake]
+from a dedicated worker:
+
+```js
+const pino = require('pino')
+const transport = pino.transport({
+  target: 'pino-airbrake-transport',
+  options: {
+    airbrake: {
+      projectId: 1,
+      projectKey: "REPLACE_ME",
+      environment: "production",
+      // additional options for airbrake
+      performanceStats: false,
+    },
+  },
+  level: "error", // minimum log level that should be sent to airbrake
+})
+pino(transport)
+```
+
+[pino-airbrake-transport]: https://github.com/enricodeleo/pino-airbrake-transport
+[Airbrake]: https://airbrake.io/
+
 <a id="pino-applicationinsights"></a>
 ### pino-applicationinsights
 The [pino-applicationinsights](https://www.npmjs.com/package/pino-applicationinsights) module is a transport that will forward logs to [Azure Application Insights](https://docs.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview).
@@ -470,6 +596,24 @@ $ node foo | pino-applicationinsights --key blablabla
 
 For full documentation of command line switches read [README](https://github.com/ovhemert/pino-applicationinsights#readme)
 
+<a id="pino-axiom"></a>
+### pino-axiom
+
+[pino-axiom](https://www.npmjs.com/package/pino-axiom) is a transport that will forward logs to [Axiom](https://axiom.co).
+
+```javascript
+const pino = require('pino')
+const transport = pino.transport({
+  target: 'pino-axiom',
+  options: {
+    orgId: 'YOUR-ORG-ID', 
+    token: 'YOUR-TOKEN', 
+    dataset: 'YOUR-DATASET', 
+  },
+})
+pino(transport)
+```
+
 <a id="pino-azuretable"></a>
 ### pino-azuretable
 The [pino-azuretable](https://www.npmjs.com/package/pino-azuretable) module is a transport that will forward logs to the [Azure Table Storage](https://azure.microsoft.com/en-us/services/storage/tables/).
@@ -518,6 +662,87 @@ $ node foo | pino-datadog --key blablabla
 
 For full documentation of command line switches read [README](https://github.com/ovhemert/pino-datadog#readme)
 
+<a id="pino-datadog-transport"></a>
+### pino-datadog-transport
+
+[pino-datadog-transport][pino-datadog-transport] is a Pino v7+ compatible transport to forward log events to [Datadog][Datadog]
+from a dedicated worker:
+
+```js
+const pino = require('pino')
+const transport = pino.transport({
+  target: 'pino-datadog-transport',
+  options: {
+    ddClientConf: {
+      authMethods: {
+        apiKeyAuth: <your datadog API key>
+      }
+    },
+  },
+  level: "error", // minimum log level that should be sent to datadog
+})
+pino(transport)
+```
+
+[pino-datadog-transport]: https://github.com/theogravity/datadog-transports
+[Datadog]: https://www.datadoghq.com/
+
+#### Logstash
+
+The [pino-socket][pino-socket] module can also be used to upload logs to
+[Logstash][logstash] via:
+
+```
+$ node app.js | pino-socket -a 127.0.0.1 -p 5000 -m tcp
+```
+
+Assuming logstash is running on the same host and configured as
+follows:
+
+```
+input {
+  tcp {
+    port => 5000
+  }
+}
+
+filter {
+  json {
+    source => "message"
+  }
+}
+
+output {
+  elasticsearch {
+    hosts => "127.0.0.1:9200"
+  }
+}
+```
+
+See <https://www.elastic.co/guide/en/kibana/current/setup.html> to learn
+how to setup [Kibana][kibana].
+
+For Docker users, see
+https://github.com/deviantony/docker-elk to setup an ELK stack.
+
+<a id="pino-discord-webhook"></a>
+### pino-discord-webhook
+
+[pino-discord-webhook](https://github.com/fabulousgk/pino-discord-webhook) is a  Pino v7+ compatible transport to forward log events to a [Discord](http://discord.com) webhook from a dedicated worker. 
+
+```js
+import pino from 'pino'
+
+const logger = pino({
+  transport: {
+    target: 'pino-discord-webhook',
+    options: {
+      webhookUrl: 'https://discord.com/api/webhooks/xxxx/xxxx',
+    }
+  }
+})
+```
+
 <a id="pino-elasticsearch"></a>
 ### pino-elasticsearch
 
@@ -568,6 +793,31 @@ $ node your-app.js | pino-gelf log
 [gelf]: https://docs.graylog.org/en/2.1/pages/gelf.html
 [graylog]: https://www.graylog.org/
 
+<a id="pino-hana"></a>
+### pino-hana
+[pino-hana](https://github.com/HiImGiovi/pino-hana) is a Pino v7+ transport that save pino logs to a SAP HANA database.
+```js
+const pino = require('pino')
+const logger = pino({
+  transport: {
+    target: 'pino-hana',
+    options: {
+      connectionOptions: {
+        host: <hana db host>,
+        port: <hana db port>,
+        user: <hana db user>,
+        password: <hana db password>,
+      },
+      schema: <schema of the table in which you want to save the logs>,
+      table: <table in which you want to save the logs>,
+    },
+  },
+})
+
+logger.info('hi') // this log will be saved into SAP HANA
+```
+For more detailed information about its usage please check the official [documentation](https://github.com/HiImGiovi/pino-hana#readme).
+
 <a id="pino-http-send"></a>
 ### pino-http-send
 
@@ -607,33 +857,20 @@ Tags and other metadata can be included using the available command line options
 $ node index.js | pino-logflare --key YOUR_KEY --source YOUR_SOURCE
 ```
 
-<a id="pino-mq"></a>
-### pino-mq
-
-The `pino-mq` transport will take all messages received on `process.stdin` and send them over a message bus using JSON serialization.
-
-This is useful for:
-
-* moving backpressure from application to broker
-* transforming messages pressure to another component
-
-```
-node app.js | pino-mq -u "amqp://guest:guest@localhost/" -q "pino-logs"
-```
-
-Alternatively, a configuration file can be used:
+<a id="pino-logfmt"></a>
+### pino-logfmt
 
-```
-node app.js | pino-mq -c pino-mq.json
-```
+[pino-logfmt](https://github.com/botflux/pino-logfmt) is a Pino v7+ transport that formats logs into [logfmt](https://brandur.org/logfmt). This transport can output the formatted logs to stdout or file.
 
-A base configuration file can be initialized with:
+```js
+import pino from 'pino'
 
+const logger = pino({
+  transport: {
+    target: 'pino-logfmt'
+  }
+})
 ```
-pino-mq -g
-```
-
-For full documentation of command line switches and configuration see [the `pino-mq` README](https://github.com/itavy/pino-mq#readme)
 
 <a id="pino-loki"></a>
 ### pino-loki
@@ -657,24 +894,33 @@ pino(transport)
 
 For full documentation and configuration, see the [README](https://github.com/Julien-R44/pino-loki).
 
-<a id="pino-papertrail"></a>
-### pino-papertrail
-pino-papertrail is a transport that will forward logs to the [papertrail](https://papertrailapp.com) log service through an UDPv4 socket.
+<a id="pino-mq"></a>
+### pino-mq
 
-Given an application `foo` that logs via pino, and a papertrail destination that collects logs on port UDP `12345` on address `bar.papertrailapp.com`, you would use `pino-papertrail`
-like so:
+The `pino-mq` transport will take all messages received on `process.stdin` and send them over a message bus using JSON serialization.
 
-```
-node yourapp.js | pino-papertrail --host bar.papertrailapp.com --port 12345 --appname foo
-```
+This is useful for:
 
+* moving backpressure from application to broker
+* transforming messages pressure to another component
 
-for full documentation of command line switches read [README](https://github.com/ovhemert/pino-papertrail#readme)
+```
+node app.js | pino-mq -u "amqp://guest:guest@localhost/" -q "pino-logs"
+```
 
-<a id="pino-pg"></a>
-### pino-pg
-[pino-pg](https://www.npmjs.com/package/pino-pg) stores logs into PostgreSQL.
-Full documentation in the [README](https://github.com/Xstoudi/pino-pg).
+Alternatively, a configuration file can be used:
+
+```
+node app.js | pino-mq -c pino-mq.json
+```
+
+A base configuration file can be initialized with:
+
+```
+pino-mq -g
+```
+
+For full documentation of command line switches and configuration see [the `pino-mq` README](https://github.com/itavy/pino-mq#readme)
 
 <a id="pino-mysql"></a>
 ### pino-mysql
@@ -695,6 +941,48 @@ For full documentation and command line switches read the [README][pino-mysql].
 [MariaDB]: https://mariadb.org/
 [JSONDT]: https://dev.mysql.com/doc/refman/8.0/en/json.html
 
+<a id="pino-opentelemetry-transport"></a>
+### pino-opentelemetry-transport
+
+[pino-opentelemetry-transport](https://www.npmjs.com/package/pino-opentelemetry-transport) is a transport that will forward logs to an [OpenTelemetry log collector](https://opentelemetry.io/docs/collector/) using [OpenTelemetry JS instrumentation](https://opentelemetry.io/docs/instrumentation/js/).
+
+```javascript
+const pino = require('pino')
+
+const transport = pino.transport({
+  target: 'pino-opentelemetry-transport',
+  options: {
+    resourceAttributes: {
+      'service.name': 'test-service',
+      'service.version': '1.0.0'
+    }
+  }
+})
+
+pino(transport)
+```
+
+Documentation on running a minimal example is available in the [README](https://github.com/Vunovati/pino-opentelemetry-transport#minimalistic-example).
+
+<a id="pino-papertrail"></a>
+### pino-papertrail
+pino-papertrail is a transport that will forward logs to the [papertrail](https://papertrailapp.com) log service through an UDPv4 socket.
+
+Given an application `foo` that logs via pino, and a papertrail destination that collects logs on port UDP `12345` on address `bar.papertrailapp.com`, you would use `pino-papertrail`
+like so:
+
+```
+node yourapp.js | pino-papertrail --host bar.papertrailapp.com --port 12345 --appname foo
+```
+
+
+for full documentation of command line switches read [README](https://github.com/ovhemert/pino-papertrail#readme)
+
+<a id="pino-pg"></a>
+### pino-pg
+[pino-pg](https://www.npmjs.com/package/pino-pg) stores logs into PostgreSQL.
+Full documentation in the [README](https://github.com/Xstoudi/pino-pg).
+
 <a id="pino-redis"></a>
 ### pino-redis
 
@@ -707,6 +995,30 @@ $ node app.js | pino-redis -U redis://username:password@localhost:6379
 [pino-redis]: https://github.com/buianhthang/pino-redis
 [Redis]: https://redis.io/
 
+<a id="pino-roll"></a>
+### pino-roll
+
+`pino-roll` is a Pino transport that automatically rolls your log files based on size or time frequency.
+
+```js
+import { join } from 'path';
+import pino from 'pino';
+
+const transport = pino.transport({
+  target: 'pino-roll',
+  options: { file: join('logs', 'log'), frequency: 'daily', mkdir: true }
+});
+
+const logger = pino(transport);
+```
+
+then you can use the logger as usual:
+
+```js
+logger.info('Hello from pino-roll!');
+```
+For full documentation check the [README](https://github.com/mcollina/pino-roll?tab=readme-ov-file#pino-roll).
+
 <a id="pino-sentry"></a>
 ### pino-sentry
 
@@ -721,6 +1033,27 @@ For full documentation of command line switches see the [pino-sentry README](htt
 [pino-sentry]: https://www.npmjs.com/package/pino-sentry
 [Sentry]: https://sentry.io/
 
+<a id="pino-sentry-transport"></a>
+### pino-sentry-transport
+
+[pino-sentry-transport][pino-sentry-transport] is a Pino v7+ compatible transport to forward log events to [Sentry][Sentry]
+from a dedicated worker:
+
+```js
+const pino = require('pino')
+const transport = pino.transport({
+  target: 'pino-sentry-transport',
+  options: {
+    sentry: {
+      dsn: 'https://******@sentry.io/12345',
+    }
+  }
+})
+pino(transport)
+```
+
+[pino-sentry-transport]: https://github.com/tomer-yechiel/pino-sentry-transport
+[Sentry]: https://sentry.io/
 
 <a id="pino-seq"></a>
 ### pino-seq
@@ -752,55 +1085,32 @@ pino(transport)
 [pino-seq-transport]: https://github.com/autotelic/pino-seq-transport
 [Seq]: https://datalust.co/seq
 
-<a id="pino-sentry-transport"></a>
-### pino-sentry-transport
+<a id="pino-slack-webhook"></a>
+### pino-slack-webhook
 
-[pino-sentry-transport][pino-sentry-transport] is a Pino v7+ compatible transport to forward log events to [Sentry][Sentry]
+[pino-slack-webhook][pino-slack-webhook] is a Pino v7+ compatible transport to forward log events to [Slack][Slack]
 from a dedicated worker:
 
 ```js
 const pino = require('pino')
 const transport = pino.transport({
-  target: 'pino-sentry-transport',
+  target: '@youngkiu/pino-slack-webhook',
   options: {
-    sentry: {
-      dsn: 'https://******@sentry.io/12345',
-    }
+    webhookUrl: 'https://hooks.slack.com/services/xxx/xxx/xxx',
+    channel: '#pino-log',
+    username: 'webhookbot',
+    icon_emoji: ':ghost:'
   }
 })
 pino(transport)
 ```
 
-[pino-sentry-transport]: https://github.com/tomer-yechiel/pino-sentry-transport
-[Sentry]: https://sentry.io/
-
-
-<a id="pino-airbrake-transport"></a>
-### pino-airbrake-transport
-
-[pino-airbrake-transport][pino-airbrake-transport] is a Pino v7+ compatible transport to forward log events to [Airbrake][Airbrake]
-from a dedicated worker:
+[pino-slack-webhook]: https://github.com/youngkiu/pino-slack-webhook
+[Slack]: https://slack.com/
 
-```js
-const pino = require('pino')
-const transport = pino.transport({
-  target: 'pino-airbrake-transport',
-  options: {
-    airbrake: {
-      projectId: 1,
-      projectKey: "REPLACE_ME",
-      environment: "production",
-      // additional options for airbrake
-      performanceStats: false,
-    },
-  },
-  level: "error", // minimum log level that should be sent to airbrake
-})
-pino(transport)
-```
+[pino-pretty]: https://github.com/pinojs/pino-pretty
 
-[pino-airbrake-transport]: https://github.com/enricodeleo/pino-airbrake-transport
-[Airbrake]: https://airbrake.io/
+For full documentation of command line switches read the [README](https://github.com/abeai/pino-websocket#readme).
 
 <a id="pino-socket"></a>
 ### pino-socket
@@ -824,69 +1134,6 @@ Logs from the application should be observed on both consoles.
 
 [pino-socket]: https://www.npmjs.com/package/pino-socket
 
-<a id="pino-datadog-transport"></a>
-### pino-datadog-transport
-
-[pino-datadog-transport][pino-datadog-transport] is a Pino v7+ compatible transport to forward log events to [Datadog][Datadog]
-from a dedicated worker:
-
-```js
-const pino = require('pino')
-const transport = pino.transport({
-  target: 'pino-datadog-transport',
-  options: {
-    ddClientConf: {
-      authMethods: {
-        apiKeyAuth: <your datadog API key>
-      }
-    },
-  },
-  level: "error", // minimum log level that should be sent to datadog
-})
-pino(transport)
-```
-
-[pino-datadog-transport]: https://github.com/theogravity/pino-datadog-transport
-[Datadog]: https://www.datadoghq.com/
-
-#### Logstash
-
-The [pino-socket][pino-socket] module can also be used to upload logs to
-[Logstash][logstash] via:
-
-```
-$ node app.js | pino-socket -a 127.0.0.1 -p 5000 -m tcp
-```
-
-Assuming logstash is running on the same host and configured as
-follows:
-
-```
-input {
-  tcp {
-    port => 5000
-  }
-}
-
-filter {
-  json {
-    source => "message"
-  }
-}
-
-output {
-  elasticsearch {
-    hosts => "127.0.0.1:9200"
-  }
-}
-```
-
-See <https://www.elastic.co/guide/en/kibana/current/setup.html> to learn
-how to setup [Kibana][kibana].
-
-For Docker users, see
-https://github.com/deviantony/docker-elk to setup an ELK stack.
-
 <a id="pino-stackdriver"></a>
 ### pino-stackdriver
 The [pino-stackdriver](https://www.npmjs.com/package/pino-stackdriver) module is a transport that will forward logs to the [Google Stackdriver](https://cloud.google.com/logging/) log service through its API.
@@ -922,145 +1169,69 @@ Example output for the "hello world" log:
 [rfc3164]: https://tools.ietf.org/html/rfc3164
 [logstash]: https://www.elastic.co/products/logstash
 
+<a id="pino-telegram-webhook"></a>
+### pino-telegram-webhook
 
-<a id="pino-websocket"></a>
-### pino-websocket
-
-[pino-websocket](https://www.npmjs.com/package/@abeai/pino-websocket) is a transport that will forward each log line to a websocket server.
-
-```sh
-$ node app.js | pino-websocket -a my-websocket-server.example.com -p 3004
-```
-
-For full documentation of command line switches read the [README](https://github.com/abeai/pino-websocket#readme).
-
-<a id="pino-slack-webhook"></a>
-### pino-slack-webhook
-
-[pino-slack-webhook][pino-slack-webhook] is a Pino v7+ compatible transport to forward log events to [Slack][Slack]
-from a dedicated worker:
+[pino-telegram-webhook](https://github.com/Jhon-Mosk/pino-telegram-webhook) is a Pino v7+ transport for sending messages to [Telegram](https://telegram.org/). 
 
 ```js
-const pino = require('pino')
-const transport = pino.transport({
-  target: '@youngkiu/pino-slack-webhook',
-  options: {
-    webhookUrl: 'https://hooks.slack.com/services/xxx/xxx/xxx',
-    channel: '#pino-log',
-    username: 'webhookbot',
-    icon_emoji: ':ghost:'
-  }
-})
-pino(transport)
-```
-
-[pino-slack-webhook]: https://github.com/youngkiu/pino-slack-webhook
-[Slack]: https://slack.com/
+const pino = require('pino');
 
-[pino-pretty]: https://github.com/pinojs/pino-pretty
-
-For full documentation of command line switches read the [README](https://github.com/abeai/pino-websocket#readme).
-
-<a id="pino-axiom"></a>
-### pino-axiom
-
-[pino-axiom](https://www.npmjs.com/package/pino-axiom) is a transport that will forward logs to [Axiom](https://axiom.co).
-
-```javascript
-const pino = require('pino')
-const transport = pino.transport({
-  target: 'pino-axiom',
-  options: {
-    orgId: 'YOUR-ORG-ID', 
-    token: 'YOUR-TOKEN', 
-    dataset: 'YOUR-DATASET', 
+const logger = pino({
+  transport: {
+    target: 'pino-telegram-webhook',
+    level: 'error',
+    options: {
+      chatId: -1234567890,
+      botToken: "123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11",
+      extra: {
+              parse_mode: "HTML",
+            },
+    },
   },
 })
-pino(transport)
-```
-
-<a id="pino-opentelemetry-transport"></a>
-### pino-opentelemetry-transport
-
-[pino-opentelemetry-transport](https://www.npmjs.com/package/pino-opentelemetry-transport) is a transport that will forward logs to an [OpenTelemetry log collector](https://opentelemetry.io/docs/collector/) using [OpenTelemetry JS instrumentation](https://opentelemetry.io/docs/instrumentation/js/).
-
-```javascript
-const pino = require('pino')
-
-const transport = pino.transport({
-  target: 'pino-opentelemetry-transport',
-  options: {
-    resourceAttributes: {
-      'service.name': 'test-service',
-      'service.version': '1.0.0'
-    }
-  }
-})
 
-pino(transport)
+logger.error('<b>test log!</b>');
 ```
 
-Documentation on running a minimal example is available in the [README](https://github.com/Vunovati/pino-opentelemetry-transport#minimalistic-example).
+The `extra` parameter is optional. Parameters that the method [`sendMessage`](https://core.telegram.org/bots/api#sendmessage) supports can be passed to it.
 
-<a id="@axiomhq/pino"></a>
-### @axiomhq/pino
-
-[@axiomhq/pino](https://www.npmjs.com/package/@axiomhq/pino) is the official [Axiom](https://axiom.co/) transport for Pino, using [axiom-js](https://github.com/axiomhq/axiom-js).
-
-```javascript
-import pino from 'pino';
-
-const logger = pino(
-  { level: 'info' },
-  pino.transport({
-    target: '@axiomhq/pino',
-    options: {
-      dataset: process.env.AXIOM_DATASET,
-      token: process.env.AXIOM_TOKEN,
-    },
-  }),
-);
-```
+<a id="pino-websocket"></a>
+### pino-websocket
 
-then you can use the logger as usual:
+[pino-websocket](https://www.npmjs.com/package/@abeai/pino-websocket) is a transport that will forward each log line to a websocket server.
 
-```js
-logger.info('Hello from pino!');
+```sh
+$ node app.js | pino-websocket -a my-websocket-server.example.com -p 3004
 ```
 
-For further examples, head over to the [examples](https://github.com/axiomhq/axiom-js/tree/main/examples/pino) directory.
-
-<a id="pino-discord-webhook"></a>
-### pino-discord-webhook
-
-[pino-discord-webhook](https://github.com/fabulousgk/pino-discord-webhook) is a  Pino v7+ compatible transport to forward log events to a [Discord](http://discord.com) webhook from a dedicated worker. 
-
-```js
-import pino from 'pino'
-
-const logger = pino({
-  transport: {
-    target: 'pino-discord-webhook',
-    options: {
-      webhookUrl: 'https://discord.com/api/webhooks/xxxx/xxxx',
-    }
-  }
-})
-```
+For full documentation of command line switches read the [README](https://github.com/abeai/pino-websocket#readme).
 
-<a id="pino-logfmt"></a>
-### pino-logfmt
+<a id="pino-yc-transport"></a>
+### pino-yc-transport
 
-[pino-logfmt](https://github.com/botflux/pino-logfmt) is a Pino v7+ transport that formats logs into [logfmt](https://brandur.org/logfmt). This transport can output the formatted logs to stdout or file.
+[pino-yc-transport](https://github.com/Jhon-Mosk/pino-yc-transport) is a Pino v7+ transport for writing to [Yandex Cloud Logging](https://yandex.cloud/ru/services/logging) from serveless functions or containers.
 
 ```js
-import pino from 'pino'
+const pino = require("pino");
 
-const logger = pino({
+const config = {
+  level: "debug",
   transport: {
-    target: 'pino-logfmt'
-  }
-})
+    target: "pino-yc-transport",
+  },
+};
+
+const logger = pino(config);
+
+logger.debug("some message")
+logger.debug({ foo: "bar" });
+logger.debug("some message %o, %s", { foo: "bar" }, "baz");
+logger.info("info");
+logger.warn("warn");
+logger.error("error");
+logger.error(new Error("error"));
+logger.fatal("fatal");
 ```
 
 <a id="communication-between-pino-and-transport"></a>