Remove loglevel-debug and DEBUG=apollo-gateway:* support.

packages/apollo-gateway/CHANGELOG.md

@@ -8,6 +8,7 @@
 - Warn of a possible misconfiguration when local service configuration is provided (via `serviceList` or `localServiceList`) and a remote Apollo Graph Manager configuration is subsequently found as well. [PR #3868](https://github.com/apollographql/apollo-server/pull/3868)
 - During composition, the unavailability of a downstream service in unmanaged federation mode will no longer result in a partially composed schema which merely lacks the types provided by the downed service.  This prevents unexpected validation errors for clients querying a graph which lacks types which were merely unavailable during the initial composition but were intended to be part of the graph. [PR #3867](https://github.com/apollographql/apollo-server/pull/3867)
 - Support providing a custom logger implementation (e.g. [`winston`](https://npm.im/winston), [`bunyan`](https://npm.im/bunyan), etc.) to capture gateway-sourced console output.  This allows the use of existing, production logging facilities or the possibiltiy to use advanced structure in logging, such as console output which is encapsulated in JSON.  The same PR that introduces this support also introduces a `logger` property to the `GraphQLRequestContext` that is exposed to `GraphQLDataSource`s and Apollo Server plugins, making it possible to attach additional properties (as supported by the logger implementation) to specific requests, if desired, by leveraging custom implementations in those components respectively.  When not provided, these will still output to `console`. [PR #3894](https://github.com/apollographql/apollo-server/pull/3894)
+- Drop use of `loglevel-debug`.  This removes the very long date and time prefix in front of each log line and also the support for the `DEBUG=apollo-gateway:` environment variable.  Both of these were uncommonly necessary or seldom used (with the environment variable also being undocumented).  The existing behavior can be preserved by providing a `logger` that uses `loglevel-debug`, if desired, and more details can be found in the PR.  [PR #3896](https://github.com/apollographql/apollo-server/pull/3896)
 
 ## 0.13.2
 

packages/apollo-gateway/package.json

@@ -30,7 +30,6 @@
     "apollo-server-types": "file:../apollo-server-types",
     "graphql-extensions": "file:../graphql-extensions",
     "loglevel": "^1.6.1",
-    "loglevel-debug": "^0.0.1",
     "make-fetch-happen": "^7.1.1",
     "pretty-format": "^24.7.0"
   },

packages/apollo-gateway/src/index.ts

@@ -21,7 +21,6 @@ import {
 import { GraphQLSchemaValidationError } from 'apollo-graphql';
 import { composeAndValidate, ServiceDefinition } from '@apollo/federation';
 import loglevel from 'loglevel';
-import loglevelDebug from 'loglevel-debug';
 
 import { buildQueryPlan, buildOperationContext } from './buildQueryPlan';
 import {
@@ -220,14 +219,13 @@ export class ApolloGateway implements GraphQLService {
       this.logger = this.config.logger;
     } else {
       // If the user didn't provide their own logger, we'll initialize one.
-      const loglevelLogger = loglevel.getLogger(`apollo-gateway:`);
-
-      // Support DEBUG environment variable, à la https://npm.im/debug/.
-      loglevelDebug(loglevelLogger);
+      const loglevelLogger = loglevel.getLogger(`apollo-gateway`);
 
       // And also support the `debug` option, if it's truthy.
       if (this.config.debug === true) {
-        loglevelLogger.enableAll();
+        loglevelLogger.setLevel(loglevelLogger.levels.DEBUG);
+      } else {
+        loglevelLogger.setLevel(loglevelLogger.levels.WARN);
       }
 
       this.logger = loglevelLogger;