Azure Monitor OpenTelemetry with Node.js to have graphql operation name

Question

Azure Monitor OpenTelemetry with Node.js to have graphql operation name

Parag Kale 25

Hi,

I recently introduced Node.js azure observability to send telemetry to Azure monitor as mentioned in the documentation https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-configuration?tabs=nodejs

Below is the code snippet that was added for NextJS to track the api calls

import { useAzureMonitor } from 'applicationinsights';

import type { AzureMonitorOpenTelemetryOptions } from 'applicationinsights';

import { resourceFromAttributes } from '@opentelemetry/resources';

import { ATTR_SERVICE_NAME } from '@opentelemetry/semantic-conventions';

const connectionString = process.env.NEXT_PUBLIC_APP_INSIGHTS_CONNECTION_STRING;

if (connectionString) {

const serviceAttributes = {

[ATTR_SERVICE_NAME]: 'gtis2-nextjs-server',

};

const resource = resourceFromAttributes(serviceAttributes);

const options: AzureMonitorOpenTelemetryOptions = {

azureMonitorExporterOptions: {

  connectionString,

},

resource,

};

// eslint-disable-next-line react-hooks/rules-of-hooks

useAzureMonitor(options);

console.log(

`[Azure Observability] OpenTelemetry with Azure Monitor initialized successfully!`,

);

}

The app insights telemetry under gtis2-nextjs-server , I am only seeing POST /api/graphql. I want to see the graphql operation name as well. I am attaching the screenshotimage (1).jpg

Siva shunmugam Nadessin 575 Reputation points Microsoft External Staff Moderator

2025-08-19T02:07:30.1333333+00:00
Hello Parag Kale,

Follow the below and provide us the update,

Custom Telemetry: You may need to manually set the operation name for your requests if they're not being captured correctly by default. This can often be done by using a custom Telemetry initializer or modifying the current telemetry with the appropriate properties.

Enable Diagnostic Logging: As outlined in the OpenTelemetry troubleshooting documentation you can enable detailed logs to help diagnose why operation names might be missing. This could potentially shed light on any underlying issues.

Check Dependency and Request Tracking: Ensure that the specific GraphQL middleware you're using is properly integrated with OpenTelemetry to capture operation names. Sometimes middleware can interfere with how telemetry is captured.

Consult Documentation: Review the Azure Monitor OpenTelemetry configuration documentation to ensure that all required settings for operation names are configured.

Testing and Validation: Once you've implemented changes, test to verify that the operation names are being sent correctly. You can use tools like Postman or a similar API testing tool to perform the GraphQL requests.

If the comment was helpful, please click "Upvote" else let us know the issue you are still facing for us to investigate further.

Thanks,

Siva shunmugam.
Parag Kale 25 Reputation points

2025-08-19T12:17:58.0566667+00:00
I am trying to capture telemetry from the Next js server level ( server side telemetry ) , can you please let me know sample code that I can use to set up telemetry to have graphql operation name or API payload details

Currently the azure monitor has been set up like below to send the telemetry details.

With this , I s ee only the path /api/graphql being logged , but not the operation name like getAllUsers etc.

import { useAzureMonitor } from 'applicationinsights';

import type { AzureMonitorOpenTelemetryOptions } from 'applicationinsights';

import { resourceFromAttributes } from '@opentelemetry/resources';

import { ATTR_SERVICE_NAME } from '@opentelemetry/semantic-conventions';

const connectionString = process.env.NEXT_PUBLIC_APP_INSIGHTS_CONNECTION_STRING;

if (connectionString) {

const serviceAttributes = {

[ATTR_SERVICE_NAME]: 'gtis2-nextjs-server',

};

const resource = resourceFromAttributes(serviceAttributes);

const options: AzureMonitorOpenTelemetryOptions = {

azureMonitorExporterOptions: { connectionString, }, resource,

};

// eslint-disable-next-line react-hooks/rules-of-hooks

useAzureMonitor(options);

console.log(

`[Azure Observability] OpenTelemetry with Azure Monitor initialized successfully!`,

);

}
Siva shunmugam Nadessin 575 Reputation points Microsoft External Staff Moderator

2025-08-20T01:05:41.4066667+00:00

Hello Parag Kale,

To address this, you might need to configure your telemetry to set the operation name explicitly for your GraphQL API calls. Here are a few steps you can take to try and resolve this:

Custom Telemetry Initializer: You can use a custom telemetry initializer to set the operation name for your GraphQL requests. Here's an example to illustrate how you might implement this:

const { ApplicationInsights } = require("applicationinsights");

const appInsights = new ApplicationInsights({

    connectionString: process.env.NEXT_PUBLIC_APP_INSIGHTS_CONNECTION_STRING,

});

appInsights.setAutoCollectConsole(true);

appInsights.start();

// Custom function to track GraphQL operation

function trackGraphQLRequest(operationName, request) {

    const telemetryClient = appInsights.defaultClient;

    telemetryClient.trackRequest({

        name: operationName,

        url: request.url,

        duration: /* duration in milliseconds */,

        resultCode: 200,

        success: true // or false based on your logic

    });

}

If the comment was helpful, please click "Upvote".

Thanks,

Siva shunmugam.

Your answer

Siva shunmugam Nadessin 575 Reputation points Microsoft External Staff Moderator

2025-08-19T02:07:30.1333333+00:00

Hello Parag Kale,

Follow the below and provide us the update,

Custom Telemetry: You may need to manually set the operation name for your requests if they're not being captured correctly by default. This can often be done by using a custom Telemetry initializer or modifying the current telemetry with the appropriate properties.

Enable Diagnostic Logging: As outlined in the OpenTelemetry troubleshooting documentation you can enable detailed logs to help diagnose why operation names might be missing. This could potentially shed light on any underlying issues.

Check Dependency and Request Tracking: Ensure that the specific GraphQL middleware you're using is properly integrated with OpenTelemetry to capture operation names. Sometimes middleware can interfere with how telemetry is captured.

Consult Documentation: Review the Azure Monitor OpenTelemetry configuration documentation to ensure that all required settings for operation names are configured.

Testing and Validation: Once you've implemented changes, test to verify that the operation names are being sent correctly. You can use tools like Postman or a similar API testing tool to perform the GraphQL requests.

If the comment was helpful, please click "Upvote" else let us know the issue you are still facing for us to investigate further.

Thanks,

Siva shunmugam.
Parag Kale 25 Reputation points

2025-08-19T12:17:58.0566667+00:00

I am trying to capture telemetry from the Next js server level ( server side telemetry ) , can you please let me know sample code that I can use to set up telemetry to have graphql operation name or API payload details

Currently the azure monitor has been set up like below to send the telemetry details.

With this , I s ee only the path /api/graphql being logged , but not the operation name like getAllUsers etc.

import { useAzureMonitor } from 'applicationinsights';

import type { AzureMonitorOpenTelemetryOptions } from 'applicationinsights';

import { resourceFromAttributes } from '@opentelemetry/resources';

import { ATTR_SERVICE_NAME } from '@opentelemetry/semantic-conventions';

const connectionString = process.env.NEXT_PUBLIC_APP_INSIGHTS_CONNECTION_STRING;

if (connectionString) {

const serviceAttributes = {

[ATTR_SERVICE_NAME]: 'gtis2-nextjs-server',

};

const resource = resourceFromAttributes(serviceAttributes);

const options: AzureMonitorOpenTelemetryOptions = {

azureMonitorExporterOptions: { connectionString, }, resource,

};

// eslint-disable-next-line react-hooks/rules-of-hooks

useAzureMonitor(options);

console.log(

`[Azure Observability] OpenTelemetry with Azure Monitor initialized successfully!`,

);

}
Siva shunmugam Nadessin 575 Reputation points Microsoft External Staff Moderator

2025-08-20T01:05:41.4066667+00:00

Hello Parag Kale,

To address this, you might need to configure your telemetry to set the operation name explicitly for your GraphQL API calls. Here are a few steps you can take to try and resolve this:

Custom Telemetry Initializer: You can use a custom telemetry initializer to set the operation name for your GraphQL requests. Here's an example to illustrate how you might implement this:

const { ApplicationInsights } = require("applicationinsights");

const appInsights = new ApplicationInsights({

connectionString: process.env.NEXT_PUBLIC_APP_INSIGHTS_CONNECTION_STRING,

});

appInsights.setAutoCollectConsole(true);

appInsights.start();

// Custom function to track GraphQL operation

function trackGraphQLRequest(operationName, request) {

const telemetryClient = appInsights.defaultClient;

telemetryClient.trackRequest({

name: operationName,

url: request.url,

duration: /* duration in milliseconds */,

resultCode: 200,

success: true // or false based on your logic

});

}

If the comment was helpful, please click "Upvote".

Thanks,

Siva shunmugam.

Share via

Azure Monitor OpenTelemetry with Node.js to have graphql operation name

Your answer