Accessing via HTTPs displays less metrics than HTTP

[DanielBoyce]

When accessing my weblogic monitoring exporter endpoint via HTTP I'm getting a larger set of metrics than when I access via HTTPs.

Number of metrics returned via HTTP: 1184
Number of metrics returned via HTTPs: 894

Missing metrics over https such as:
wls_jvm_heap_free_current
wls_jvm_heap_free_percent
wls_jvm_heap_size_current
wls_jms_dest_messages_current_count

I also see #107 in the server logs for HTTPs calls.

Configuration:
`metricsNameSnakeCase: true
queries:

• key: name
  keyName: location
  prefix: wls_server_
  applicationRuntimes:
  key: name
  keyName: app
  componentRuntimes:
  prefix: wls_webapp_config_
  type: WebAppComponentRuntime
  key: name
  values: [deploymentState, contextRoot, sourceInfo, openSessionsHighCount, openSessionsCurrentCount, sessionsOpenedTotalCount, sessionCookieMaxAgeSecs, sessionInvalidationIntervalSecs, sessionTimeoutSecs, singleThreadedServletPoolSize, sessionIDLength, servletReloadCheckSecs, jSPPageCheckSecs]
  servlets:
  prefix: wls_servlet_
  key: servletName

• JVMRuntime:
  prefix: wls_jvm_
  key: name
  values: [heapFreeCurrent, heapFreePercent, heapSizeCurrent, heapSizeMax, uptime]

• executeQueueRuntimes:
  prefix: wls_socketmuxer_
  key: name
  values: [pendingRequestCurrentCount]

• workManagerRuntimes:
  prefix: wls_workmanager_
  key: name
  values: [stuckThreadCount, pendingRequests, completedRequests]

• threadPoolRuntime:
  prefix: wls_threadpool_
  key: name
  values: [executeThreadTotalCount, queueLength, stuckThreadCount, hoggingThreadCount]

• JMSRuntime:
  key: name
  keyName: jmsruntime
  prefix: wls_jmsruntime_
  JMSServers:
  prefix: wls_jms_
  key: name
  keyName: jmsserver
  destinations:
  prefix: wls_jms_dest_
  key: name
  keyName: destination

• persistentStoreRuntimes:
  prefix: wls_persistentstore_
  key: name

• JTARuntime:
  prefix: wls_jta_
  key: name`

[DanielBoyce]

Some additional information.
Initially I was only checking HTTPs first then comparing to HTTP.
I've found that once I've accessed via HTTP using the same weblogic login as is being used for HTTPs the additional metrics appear.

So logging in once using the HTTP endpoint enables the additional metrics for the HTTPs endpoint.

Unfortunately we would not be able to use this in production as the HTTP endpoint would be disabled.