
Product
Socket Now Supports pylock.toml Files
Socket now supports pylock.toml, enabling secure, reproducible Python builds with advanced scanning and full alignment with PEP 751's new standard.
Next generation observability. For browser / worker compatible IUDEX, use iudex-web
✅ aws-api-gateway ✅ console ✅ pino-http ✅ trpc
Supported libraries from OTel:
✅ amqplib ✅ aws-lambda ✅ aws-sdk ✅ bunyan ✅ cassandra-driver ✅ connect ✅ cucumber ✅ dataloader ✅ dns ✅ express ✅ fastify ✅ generic-pool ✅ graphql ✅ grpc ✅ hapi ✅ http ✅ ioredis ✅ knex ✅ koa ✅ lru-memoizer ✅ memcached ✅ mongodb ✅ mongoose ✅ mysql ✅ mysql2 ✅ nestjs-core ✅ net ✅ pg ✅ pino ✅ redis ✅ restify ✅ socket.io ✅ undici ✅ winston
Supported libraries from OpenLLMetry:
✅ @azure/openai ✅ @anthropic-ai/sdk ✅ @aws-sdk/client-bedrock-runtime ✅ @google-cloud/vertexai ✅ @qdrant/js-client-rest ✅ chromadb ✅ cohere-ai ✅ langchain ✅ llamaindex ✅ openai ✅ pinecone-client
Instrumenting your code with Iudex just takes a few steps.
npm install iudex
IUDEX_API_KEY
. You can manually add this to instrument
as well if you use something like a secrets manager.Search
to view your logs.Add this code to the top your entrypoint file (likely index.ts
).
import { instrument } from 'iudex';
instrument({
serviceName: 'YOUR_SERVICE_NAME', // highly encouraged
env: 'prod', // dev, local, etc
publicWriteOnlyIudexApiKey: 'YOUR_PUBLIC_WRITE_ONLY_KEY', // only ever commit your WRITE ONLY key
});
// ^ run above your other imports
You should be all set! Iudex will now record logs and trace the entire life cycle for each request.
Go to https://app.iudex.ai/ to start viewing your logs and traces!
For libraries that are not autoinstrumented or if your project uses "type": "module"
, follow the instructions from the table of contents for that specific library.
Add this code snippet to the top of your server file (likely app.ts
or index.ts
).
import { instrument } from 'iudex';
instrument({
serviceName: 'YOUR_SERVICE_NAME', // highly encouraged
env: 'prod', // dev, local, etc
publicWriteOnlyIudexApiKey: 'YOUR_PUBLIC_WRITE_ONLY_KEY', // only ever commit your WRITE ONLY key
});
// ^ run above your other imports
Add this code snippet to the top of your server file (likely server.ts
), add iudexFastify.logger
to the Fastify config.
import { instrument, iudexFastify } from 'iudex';
instrument({
serviceName: 'YOUR_SERVICE_NAME', // highly encouraged
env: 'prod', // dev, local, etc
publicWriteOnlyIudexApiKey: 'YOUR_PUBLIC_WRITE_ONLY_KEY', // only ever commit your WRITE ONLY key
});
// ^ run above your other imports
const fastify = Fastify({
logger: {
...iudexFastify.logger,
level: 'info',
},
});
TRPC instrumentation automatically works with pino-http
on your server.
If you want to log using custom middleware, you can write your own middleware.
const loggedProcedure = publicProcedure.use(withTracing((opts) => {
trackAttribute('path', opts.path);
trackAttribute('type', opts.type);
return opts.next();
}));
We are in the process of making this better.
import { instrument, iudexAwsLambda } from 'iudex';
const { withTracing } = iudexAwsLambda;
instrument({
serviceName: 'YOUR_SERVICE_NAME', // highly encouraged
env: 'prod', // dev, local, etc
publicWriteOnlyIudexApiKey: 'YOUR_PUBLIC_WRITE_ONLY_KEY', // only ever commit your WRITE ONLY key
});
// ^ run above your other imports
withTracing
.export const handler = withTracing(
// Your handler function goes here
);
If you use AWS API Gateway along with lambdas, instead import iudexAwsApiGateway
and wrap your lambda functions the same way using withTracing
.
import { instrument, iudexAwsApiGateway } from 'iudex';
const { withTracing } = iudexAwsApiGateway;
instrument({
serviceName: 'YOUR_SERVICE_NAME', // highly encouraged
env: 'prod', // dev, local, etc
publicWriteOnlyIudexApiKey: 'YOUR_PUBLIC_WRITE_ONLY_KEY', // only ever commit your WRITE ONLY key
});
// ^ run above your other imports
Call instrument
before instantiating the pino logger
. Create your logger using iudexPino.args
which will add IUDEX as an output destination for pino.
import { iudexPino } from 'iudex';
import pino from 'pino';
const logger = pino(...iudexPino.args);
If you have configured pino options or destinations, use iudexPino.options
and iudexPino.destination
for fine-grained control.
iudexPino.options
sets the mixin
propertyiudexPino.destination
sets the write
propertyimport { iudexPino } from 'iudex';
import pino from 'pino';
const write = str => {
iudexPino.destination.write(str);
console.log(str);
};
const logger = pino(iudexPino.options, { write });
Add this code snippet to the top your entry point file (likely index.ts
). Skip this step if you already call instrument
on your server.
import { instrument } from 'iudex';
instrument({
serviceName: 'YOUR_SERVICE_NAME', // highly encouraged
env: 'prod', // dev, local, etc
publicWriteOnlyIudexApiKey: 'YOUR_PUBLIC_WRITE_ONLY_KEY', // only ever commit your WRITE ONLY key
});
// ^ run above your other imports
Objects with the key ctx
will have values in ctx
added as attributes to the log. Example:
console.log('hello', { ctx: { userId: '123' } })
will create a log line with the userId
attribute set to 123
.
Use emitOtelLog
to send logs to iudex
. You have have called instrument
somewhere before emitOtelLog
.
import { emitOtelLog } from 'iudex';
/**
* Custom logger example
*/
function createLogger(level: keyof typeof console) {
return function logger(body: string, attributes: Record<string, any>) {
console[level](body, attributes);
emitOtelLog({ level, body, attributes })
};
}
Its recommended that you trace functions that are not called extremely frequently and that tend to be entry points for complex functionality. Examples of this are API routes, service controllers, and database clients. You can trace your function by wrapping it with withTracing
.
import { withTracing } from 'iudex';
const myFunction = withTracing(async () => {
console.log('I am traced');
}, { name: 'myFunction', trackArgs: true });
await myFunction();
// console: I am traced
Anytime myFunction
is called, it will create a span layer in a trace. trackArgs
will also track the arguments for the function. Tracked arguments will be truncated at 5000 characters. If you want to track specific parameters, it is recommended that you log them at the beginning of the function.
You can easily configure Slack alerts on a per-log basis with custom filters an logic by adding it in code.
Visit https://app.iudex.ai/logs and click on the Add to Slack
button in the top right.
Once installed to your workspace, tag your logs with the iudex.slack_channel_id
attribute.
// Example using logger
logger.info({ 'iudex.slack_channel_id': 'YOUR_SLACK_CHANNEL_ID' }, 'Hello from Slack!');
// Example using console, you must set { ctx }
console.log('Hello from Slack!', { ctx: { 'iudex.slack_channel_id': 'YOUR_SLACK_CHANNEL_ID' } });
Your channel ID can be found by clicking the name of the channel in the top left, then at the bottom of the dialog that pops up.
As long as the channel is public or you've invited the IUDEX app, logs will be sent as messages to their tagged channel any time they are logged.
The iudex
package contains the function instrument
which automatically attaches to libraries you use
and starts sending trace data to iudex
. Separately, logs sent via console are also sent. If you use another
logger library, find its instrumentation instructions or manually call emitOtelLog
to send a log.
instrument
is a function that automatically attaches to libraries you use and starts sending trace data to iudex
.
baseUrl?: string
api.iudex.ai
.iudexApiKey?: string
process.env.IUDEX_API_KEY
.serviceName?: string
instanceId?: string
gitCommit?: string
githubUrl?: string
env?: string
process.env.NODE_ENV
headers?: Record<string, string>
baseUrl
.settings?: Record<string, boolean>
false
.
emitOtelLog
is a function that sends a log to iudex
.
level: string
INFO
, WARN
, ERROR
, FATAL
, DEBUG
) of the log.body: any
severityNumber?: number
level
overwrites this.attributes?: Record<string, any>
trackAttribute
adds an attribute to the current active span.
key: string
value: any
withTracing
instruments a function by wrapping with a trace context. Wrapped functions can be called elsewhere and will always be traced.
import { withTracing } from 'iudex';
const myFunction = withTracing(async () => {
console.log('I am traced');
}, { name: 'myFunction' });
await myFunction();
// console: I am traced
fn: Function
opts
name?: string
trackArgs?: boolean
attributes.arg
or attributes.args
if there are multiple arguments.attributes?: Record<string, any>
setSpan?: (span: Span, ret: ReturnType<Function>) => void
useTracing
instruments and runs a function with trace context. The arguments are the same as withTracing
import { useTracing } from 'iudex';
await useTracing(async () => {
console.log('I am traced');
}, { name: 'myFunction' });
// console: I am traced
FAQs
Iudex client
The npm package iudex receives a total of 25 weekly downloads. As such, iudex popularity was classified as not popular.
We found that iudex demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now supports pylock.toml, enabling secure, reproducible Python builds with advanced scanning and full alignment with PEP 751's new standard.
Security News
Research
Socket uncovered two npm packages that register hidden HTTP endpoints to delete all files on command.
Research
Security News
Malicious Ruby gems typosquat Fastlane plugins to steal Telegram bot tokens, messages, and files, exploiting demand after Vietnam’s Telegram ban.